Announced routes
Every prefix a peer of the route collectors sees with origin AS61414, 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.
| 93.93.246.0/24 | Valid | Other origin only | 667 99% |
| 103.93.76.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.93.77.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.93.78.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.93.79.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.213.244.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 103.225.68.0/23 | Valid | RIR databaseAPNIC | 669 99% |
| 123.253.108.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 123.253.109.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 144.48.4.0/24 | Valid | RIR databaseAPNIC | 669 99% |
| 185.243.40.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 185.243.41.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 185.243.42.0/24 | Valid | RIR databaseRIPE | 667 99% |
| 193.3.191.0/24 | Valid | RIR databaseRADB, RIPE | 667 99% |
| 2a0d:280::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS61414's PeeringDB record names no 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 23 are in fix.csv.
- Route object: none1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 93.93.246.0/24 | Route objects for it name AS997, AS49466. Add a route object with origin AS61414 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61414 whose prefix no peer sees AS61414 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 93.93.244.0/24 | RIPE | Invalid: origin |
| 93.93.245.0/24 | RIPE | Invalid: origin |
| 103.23.172.0/23 | APNIC | Valid |
| 103.23.172.0/24 | APNIC | Valid |
| 103.23.173.0/24 | APNIC | Valid |
| 103.93.76.0/22 | APNIC | Valid |
| 103.213.244.0/22 | APNIC | Valid |
| 103.213.244.0/23 | APNIC | Valid |
| 103.213.245.0/24 | APNIC | Valid |
| 103.213.246.0/23 | APNIC | Valid |
| 103.213.246.0/24 | APNIC | Valid |
| 103.213.247.0/24 | APNIC | Valid |
| 123.253.108.0/22 | APNIC | Valid |
| 144.48.4.0/22 | APNIC | Valid |
| 144.48.4.0/23 | APNIC | Valid |
| 144.48.5.0/24 | APNIC | Valid |
| 144.48.6.0/23 | APNIC | Valid |
| 144.48.6.0/24 | APNIC | Valid |
| 144.48.7.0/24 | APNIC | Valid |
| 154.217.248.0/21 | RADB | Valid |
| 2600:b400::/32 | ARIN | Valid |
| 2a0d:280::/29 | RIPE | 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.