Network · data from 2026-11-12
AS208673 ESTOXY-EE
Registry name: ESTOXY-EE ESTOXY OU, EE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208673, 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.
| 91.234.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.112.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.113.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.119.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.121.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.122.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.123.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.53.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.53.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.214.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.214.103.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.214.104.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.214.107.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.214.114.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.214.116.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 178.214.118.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS208673's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS208673 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.