bgpreport

Network · data from 2026-11-12

AS264120 G20 Telecomunicacoes LTDA

Registry name: AS264120 - G20 Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264120, 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:22c0:f700::/40 Valid Nonecovered by 2804:22c0:f000::/36 635 100% 69
2804:22c0:f800::/40 Valid Nonecovered by 2804:22c0:f000::/36 635 100% 69
2804:22c0:f900::/40 Valid Nonecovered by 2804:22c0:f000::/36 635 100% 69
2804:22c0:fb00::/40 Valid Nonecovered by 2804:22c0:f000::/36 635 100% 69
138.97.40.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
138.97.40.0/23 Valid Other IRR onlyTC 672 100% 67
138.97.42.0/23 Valid Other IRR onlyTC 672 100% 67
138.97.42.0/24 Valid Other IRR onlyTC 672 100% 67
177.12.128.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
177.12.128.0/23 Valid Other IRR onlyTC 672 100% 67
177.12.128.0/24 Valid Other IRR onlyTC 672 100% 67
177.12.130.0/23 Valid Other IRR onlyTC 672 100% 67
177.12.131.0/24 Valid Other IRR onlyTC 672 100% 67
181.232.224.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
181.232.224.0/24 Valid Other IRR onlyTC 672 100% 67
189.89.240.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
191.160.44.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
191.160.44.0/23 Valid Other IRR onlyTC 672 100% 67
191.160.44.0/24 Valid Other IRR onlyTC 672 100% 67
191.160.45.0/24 Valid Other IRR onlyTC 672 100% 67
191.160.46.0/23 Valid Other IRR onlyTC 672 100% 67
191.160.46.0/24 Valid Other IRR onlyTC 672 100% 67
138.97.40.0/24 Valid Other IRR onlyTC 670 100% 67
138.97.41.0/24 Valid Other IRR onlyTC 670 100% 67
138.97.43.0/24 Valid Other IRR onlyTC 670 100% 67
177.12.129.0/24 Valid Other IRR onlyTC 670 100% 67
177.12.130.0/24 Valid Other IRR onlyTC 670 100% 67
181.232.225.0/24 Valid Other IRR onlyTC 670 100% 67
191.160.47.0/24 Valid Other IRR onlyTC 670 100% 67
2804:22c0::/32 Valid Other IRR onlyRADB, TC 635 100% 69
2804:22c0::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0::/48 Valid Other IRR onlyTC 635 100% 69
2804:22c0:1000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:2000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:3000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:4000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:5000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:6000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:7000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:8000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:9000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:a000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:b000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:c000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:d000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:e000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f000::/36 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f000::/40 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f100::/40 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f200::/40 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f400::/40 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f500::/40 Valid Other IRR onlyTC 635 100% 69
2804:22c0:f600::/40 Valid Other IRR onlyTC 635 100% 69
2804:22c0:fa00::/40 Valid Other IRR onlyTC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS264120: AS264120:AS-G20. 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 (AS264120 isn't in the set, or no route object for AS264120 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 objectsAS264120 in itNot covered
AS264120:AS-G20 TC 283548 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 54 are in fix.csv.

  • Route object: none4
  • Route object: RIR50
ChangePrefix or setDetailFull-table peers
Route object: none2804:22c0:f700::/40No route object for it. A route object for 2804:22c0:f000::/36 with origin AS264120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264120 in the RIR database for the space.635 of 636
Route object: none2804:22c0:f800::/40No route object for it. A route object for 2804:22c0:f000::/36 with origin AS264120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264120 in the RIR database for the space.635 of 636
Route object: none2804:22c0:f900::/40No route object for it. A route object for 2804:22c0:f000::/36 with origin AS264120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264120 in the RIR database for the space.635 of 636
Route object: none2804:22c0:fb00::/40No route object for it. A route object for 2804:22c0:f000::/36 with origin AS264120 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264120 in the RIR database for the space.635 of 636
Route object: RIR138.97.40.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.97.40.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.97.42.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.97.42.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.12.128.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.12.128.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.12.128.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.12.130.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.12.131.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR181.232.224.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR181.232.224.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.89.240.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.44.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.44.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.45.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.46.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.160.46.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.97.40.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR138.97.41.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR138.97.43.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.12.129.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.12.130.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR181.232.225.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR191.160.47.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:22c0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0::/48Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:1000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:2000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:3000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:4000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:5000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:6000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:7000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:8000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:9000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:a000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:b000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:c000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:d000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:e000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f000::/36Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f000::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f100::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f200::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f400::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f500::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:f600::/40Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:22c0:fa00::/40Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS264120 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.