bgpreport

Network · data from 2026-11-12

AS263980 G3 Telecom EIRELI

Registry name: AS263980 - G3 Telecom, BR · PeeringDB

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

Announced routes

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

191.37.6.0/24 Valid Other IRR onlyRADB 672 100% 66
138.255.244.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
191.37.0.0/23 Valid Other IRR onlyRADB 670 100% 66
191.37.7.0/24 Valid Other IRR onlyALTDB, RADB 670 100% 66
45.176.252.0/22 Valid Other IRR onlyRADB 668 99% 66
45.232.200.0/22 Valid Other IRR onlyRADB 668 99% 66
45.232.244.0/22 Valid Other IRR onlyRADB 668 99% 66
45.239.166.0/23 Valid Other IRR onlyRADB 668 99% 66
168.227.16.0/22 Valid Other IRR onlyALTDB, RADB, TC 668 99% 66
170.245.120.0/22 Valid Other IRR onlyALTDB, RADB 668 99% 66
177.72.216.0/22 Valid Other IRR onlyRADB 668 99% 66
177.72.218.0/23 Valid Other IRR onlyRADB 668 99% 66
191.36.224.0/22 Valid Other IRR onlyRADB 668 99% 66
191.37.2.0/23 Valid Other IRR onlyRADB 668 99% 66
45.239.164.0/24 Valid Other IRR onlyRADB 665 99% 66
191.37.4.0/23 Valid Other IRR onlyRADB 665 99% 67
2804:28c8:8000::/33 Valid Other IRR onlyRADB 629 99% 67
2804:28c8::/32 Valid Other IRR onlyALTDB, RADB, TC 628 99% 67
2804:28c8::/33 Valid Other IRR onlyRADB 628 99% 67
2804:28c8::/34 Valid Other IRR onlyALTDB 628 99% 67
2804:28c8:4000::/34 Valid Other IRR onlyALTDB 628 99% 67
138.255.244.0/23 Valid Other IRR onlyALTDB, RADB 201 30% 54
138.255.246.0/23 Valid Other IRR onlyALTDB, RADB 201 30% 54
45.176.252.0/23 Valid Other IRR onlyRADB 200 30% 54
45.176.254.0/23 Valid Other IRR onlyRADB 200 30% 54
45.232.200.0/23 Valid Other IRR onlyALTDB, RADB 200 30% 54
45.232.202.0/23 Valid Other IRR onlyALTDB, RADB 200 30% 54
168.227.16.0/23 Valid Other IRR onlyALTDB, RADB 200 30% 54
168.227.18.0/23 Valid Other IRR onlyALTDB, RADB 200 30% 54
170.245.120.0/23 Valid Other IRR onlyALTDB, RADB 200 30% 54
170.245.122.0/23 Valid Other IRR onlyALTDB, RADB 200 30% 54
45.232.244.0/23 Valid Other IRR onlyRADB 199 30% 54
45.232.246.0/23 Valid Other IRR onlyRADB 199 30% 54
191.36.224.0/23 Valid Other IRR onlyRADB 199 30% 54
191.36.226.0/23 Valid Other IRR onlyRADB 199 30% 54
177.72.216.0/23 Valid Other IRR onlyRADB 3 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS263980: RADB::AS263980:AS-G3TELECOM. 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 (AS263980 isn't in the set, or no route object for AS263980 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 objectsAS263980 in itNot covered
RADB::AS263980:AS-G3TELECOM RADB 222545 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 75 are in fix.csv.

  • Route object: RIR36
  • Route object: not announced39
ChangePrefix or setDetailFull-table peers
Route object: RIR191.37.6.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR138.255.244.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR191.37.0.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR191.37.7.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.176.252.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.232.200.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.232.244.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.239.166.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR168.227.16.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR170.245.120.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.216.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR177.72.218.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR191.36.224.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR191.37.2.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR45.239.164.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR191.37.4.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:28c8:8000::/33Route object only in RADB. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:28c8::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:28c8::/33Route object only in RADB. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:28c8::/34Route object only in ALTDB. Add it in the RIR database for the space.628 of 636
Route object: RIR2804:28c8:4000::/34Route object only in ALTDB. Add it in the RIR database for the space.628 of 636
Route object: RIR138.255.244.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR138.255.246.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.201 of 673
Route object: RIR45.176.252.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR45.176.254.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR45.232.200.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR45.232.202.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR168.227.16.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR168.227.18.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR170.245.120.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR170.245.122.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR45.232.244.0/23Route object only in RADB. Add it in the RIR database for the space.199 of 673
Route object: RIR45.232.246.0/23Route object only in RADB. Add it in the RIR database for the space.199 of 673
Route object: RIR191.36.224.0/23Route object only in RADB. Add it in the RIR database for the space.199 of 673
Route object: RIR191.36.226.0/23Route object only in RADB. Add it in the RIR database for the space.199 of 673
Route object: RIR177.72.216.0/23Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

45.176.252.0/24RADBValid
45.176.253.0/24RADBValid
45.176.254.0/24RADBValid
45.176.255.0/24RADBValid
45.232.200.0/24RADBValid
45.232.201.0/24RADBValid
45.232.202.0/24RADBValid
45.232.203.0/24RADBValid
45.239.166.0/24RADBValid
45.239.167.0/24RADBValid
138.255.244.0/24RADBValid
138.255.245.0/24RADBValid
138.255.246.0/24RADBValid
138.255.247.0/24RADBValid
168.227.16.0/24RADBValid
168.227.17.0/24RADBValid
168.227.18.0/24RADBValid
168.227.19.0/24RADBValid
170.245.120.0/24RADBValid
170.245.121.0/24RADBValid
170.245.122.0/24RADBValid
170.245.123.0/24RADBValid
177.72.216.0/24RADBValid
177.72.217.0/24RADBValid
177.72.218.0/24RADBValid
177.72.219.0/24RADBValid
191.36.224.0/24RADBValid
191.36.225.0/24RADBValid
191.36.226.0/24RADBValid
191.36.227.0/24RADBValid
191.37.0.0/24RADBValid
191.37.1.0/24RADBValid
191.37.2.0/24RADBValid
191.37.3.0/24RADBValid
191.37.4.0/24RADBValid
191.37.5.0/24RADBValid
191.37.6.0/23RADBValid
2804:28c8:8000::/34ALTDBValid
2804:28c8:c000::/34ALTDBValid

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.