bgpreport

Network · data from 2026-11-12

AS266551 CONEXAOBA PROVEDOR DE INTERNET

Registry name: AS266551 - CONEXAOBA PROVEDOR DE INTERNET, BR · PeeringDB

7IPv4 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS266551, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266551, 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.
160.238.224.0/22 Valid Other IRR onlyBBOI, NTTCOM, RADB, TC 672 100% 67
160.238.224.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
160.238.226.0/23 Valid Other IRR onlyRADB, TC 672 100% 67
160.238.224.0/24 Valid Other IRR onlyRADB 670 100% 67
160.238.225.0/24 Valid Other IRR onlyRADB 670 100% 67
160.238.226.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
160.238.227.0/24 Valid Other IRR onlyRADB 668 99% 67
2804:3dc0::/32 Valid Other IRR onlyBBOI, NTTCOM, RADB, TC 636 100% 67
2804:3dc0::/34 Valid Other IRR onlyTC 636 100% 67
2804:3dc0:4000::/34 Valid Other IRR onlyTC 636 100% 67
2804:3dc0:8000::/34 Valid Other IRR onlyTC 636 100% 67
2804:3dc0:c000::/34 Valid Other IRR onlyTC 636 100% 67

AS-SET

AS266551's PeeringDB record names no AS-SET.

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

  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: RIR160.238.224.0/22Route object only in BBOI, NTTCOM, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR160.238.224.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR160.238.226.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR160.238.224.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR160.238.225.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR160.238.226.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR160.238.227.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:3dc0::/32Route object only in BBOI, NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:3dc0::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:3dc0:4000::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:3dc0:8000::/34Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:3dc0:c000::/34Route object only in TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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