Network · data from 2026-11-12
AS56057 ENTITYDATA-AU - Entity Data Pty Limited
Registry name: ENTITYDATA-AU - Entity Data Pty Limited, AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56057, 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.
| 119.148.66.0/24 | No ROA | Other origin only | 672 100% |
| 2402:e500:f000::/48 | No ROA | Other origin only | 635 100% |
| 103.82.155.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 111.118.220.0/24 | Valid | Nonecovered by 111.118.220.0/23 | 672 100% |
| 111.118.221.0/24 | Valid | Nonecovered by 111.118.220.0/23 | 672 100% |
| 111.118.222.0/24 | Valid | Nonecovered by 111.118.222.0/23 | 672 100% |
| 111.118.223.0/24 | Valid | Nonecovered by 111.118.222.0/23 | 672 100% |
| 2402:e500:1000::/36 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS56057 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 14 are in fix.csv.
- ROA: none3
- Route object: none6
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 119.148.66.0/24 | No ROA covers it. Add a ROA for AS56057, maxLength 24. |
| Route object: none | 119.148.66.0/24 | Route objects for it name AS4851. Add a route object with origin AS56057 in the RIR database for the space. |
| ROA: none | 2402:e500:f000::/48 | No ROA covers it. Add a ROA for AS56057, maxLength 48. |
| Route object: none | 2402:e500:f000::/48 | Route objects for it name AS20473. Add a route object with origin AS56057 in the RIR database for the space. |
| ROA: none | 103.82.155.0/24 | No ROA covers it. Add a ROA for AS56057, maxLength 24. |
| Route object: RIR | 103.82.155.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 111.118.220.0/24 | No route object for it. A route object for 111.118.220.0/23 with origin AS56057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56057 in the RIR database for the space. |
| Route object: none | 111.118.221.0/24 | No route object for it. A route object for 111.118.220.0/23 with origin AS56057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56057 in the RIR database for the space. |
| Route object: none | 111.118.222.0/24 | No route object for it. A route object for 111.118.222.0/23 with origin AS56057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56057 in the RIR database for the space. |
| Route object: none | 111.118.223.0/24 | No route object for it. A route object for 111.118.222.0/23 with origin AS56057 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56057 in the RIR database for the space. |
| Route object: RIR | 2402:e500:1000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56057 whose prefix no peer sees AS56057 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 111.118.220.0/22 | RADB | No ROA |
| 111.118.220.0/23 | RADB | No ROA |
| 111.118.222.0/23 | 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.