Network · data from 2026-11-12
AS46457 ESD112 - ESD 112
Registry name: ESD112 - ESD 112, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46457, 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.
| 69.56.66.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 164.116.2.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 164.116.49.0/24 | Valid | Other IRR onlyRADB | 669 99% |
AS-SET
AS46457 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 3 are in fix.csv.
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 69.56.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.116.2.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 164.116.49.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS46457 is announced.
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.