bgpreport

Network · data from 2026-11-12

AS262769 AVANZA TELECOM LTDA

Registry name: AS262769 - AVANZA TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262769, 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.128.96.0/23 Valid Nonecovered by 177.128.96.0/21 670 100% 67
177.128.100.0/23 Valid Nonecovered by 177.128.96.0/21 670 100% 67
177.128.102.0/23 Valid Nonecovered by 177.128.96.0/21 670 100% 67
177.124.164.0/23 Valid Nonecovered by 177.124.164.0/22 668 99% 67
177.124.164.0/24 Valid Nonecovered by 177.124.164.0/22 668 99% 66
177.124.166.0/23 Valid Nonecovered by 177.124.164.0/22 668 99% 67
177.128.98.0/23 Valid Nonecovered by 177.128.96.0/21 668 99% 67
2804:224c:4000::/36 Valid Nonecovered by 2804:224c::/32 635 100% 69
2804:224c::/34 Valid Nonecovered by 2804:224c::/32 76 12% 29
2804:224c:2000::/37 Valid Nonecovered by 2804:224c:2000::/36 76 12% 29
2804:224c:2800::/37 Valid Nonecovered by 2804:224c:2000::/36 76 12% 29
2804:224c:4000::/34 Valid Nonecovered by 2804:224c::/32 76 12% 29
2804:224c:8000::/34 Valid Nonecovered by 2804:224c::/32 76 12% 29
2804:224c:c000::/34 Valid Nonecovered by 2804:224c::/32 76 12% 29
2804:224c:7800::/37 Valid Nonecovered by 2804:224c::/32 24 4%low visibility 11
138.59.92.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
168.181.156.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
177.73.76.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
177.124.164.0/22 Valid Other IRR onlyRADB 672 100% 66
177.128.96.0/21 Valid Other IRR onlyRADB 672 100% 66
177.155.144.0/20 Valid Other IRR onlyRADB, TC 672 100% 66
177.155.144.0/21 Valid Other IRR onlyRADB, TC 672 100% 66
177.155.144.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
177.155.148.0/22 Valid Other IRR onlyTC 672 100% 66
177.155.152.0/21 Valid Other IRR onlyTC 672 100% 66
177.155.156.0/22 Valid Other IRR onlyTC 672 100% 66
186.232.56.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
138.59.94.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
138.59.94.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
168.181.158.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
177.73.78.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
177.155.144.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
177.155.144.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
186.232.56.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
186.232.57.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
138.59.92.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
177.155.152.0/22 Valid Other IRR onlyTC 670 100% 66
168.181.156.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
177.73.76.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
177.155.158.0/23 Valid Other IRR onlyTC 669 99% 67
186.232.58.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
2804:224c::/32 Valid Other IRR onlyRADB, TC 636 100% 69
177.155.154.0/23 Valid Other IRR onlyTC 91 14% 30
177.155.156.0/23 Valid Other IRR onlyTC 90 13% 30
177.155.146.0/23 Valid Other IRR onlyTC 89 13% 30
177.155.148.0/23 Valid Other IRR onlyTC 89 13% 30
177.155.150.0/23 Valid Other IRR onlyTC 89 13% 30
2804:224c:2000::/36 Valid Other IRR onlyTC 80 13% 29

AS-SET

PeeringDB's irr_as_set for AS262769: AS-GEEKNET-BR. 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 (AS262769 isn't in the set, or no route object for AS262769 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 objectsAS262769 in itNot covered
AS-GEEKNET-BR ALTDB 193837 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 78 are in fix.csv.

  • Route object: none15
  • Route object: RIR33
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
Route object: none177.128.96.0/23No route object for it. A route object for 177.128.96.0/21 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.670 of 673
Route object: none177.128.100.0/23No route object for it. A route object for 177.128.96.0/21 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.670 of 673
Route object: none177.128.102.0/23No route object for it. A route object for 177.128.96.0/21 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.670 of 673
Route object: none177.124.164.0/23No route object for it. A route object for 177.124.164.0/22 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.668 of 673
Route object: none177.124.164.0/24No route object for it. A route object for 177.124.164.0/22 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.668 of 673
Route object: none177.124.166.0/23No route object for it. A route object for 177.124.164.0/22 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.668 of 673
Route object: none177.128.98.0/23No route object for it. A route object for 177.128.96.0/21 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.668 of 673
Route object: none2804:224c:4000::/36No route object for it. A route object for 2804:224c::/32 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.635 of 636
Route object: none2804:224c::/34No route object for it. A route object for 2804:224c::/32 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.76 of 636
Route object: none2804:224c:2000::/37No route object for it. A route object for 2804:224c:2000::/36 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.76 of 636
Route object: none2804:224c:2800::/37No route object for it. A route object for 2804:224c:2000::/36 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.76 of 636
Route object: none2804:224c:4000::/34No route object for it. A route object for 2804:224c::/32 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.76 of 636
Route object: none2804:224c:8000::/34No route object for it. A route object for 2804:224c::/32 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.76 of 636
Route object: none2804:224c:c000::/34No route object for it. A route object for 2804:224c::/32 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.76 of 636
Route object: none2804:224c:7800::/37No route object for it. A route object for 2804:224c::/32 with origin AS262769 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262769 in the RIR database for the space.24 of 636
Route object: RIR138.59.92.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.181.156.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.73.76.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.124.164.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.128.96.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.155.144.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.155.144.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.155.144.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.155.148.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.155.152.0/21Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.155.156.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR186.232.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.59.94.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.59.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.181.158.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.73.78.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.155.144.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.155.144.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.232.56.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.232.57.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.59.92.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.155.152.0/22Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR168.181.156.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.73.76.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.155.158.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR186.232.58.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:224c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR177.155.154.0/23Route object only in TC. Add it in the RIR database for the space.91 of 673
Route object: RIR177.155.156.0/23Route object only in TC. Add it in the RIR database for the space.90 of 673
Route object: RIR177.155.146.0/23Route object only in TC. Add it in the RIR database for the space.89 of 673
Route object: RIR177.155.148.0/23Route object only in TC. Add it in the RIR database for the space.89 of 673
Route object: RIR177.155.150.0/23Route object only in TC. Add it in the RIR database for the space.89 of 673
Route object: RIR2804:224c:2000::/36Route object only in TC. Add it in the RIR database for the space.80 of 636

Route objects not announced

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

138.59.92.0/24RADB, TCValid
138.59.93.0/24RADB, TCValid
138.59.95.0/24RADB, TCValid
168.181.156.0/24RADB, TCValid
168.181.157.0/24RADB, TCValid
168.181.158.0/24RADB, TCValid
168.181.159.0/24RADB, TCValid
177.73.76.0/24RADB, TCValid
177.73.77.0/24RADB, TCValid
177.73.78.0/24RADB, TCValid
177.73.79.0/24RADB, TCValid
177.155.145.0/24TCValid
177.155.146.0/24TCValid
177.155.147.0/24TCValid
177.155.148.0/24TCValid
177.155.149.0/24TCValid
177.155.150.0/24TCValid
177.155.151.0/24TCValid
177.155.152.0/23TCValid
177.155.152.0/24TCValid
177.155.153.0/24TCValid
177.155.154.0/24TCValid
177.155.155.0/24TCValid
177.155.156.0/24TCValid
177.155.157.0/24TCValid
177.155.158.0/24TCValid
177.155.159.0/24TCValid
186.232.56.0/23RADB, TCValid
186.232.58.0/24RADB, TCValid
186.232.59.0/24RADB, TCValid

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.