bgpreport

Network · data from 2026-11-12

AS270936 GTBA

Registry name: AS270936 - GTBA TELECOM LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270936, 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:73c4:6e00::/42 No ROA Nonecovered by 2804:73c4::/32 634 100% 67
2804:73c4:6e40::/42 No ROA Nonecovered by 2804:73c4::/32 634 100% 67
2804:73c4:6e80::/42 No ROA Nonecovered by 2804:73c4::/32 634 100% 67
2804:73c4:6ec0::/42 No ROA Nonecovered by 2804:73c4::/32 634 100% 67
2804:73c4::/32 No ROA Other IRR onlyRADB, TC 635 100% 69
190.103.154.0/23 Valid Nonecovered by 190.103.152.0/22 670 100% 66
190.103.152.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
190.103.152.0/23 Valid Other IRR onlyRADB 670 100% 66

AS-SET

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

  • ROA: none5
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:73c4:6e00::/42No ROA covers it. Add a ROA for AS270936, maxLength 42.634 of 636
Route object: none2804:73c4:6e00::/42No route object for it. A route object for 2804:73c4::/32 with origin AS270936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270936 in the RIR database for the space.634 of 636
ROA: none2804:73c4:6e40::/42No ROA covers it. Add a ROA for AS270936, maxLength 42.634 of 636
Route object: none2804:73c4:6e40::/42No route object for it. A route object for 2804:73c4::/32 with origin AS270936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270936 in the RIR database for the space.634 of 636
ROA: none2804:73c4:6e80::/42No ROA covers it. Add a ROA for AS270936, maxLength 42.634 of 636
Route object: none2804:73c4:6e80::/42No route object for it. A route object for 2804:73c4::/32 with origin AS270936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270936 in the RIR database for the space.634 of 636
ROA: none2804:73c4:6ec0::/42No ROA covers it. Add a ROA for AS270936, maxLength 42.634 of 636
Route object: none2804:73c4:6ec0::/42No route object for it. A route object for 2804:73c4::/32 with origin AS270936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270936 in the RIR database for the space.634 of 636
ROA: none2804:73c4::/32No ROA covers it. Add a ROA for AS270936, maxLength 32.635 of 636
Route object: RIR2804:73c4::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: none190.103.154.0/23No route object for it. A route object for 190.103.152.0/22 with origin AS270936 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270936 in the RIR database for the space.670 of 673
Route object: RIR190.103.152.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR190.103.152.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

190.103.152.0/24RADBValid
190.103.153.0/24RADBValid
190.103.154.0/24RADBValid
190.103.155.0/24RADBValid

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.