bgpreport

Network · data from 2026-11-12

AS264517 GM NETWORK TELECOMUNICACOES

Registry name: AS264517 - GM NETWORK TELECOMUNICACOES LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264517, 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:20dc::/33 Valid Nonecovered by 2804:20dc::/32 633 100% 67
2804:20dc:8000::/33 Valid Nonecovered by 2804:20dc::/32 633 100% 67
2804:20dc:b000::/36 Valid Nonecovered by 2804:20dc::/32 632 99% 67
132.255.172.0/22 Valid Other IRR onlyRADB 672 100% 67
138.117.164.0/22 Valid Other IRR onlyRADB 672 100% 67
132.255.173.0/24 Valid Other IRR onlyRADB 670 100% 67
132.255.174.0/24 Valid Other IRR onlyRADB 670 100% 67
138.117.165.0/24 Valid Other IRR onlyRADB 670 100% 67
2804:20dc::/32 Valid Other IRR onlyRADB 633 100% 69
132.255.172.0/23 Valid Other IRR onlyRADB 97 14% 39
132.255.174.0/23 Valid Other IRR onlyRADB 97 14% 39
138.117.164.0/23 Valid Other IRR onlyRADB 97 14% 39
138.117.166.0/23 Valid Other IRR onlyRADB 97 14% 39
132.255.172.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
132.255.175.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
138.117.164.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
138.117.166.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2
138.117.167.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS264517: AS-GMNETWORK-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS264517 isn't in the set, or no route object for AS264517 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS264517 in itNot covered
AS-GMNETWORK-ALL RADB 103130 Yes 0

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 19 are in fix.csv.

  • Route object: none3
  • Route object: RIR15
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2804:20dc::/33No route object for it. A route object for 2804:20dc::/32 with origin AS264517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264517 in the RIR database for the space.633 of 636
Route object: none2804:20dc:8000::/33No route object for it. A route object for 2804:20dc::/32 with origin AS264517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264517 in the RIR database for the space.633 of 636
Route object: none2804:20dc:b000::/36No route object for it. A route object for 2804:20dc::/32 with origin AS264517 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264517 in the RIR database for the space.632 of 636
Route object: RIR132.255.172.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.117.164.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR132.255.173.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR132.255.174.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR138.117.165.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:20dc::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR132.255.172.0/23Route object only in RADB. Add it in the RIR database for the space.97 of 673
Route object: RIR132.255.174.0/23Route object only in RADB. Add it in the RIR database for the space.97 of 673
Route object: RIR138.117.164.0/23Route object only in RADB. Add it in the RIR database for the space.97 of 673
Route object: RIR138.117.166.0/23Route object only in RADB. Add it in the RIR database for the space.97 of 673
Route object: RIR132.255.172.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR132.255.175.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR138.117.164.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR138.117.166.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: RIR138.117.167.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:20dc::/34RADBValid

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.