Announced routes
Every prefix a peer of the route collectors sees with origin AS61254, 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.
| 117.55.202.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.241.206.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.237.231.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 205.237.104.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 205.237.105.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 205.237.106.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 205.237.107.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 117.55.203.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 77.247.108.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 185.53.90.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 185.53.91.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 77.247.111.0/24 | No ROA | RIR databaseRIPE | 668 99% |
| 185.209.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.49.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.49.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.49.227.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.49.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.49.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.49.230.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 37.49.226.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 37.49.231.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.196.229.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 2a13:adc3::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS61254: RIPE::AS-ESTOXY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61254 isn't in the set, or no route object for AS61254 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS61254 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-ESTOXY | RIPE | 43 | 4 | Yes | 0 |
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 12 are in fix.csv.
- ROA: none12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 117.55.202.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 185.241.206.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 212.237.231.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 205.237.104.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 205.237.105.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 205.237.106.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 205.237.107.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 117.55.203.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 77.247.108.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 185.53.90.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 185.53.91.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
| ROA: none | 77.247.111.0/24 | No ROA covers it. Add a ROA for AS61254, maxLength 24. |
Route objects not announced
Every route object with origin AS61254 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.