Network · data from 2026-11-12
AS23686 ASN-EQIX-MELBOURNE-AP - Equinix Asia Pacific
Registry name: ASN-EQIX-MELBOURNE-AP - Equinix Asia Pacific, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS23686, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 103.73.83.0/24 | No ROA | Other origin only | 671 100% |
| 203.3.137.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 129.192.211.0/24 | No ROA | Other IRR onlyNTTCOM | 671 100% |
| 2404:4f01::/33 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
AS23686 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 32 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: RIR2
- Route object: not announced26
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.73.83.0/24 | No ROA covers it. Add a ROA for AS23686, maxLength 24. |
| Route object: none | 103.73.83.0/24 | Route objects for it name AS7566. Add a route object with origin AS23686 in the RIR database for the space. |
| ROA: none | 203.3.137.0/24 | No ROA covers it. Add a ROA for AS23686, maxLength 24. |
| Route object: RIR | 203.3.137.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 129.192.211.0/24 | No ROA covers it. Add a ROA for AS23686, maxLength 24. |
| Route object: RIR | 129.192.211.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS23686 whose prefix no peer sees AS23686 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 51.162.48.0/24 | RADB | Valid |
| 51.162.49.0/24 | RADB | Valid |
| 51.162.50.0/23 | RADB | Valid |
| 51.162.71.0/24 | APNIC, RADB | Valid |
| 101.97.48.0/23 | RADB | Valid |
| 101.97.50.0/23 | RADB | Valid |
| 101.97.56.0/21 | NTTCOM | No ROA |
| 103.136.140.0/24 | RADB | No ROA |
| 103.236.202.0/24 | RADB | No ROA |
| 129.192.202.0/24 | RADB | No ROA |
| 169.173.160.0/24 | RADB | No ROA |
| 194.145.28.0/24 | RADB | No ROA |
| 203.0.34.128/29 | NTTCOM | No ROA |
| 203.0.34.136/29 | NTTCOM | No ROA |
| 203.3.107.0/24 | RADB | No ROA |
| 203.3.108.0/24 | RADB | No ROA |
| 203.3.109.0/24 | RADB | No ROA |
| 203.3.110.0/24 | RADB | No ROA |
| 203.55.184.0/24 | RADB | No ROA |
| 203.55.187.0/24 | RADB | No ROA |
| 203.119.26.0/24 | RADB | No ROA |
| 203.119.28.0/24 | RADB | No ROA |
| 2001:dc7::/48 | RADB | No ROA |
| 2001:dc7:1000::/48 | RADB | No ROA |
| 2001:dc7:fffe::/48 | RADB | No ROA |
| 2001:dc7:ffff::/48 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.