Network · data from 2026-11-12
AS269320 AS269320 - R M INTERWEB LTDA
Registry name: AS269320 - R M INTERWEB LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269320, 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:62d0::/33 | Valid | Nonecovered by 2804:62d0::/32 | 634 100% |
| 2804:62d0:c000::/34 | Valid | Nonecovered by 2804:62d0::/32 | 634 100% |
| 45.184.64.0/24 | Valid | Other IRR onlyALTDB, RADB | 669 99% |
| 45.184.65.0/24 | Valid | Other IRR onlyALTDB, RADB, TC | 669 99% |
| 45.184.66.0/24 | Valid | Other IRR onlyALTDB, TC | 669 99% |
| 45.184.67.0/24 | Valid | Other IRR onlyALTDB, TC | 669 99% |
AS-SET
AS269320 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 10 are in fix.csv.
- Route object: none2
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:62d0::/33 | No route object for it. A route object for 2804:62d0::/32 with origin AS269320 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269320 in the RIR database for the space. |
| Route object: none | 2804:62d0:c000::/34 | No route object for it. A route object for 2804:62d0::/32 with origin AS269320 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269320 in the RIR database for the space. |
| Route object: RIR | 45.184.64.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.65.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.66.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.184.67.0/24 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269320 whose prefix no peer sees AS269320 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.184.64.0/22 | ALTDB, NTTCOM, RADB, TC | No ROA |
| 45.184.64.0/23 | RADB | No ROA |
| 45.184.66.0/23 | RADB | No ROA |
| 2804:62d0::/32 | ALTDB, NTTCOM, RADB, TC | 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.