bgpreport

Network · data from 2026-11-12

AS262601 GTNET PROVEDOR DE ACESSO A INTERNET

Registry name: AS262601 - GtNet Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262601, 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.
177.75.241.0/24 Valid Nonecovered by 177.75.240.0/22 668 99% 67
177.75.240.0/20 Valid Other IRR onlyRADB, TC 672 100% 67
177.75.240.0/21 Valid Other IRR onlyTC 672 100% 67
177.75.240.0/22 Valid Other IRR onlyRADB 672 100% 67
177.75.244.0/22 Valid Other IRR onlyTC 672 100% 67
177.75.247.0/24 Valid Other IRR onlyRADB 672 100% 67
177.75.248.0/21 Valid Other IRR onlyTC 672 100% 67
177.75.240.0/24 Valid Other IRR onlyRADB 670 100% 67
177.75.248.0/22 Valid Other IRR onlyTC 670 100% 67
177.75.252.0/22 Valid Other IRR onlyTC 670 100% 67
2804:6ac::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:6ac:7f00::/40 Valid Other IRR onlyRADB 635 100% 69
2804:6ac:8000::/33 Valid Other IRR onlyRADB 635 100% 69

AS-SET

AS262601'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: none1
  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: none177.75.241.0/24No route object for it. A route object for 177.75.240.0/22 with origin AS262601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262601 in the RIR database for the space.668 of 673
Route object: RIR177.75.240.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.75.240.0/21Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.75.240.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.75.244.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.75.247.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.75.248.0/21Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.75.240.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR177.75.248.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.75.252.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:6ac::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6ac:7f00::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:6ac:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS262601 is announced.

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.