bgpreport

Network · data from 2026-11-12

AS264308 RM INFORMATICA

Registry name: AS264308 - RM INFORMATICA INTERNET LTDA, BR · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 routes 100.0% RPKI valid · 40.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS264308, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264308, 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:25e0::/34 Valid Nonecovered by 2804:25e0::/32 632 99% 67
2804:25e0:4000::/34 Valid Nonecovered by 2804:25e0::/32 632 99% 67
2804:25e0:8000::/34 Valid Nonecovered by 2804:25e0::/32 632 99% 67
138.122.23.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 66
138.122.20.0/23 Valid Other IRR onlyALTDB 668 99% 66
138.122.20.0/24 Valid Other IRR onlyALTDB 667 99% 66
138.122.22.0/24 Valid Other IRR onlyALTDB, RADB 667 99% 66
138.122.21.0/24 Valid Other IRR onlyALTDB 666 99% 67
2804:25e0:c000::/34 Valid Other IRR onlyRADB 636 100% 67
2804:25e0:c000::/40 Valid Other IRR onlyALTDB, RADB 628 99% 67

AS-SET

AS264308's PeeringDB record names no 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 13 are in fix.csv.

  • Route object: none3
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2804:25e0::/34No route object for it. A route object for 2804:25e0::/32 with origin AS264308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264308 in the RIR database for the space.632 of 636
Route object: none2804:25e0:4000::/34No route object for it. A route object for 2804:25e0::/32 with origin AS264308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264308 in the RIR database for the space.632 of 636
Route object: none2804:25e0:8000::/34No route object for it. A route object for 2804:25e0::/32 with origin AS264308 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264308 in the RIR database for the space.632 of 636
Route object: RIR138.122.23.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.122.20.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
Route object: RIR138.122.20.0/24Route object only in ALTDB. Add it in the RIR database for the space.667 of 673
Route object: RIR138.122.22.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR138.122.21.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:25e0:c000::/34Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:25e0:c000::/40Route object only in ALTDB, RADB. Add it in the RIR database for the space.628 of 636

Route objects not announced

Route objects with origin AS264308 whose prefix no peer sees AS264308 announce. Many are kept on purpose (backup routes, space announced only in some places).

138.122.20.0/22ALTDB, RADB, TCValid
138.122.22.0/23ALTDBValid
2804:25e0::/32ALTDB, RADB, TCValid

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.