bgpreport

Network · data from 2026-11-12

AS265481 AS265481 - GM TELECOM E INFORMATICA LTDA ME

Registry name: AS265481 - GM TELECOM E INFORMATICA LTDA ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265481, 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:34cc::/33 Valid Nonecovered by 2804:34cc::/32 636 100% 67
2804:34cc:8000::/33 Valid Nonecovered by 2804:34cc::/32 636 100% 67
168.197.116.0/22 Valid Other IRR onlyRADB 672 100% 66
168.197.119.0/24 Valid Other IRR onlyRADB 672 100% 66
168.197.116.0/24 Valid Other IRR onlyRADB 671 100% 67
168.197.117.0/24 Valid Other IRR onlyRADB 671 100% 67
168.197.118.0/24 Valid Other IRR onlyRADB 671 100% 67
2804:34cc::/32 Valid Other IRR onlyRADB 636 100% 67

AS-SET

AS265481 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: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2804:34cc::/33No route object for it. A route object for 2804:34cc::/32 with origin AS265481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265481 in the RIR database for the space.636 of 636
Route object: none2804:34cc:8000::/33No route object for it. A route object for 2804:34cc::/32 with origin AS265481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265481 in the RIR database for the space.636 of 636
Route object: RIR168.197.116.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.197.119.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR168.197.116.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.197.117.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.197.118.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:34cc::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

168.197.116.0/23RADBValid
168.197.118.0/23RADBValid

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.