Announced routes
Every prefix a peer of the route collectors sees with origin AS25743, 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.
| 103.221.49.0/24 | Valid | Other origin only | 221 33% |
| 45.73.180.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS25743'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 8 are in fix.csv.
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.221.49.0/24 | Route objects for it name AS139259. Add a route object with origin AS25743 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25743 whose prefix no peer sees AS25743 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.6.108.0/22 | RADB | Valid |
| 103.6.228.0/24 | RADB | Valid |
| 116.204.208.0/24 | APNIC | Valid |
| 116.204.209.0/24 | APNIC | Valid |
| 116.204.210.0/24 | APNIC | Valid |
| 116.204.211.0/24 | APNIC | Valid |
| 205.198.116.0/24 | 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.