Network · data from 2026-11-12
AS138180 ERNSTYOUNG-AS-AP - Ernst & Young Services Pty Ltd
Registry name: ERNSTYOUNG-AS-AP - Ernst & Young Services Pty Ltd, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138180, 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.
| 203.2.0.0/19 | No ROA | None | 2 0%low visibility |
| 199.49.55.0/24 | No ROA | RIR databaseARIN | 2 0%low visibility |
| 203.2.12.0/24 | No ROA | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS138180 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 34 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: not announced30
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 203.2.0.0/19 | No ROA covers it. Add a ROA for AS138180, maxLength 19. |
| Route object: none | 203.2.0.0/19 | No route object for it. Add a route object with origin AS138180 in the RIR database for the space. |
| ROA: none | 199.49.55.0/24 | No ROA covers it. Add a ROA for AS138180, maxLength 24. |
| ROA: none | 203.2.12.0/24 | No ROA covers it. Add a ROA for AS138180, maxLength 24. |
Route objects not announced
Route objects with origin AS138180 whose prefix no peer sees AS138180 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 203.2.1.0/24 | APNIC | No ROA |
| 203.2.2.0/24 | APNIC | No ROA |
| 203.2.3.0/24 | APNIC | No ROA |
| 203.2.4.0/24 | APNIC | No ROA |
| 203.2.5.0/24 | APNIC | No ROA |
| 203.2.6.0/24 | APNIC | No ROA |
| 203.2.7.0/24 | APNIC | No ROA |
| 203.2.8.0/24 | APNIC | No ROA |
| 203.2.9.0/24 | APNIC | No ROA |
| 203.2.10.0/24 | APNIC | No ROA |
| 203.2.11.0/24 | APNIC | No ROA |
| 203.2.13.0/24 | APNIC | No ROA |
| 203.2.14.0/24 | APNIC | No ROA |
| 203.2.15.0/24 | APNIC | No ROA |
| 203.2.16.0/24 | APNIC | No ROA |
| 203.2.17.0/24 | APNIC | No ROA |
| 203.2.18.0/24 | APNIC | No ROA |
| 203.2.19.0/24 | APNIC | No ROA |
| 203.2.20.0/24 | APNIC | No ROA |
| 203.2.21.0/24 | APNIC | No ROA |
| 203.2.22.0/24 | APNIC | No ROA |
| 203.2.23.0/24 | APNIC | No ROA |
| 203.2.24.0/24 | APNIC | No ROA |
| 203.2.25.0/24 | APNIC | No ROA |
| 203.2.26.0/24 | APNIC | No ROA |
| 203.2.27.0/24 | APNIC | No ROA |
| 203.2.28.0/24 | APNIC | No ROA |
| 203.2.29.0/24 | APNIC | No ROA |
| 203.2.30.0/24 | APNIC | No ROA |
| 203.2.31.0/24 | APNIC | 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.