Network · data from 2026-11-12
AS273364 AS273364 - i9 Telecom MS
Registry name: AS273364 - i9 Telecom MS, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273364, 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.
| 2804:8d8c::/32 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS273364 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 7 are in fix.csv.
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2804:8d8c::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273364 whose prefix no peer sees AS273364 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:8d8c::/33 | RADB | Valid |
| 2804:8d8c::/34 | RADB | Valid |
| 2804:8d8c:4000::/34 | RADB | Valid |
| 2804:8d8c:8000::/33 | RADB | Valid |
| 2804:8d8c:8000::/34 | RADB | Valid |
| 2804:8d8c:c000::/34 | RADB | Valid |
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.