Network · data from 2026-11-12
AS267394 AS267394 - AV3M Telecom e Multimidia LTDA
Registry name: AS267394 - AV3M Telecom e Multimidia LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267394, 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.235.60.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 45.235.62.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 45.235.60.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 2804:4cd0::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
AS-SET
AS267394 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: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.235.60.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.235.62.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.235.60.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4cd0::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267394 whose prefix no peer sees AS267394 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.235.61.0/24 | RADB | Valid |
| 45.235.62.0/24 | RADB | Valid |
| 45.235.63.0/24 | 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.