bgpreport

Network · data from 2026-11-12

AS263355 GTR NET PROVEDOR DE INTERNET EIRELI

Registry name: AS263355 - GTR NET COMUNICACOES EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263355, 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.

132.255.104.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
191.37.68.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:14dc::/32 No ROA Other IRR onlyRADB, TC 339 53% 65
132.255.104.0/23 No ROA Other IRR onlyTC 135 20% 45
191.37.70.0/23 No ROA Other IRR onlyTC 135 20% 45
132.255.106.0/23 No ROA Other IRR onlyTC 132 20% 44
191.37.68.0/23 No ROA Other IRR onlyTC 132 20% 44

AS-SET

PeeringDB's irr_as_set for AS263355: AS263355:AS-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 (AS263355 isn't in the set, or no route object for AS263355 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 objectsAS263355 in itNot covered
AS263355:AS-ALL TC 1221 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 28 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none132.255.104.0/22No ROA covers it. Add a ROA for AS263355, maxLength 22.671 of 673
Route object: RIR132.255.104.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none191.37.68.0/22No ROA covers it. Add a ROA for AS263355, maxLength 22.671 of 673
Route object: RIR191.37.68.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:14dc::/32No ROA covers it. Add a ROA for AS263355, maxLength 32.339 of 636
Route object: RIR2804:14dc::/32Route object only in RADB, TC. Add it in the RIR database for the space.339 of 636
ROA: none132.255.104.0/23No ROA covers it. Add a ROA for AS263355, maxLength 23.135 of 673
Route object: RIR132.255.104.0/23Route object only in TC. Add it in the RIR database for the space.135 of 673
ROA: none191.37.70.0/23No ROA covers it. Add a ROA for AS263355, maxLength 23.135 of 673
Route object: RIR191.37.70.0/23Route object only in TC. Add it in the RIR database for the space.135 of 673
ROA: none132.255.106.0/23No ROA covers it. Add a ROA for AS263355, maxLength 23.132 of 673
Route object: RIR132.255.106.0/23Route object only in TC. Add it in the RIR database for the space.132 of 673
ROA: none191.37.68.0/23No ROA covers it. Add a ROA for AS263355, maxLength 23.132 of 673
Route object: RIR191.37.68.0/23Route object only in TC. Add it in the RIR database for the space.132 of 673

Route objects not announced

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

132.255.104.0/24TCNo ROA
132.255.105.0/24TCNo ROA
132.255.106.0/24TCNo ROA
132.255.107.0/24TCNo ROA
191.37.68.0/24TCNo ROA
191.37.69.0/24TCNo ROA
191.37.70.0/24TCNo ROA
191.37.71.0/24TCNo ROA
2804:14dc::/33TCNo ROA
2804:14dc::/34TCNo ROA
2804:14dc:4000::/34TCNo ROA
2804:14dc:8000::/33TCNo ROA
2804:14dc:8000::/34TCNo ROA
2804:14dc:c000::/34TCNo 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.