bgpreport

Network · data from 2026-11-12

AS268221 Fiber Banda Larga

Registry name: AS268221 - FIBER BANDA LARGA SERV DE CONEXAO INT E LIVROS DIG, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268221, 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:4dd0::/33 Valid Nonecovered by 2804:4dd0::/32 636 100% 67
2804:4dd0:8000::/33 Valid Nonecovered by 2804:4dd0::/32 636 100% 67
45.236.52.0/22 Valid Other IRR onlyALTDB, TC 672 100% 67
45.236.52.0/23 Valid Other IRR onlyALTDB 671 100% 67
45.236.54.0/23 Valid Other IRR onlyALTDB 671 100% 67
2804:4dd0::/32 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS268221: AS-268221. 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 (AS268221 isn't in the set, or no route object for AS268221 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 objectsAS268221 in itNot covered
AS-268221 ALTDB 114 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 6 are in fix.csv.

  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
Route object: none2804:4dd0::/33No route object for it. A route object for 2804:4dd0::/32 with origin AS268221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268221 in the RIR database for the space.636 of 636
Route object: none2804:4dd0:8000::/33No route object for it. A route object for 2804:4dd0::/32 with origin AS268221 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268221 in the RIR database for the space.636 of 636
Route object: RIR45.236.52.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.236.52.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.236.54.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:4dd0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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