Network · data from 2026-11-12
AS267403 AS267403 - Inova Servicos em Tecnologia Comercail Ltda - Me.
Registry name: AS267403 - Inova Servicos em Tecnologia Comercail Ltda - Me., BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267403, 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.
| 45.234.204.0/24 | No ROA | Nonecovered by 45.234.204.0/22 | 669 99% |
AS-SET
AS267403 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.234.204.0/24 | No ROA covers it. Add a ROA for AS267403, maxLength 24. |
| Route object: none | 45.234.204.0/24 | No route object for it. A route object for 45.234.204.0/22 with origin AS267403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267403 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267403 whose prefix no peer sees AS267403 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.234.204.0/22 | RADB | No ROA |
| 2804:4cf4::/32 | 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.