bgpreport

Network · data from 2026-11-12

AS266850 NODO ZERO BAHIA

Registry name: AS266850 - NODO ZERO BAHIA SRL, AR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 0.0% with a route object
1IPv6 routes 100.0% RPKI valid · 0.0% 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 AS266850, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266850, 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.
45.239.117.0/24 Valid None 670 100% 67
45.239.116.0/24 Valid None 669 99% 66
45.239.118.0/24 Valid None 669 99% 66
45.239.119.0/24 Valid None 669 99% 66
2803:82a0:2000::/36 Valid None 636 100% 67

AS-SET

AS266850'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 5 are in fix.csv.

  • Route object: none5
ChangePrefix or setDetailFull-table peers
Route object: none45.239.117.0/24No route object for it. Add a route object with origin AS266850 in the RIR database for the space.670 of 673
Route object: none45.239.116.0/24No route object for it. Add a route object with origin AS266850 in the RIR database for the space.669 of 673
Route object: none45.239.118.0/24No route object for it. Add a route object with origin AS266850 in the RIR database for the space.669 of 673
Route object: none45.239.119.0/24No route object for it. Add a route object with origin AS266850 in the RIR database for the space.669 of 673
Route object: none2803:82a0:2000::/36No route object for it. Add a route object with origin AS266850 in the RIR database for the space.636 of 636

Route objects not announced

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