bgpreport

Network · data from 2026-11-12

AS264025 Arroba Banda Larga

Registry name: AS264025 - Arroba Banda Larga, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264025, 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:299c:1300::/40 Valid Nonecovered by 2804:299c::/33 634 100% 67
2804:299c:1400::/40 Valid Nonecovered by 2804:299c::/33 634 100% 67
2804:299c:1500::/40 Valid Nonecovered by 2804:299c::/33 634 100% 67
2804:299c:7e00::/40 Valid Nonecovered by 2804:299c::/33 634 100% 67
2804:299c:7f00::/40 Valid Nonecovered by 2804:299c::/33 634 100% 67
143.137.32.0/22 Valid Other IRR onlyTC 672 100% 67
168.197.56.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
143.137.32.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
143.137.34.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
168.197.56.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
168.197.56.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
168.197.58.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
2804:299c::/32 Valid Other IRR onlyRADB, TC 636 100% 67
2804:299c::/33 Valid Other IRR onlyRADB 634 100% 67
2804:299c:8000::/33 Valid Other IRR onlyRADB 634 100% 67
168.197.57.0/24 Valid Other IRR onlyTC 336 50% 63
168.197.58.0/24 Valid Other IRR onlyTC 336 50% 63
168.197.59.0/24 Valid Other IRR onlyTC 336 50% 63
143.137.32.0/24 Valid Other IRR onlyTC 206 31% 56
143.137.33.0/24 Valid Other IRR onlyTC 206 31% 56
143.137.34.0/24 Valid Other IRR onlyTC 206 31% 56
143.137.35.0/24 Valid Other IRR onlyTC 206 31% 56

AS-SET

PeeringDB's irr_as_set for AS264025: AS264025:AS-ARROBA-BANDA. 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 (AS264025 isn't in the set, or no route object for AS264025 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 objectsAS264025 in itNot covered
AS264025:AS-ARROBA-BANDA TC 1317 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 22 are in fix.csv.

  • Route object: none5
  • Route object: RIR17
ChangePrefix or setDetailFull-table peers
Route object: none2804:299c:1300::/40No route object for it. A route object for 2804:299c::/33 with origin AS264025 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264025 in the RIR database for the space.634 of 636
Route object: none2804:299c:1400::/40No route object for it. A route object for 2804:299c::/33 with origin AS264025 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264025 in the RIR database for the space.634 of 636
Route object: none2804:299c:1500::/40No route object for it. A route object for 2804:299c::/33 with origin AS264025 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264025 in the RIR database for the space.634 of 636
Route object: none2804:299c:7e00::/40No route object for it. A route object for 2804:299c::/33 with origin AS264025 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264025 in the RIR database for the space.634 of 636
Route object: none2804:299c:7f00::/40No route object for it. A route object for 2804:299c::/33 with origin AS264025 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264025 in the RIR database for the space.634 of 636
Route object: RIR143.137.32.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.197.56.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR143.137.32.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR143.137.34.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.197.56.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.197.56.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR168.197.58.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:299c::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:299c::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:299c:8000::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR168.197.57.0/24Route object only in TC. Add it in the RIR database for the space.336 of 673
Route object: RIR168.197.58.0/24Route object only in TC. Add it in the RIR database for the space.336 of 673
Route object: RIR168.197.59.0/24Route object only in TC. Add it in the RIR database for the space.336 of 673
Route object: RIR143.137.32.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR143.137.33.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR143.137.34.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
Route object: RIR143.137.35.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673

Route objects not announced

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