Network · data from 2026-11-12
AS265331 AS265331 - M. R. MELO ALEXANDRINO
Registry name: AS265331 - M. R. MELO ALEXANDRINO, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265331, 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.
| 168.181.84.0/22 | No ROA | Other IRR onlyRADB, TC | 668 99% |
| 2804:2e34::/32 | No ROA | Other IRR onlyRADB | 633 100% |
AS-SET
AS265331 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 8 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 168.181.84.0/22 | No ROA covers it. Add a ROA for AS265331, maxLength 22. |
| Route object: RIR | 168.181.84.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:2e34::/32 | No ROA covers it. Add a ROA for AS265331, maxLength 32. |
| Route object: RIR | 2804:2e34::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265331 whose prefix no peer sees AS265331 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.181.84.0/23 | RADB | No ROA |
| 168.181.86.0/23 | RADB | No ROA |
| 2804:2e34::/33 | RADB | No ROA |
| 2804:2e34:8000::/33 | 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.