bgpreport

Network · data from 2026-11-12

AS264111 RedeBr Telecom

Registry name: AS264111 - RedeBr Telecom, BR · PeeringDB

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

Announced routes

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

38.3.248.0/21 No ROA None 668 99% 67
138.97.12.0/22 No ROA Other IRR onlyRADB, TC 668 99% 67
168.196.88.0/22 No ROA Other IRR onlyRADB, TC 668 99% 67
38.51.152.0/24 No ROA Other IRR onlyRADB 666 99% 67
2804:229c::/32 No ROA Other IRR onlyRADB, TC 628 99% 67
2804:229c::/33 No ROA Other IRR onlyTC 354 56% 65
2804:229c:8000::/33 No ROA Other IRR onlyTC 354 56% 65
138.97.12.0/23 No ROA Other IRR onlyRADB, TC 203 30% 56
138.97.14.0/23 No ROA Other IRR onlyRADB, TC 202 30% 56
168.196.88.0/23 No ROA Other IRR onlyRADB, TC 202 30% 56
168.196.90.0/23 No ROA Other IRR onlyRADB, TC 202 30% 56

AS-SET

PeeringDB's irr_as_set for AS264111: AS264111:AS-ALL. 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 (AS264111 isn't in the set, or no route object for AS264111 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 objectsAS264111 in itNot covered
AS264111:AS-ALL TC 6884 Yes 1

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 34 are in fix.csv.

  • ROA: none11
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none38.3.248.0/21No ROA covers it. Add a ROA for AS264111, maxLength 21.668 of 673
Route object: none38.3.248.0/21No route object for it. Add a route object with origin AS264111 in the RIR database for the space.668 of 673
ROA: none138.97.12.0/22No ROA covers it. Add a ROA for AS264111, maxLength 22.668 of 673
Route object: RIR138.97.12.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none168.196.88.0/22No ROA covers it. Add a ROA for AS264111, maxLength 22.668 of 673
Route object: RIR168.196.88.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none38.51.152.0/24No ROA covers it. Add a ROA for AS264111, maxLength 24.666 of 673
Route object: RIR38.51.152.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none2804:229c::/32No ROA covers it. Add a ROA for AS264111, maxLength 32.628 of 636
Route object: RIR2804:229c::/32Route object only in RADB, TC. Add it in the RIR database for the space.628 of 636
ROA: none2804:229c::/33No ROA covers it. Add a ROA for AS264111, maxLength 33.354 of 636
Route object: RIR2804:229c::/33Route object only in TC. Add it in the RIR database for the space.354 of 636
ROA: none2804:229c:8000::/33No ROA covers it. Add a ROA for AS264111, maxLength 33.354 of 636
Route object: RIR2804:229c:8000::/33Route object only in TC. Add it in the RIR database for the space.354 of 636
ROA: none138.97.12.0/23No ROA covers it. Add a ROA for AS264111, maxLength 23.203 of 673
Route object: RIR138.97.12.0/23Route object only in RADB, TC. Add it in the RIR database for the space.203 of 673
ROA: none138.97.14.0/23No ROA covers it. Add a ROA for AS264111, maxLength 23.202 of 673
Route object: RIR138.97.14.0/23Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
ROA: none168.196.88.0/23No ROA covers it. Add a ROA for AS264111, maxLength 23.202 of 673
Route object: RIR168.196.88.0/23Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
ROA: none168.196.90.0/23No ROA covers it. Add a ROA for AS264111, maxLength 23.202 of 673
Route object: RIR168.196.90.0/23Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673

Route objects not announced

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

138.97.12.0/24TCNo ROA
138.97.13.0/24TCNo ROA
138.97.14.0/24TCNo ROA
138.97.15.0/24TCNo ROA
168.196.88.0/24TCNo ROA
168.196.89.0/24TCNo ROA
168.196.90.0/24TCNo ROA
168.196.91.0/24TCNo ROA
2804:229c::/34TCNo ROA
2804:229c:4000::/34TCNo ROA
2804:229c:8000::/34TCNo ROA
2804:229c:c000::/34TCNo ROA

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.