bgpreport

Network · data from 2026-11-12

AS266399 NUDOZE TELECOMUNICACOES EIRELI

Registry name: AS266399 - NUDOZE TELECOMUNICACOES EIRELI, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
25Route objects not announced registered with origin AS266399, seen from no peer

Announced routes

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

170.81.92.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
2804:3740::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67
2804:3740::/33 Valid Other IRR onlyRADB, TC 350 55% 65
2804:3740::/34 Valid Other IRR onlyRADB, TC 350 55% 65
2804:3740:4000::/34 Valid Other IRR onlyRADB, TC 350 55% 65
2804:3740:8000::/33 Valid Other IRR onlyRADB, TC 350 55% 65
2804:3740:8000::/34 Valid Other IRR onlyRADB, TC 350 55% 65
2804:3740:c000::/34 Valid Other IRR onlyRADB, TC 350 55% 65
170.81.93.0/24 Valid Other IRR onlyRADB, TC 183 27% 53
170.81.92.0/24 Valid Other IRR onlyRADB, TC 182 27% 53
170.81.94.0/24 Valid Other IRR onlyRADB, TC 182 27% 53
170.81.95.0/24 Valid Other IRR onlyRADB, TC 182 27% 53
170.81.94.0/23 Valid Other IRR onlyRADB, TC 101 15% 38
170.81.92.0/23 Valid Other IRR onlyRADB, TC 100 15% 37

AS-SET

PeeringDB's irr_as_set for AS266399: AS266399. 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 (AS266399 isn't in the set, or no route object for AS266399 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 objectsAS266399 in itNot covered
AS266399 A single AS number, not a set: AS266399 (this network), 39 route objects.

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

  • Route object: RIR14
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
Route object: RIR170.81.92.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3740::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:3740::/33Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:3740::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:3740:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:3740:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:3740:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR2804:3740:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.350 of 636
Route object: RIR170.81.93.0/24Route object only in RADB, TC. Add it in the RIR database for the space.183 of 673
Route object: RIR170.81.92.0/24Route object only in RADB, TC. Add it in the RIR database for the space.182 of 673
Route object: RIR170.81.94.0/24Route object only in RADB, TC. Add it in the RIR database for the space.182 of 673
Route object: RIR170.81.95.0/24Route object only in RADB, TC. Add it in the RIR database for the space.182 of 673
Route object: RIR170.81.94.0/23Route object only in RADB, TC. Add it in the RIR database for the space.101 of 673
Route object: RIR170.81.92.0/23Route object only in RADB, TC. Add it in the RIR database for the space.100 of 673

Route objects not announced

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

2804:3740::/35RADBValid
2804:3740::/36RADBValid
2804:3740:1000::/36RADBValid
2804:3740:2000::/35RADBValid
2804:3740:2000::/36RADBValid
2804:3740:3000::/36RADBValid
2804:3740:4000::/35RADBValid
2804:3740:4000::/36RADBValid
2804:3740:5000::/36RADBValid
2804:3740:6000::/35RADBValid
2804:3740:6000::/36RADBValid
2804:3740:7000::/36RADBValid
2804:3740:8000::/35RADBValid
2804:3740:8000::/36RADBValid
2804:3740:9000::/36RADBValid
2804:3740:a000::/35RADBValid
2804:3740:a000::/36RADBValid
2804:3740:b000::/36RADBValid
2804:3740:c000::/35RADBValid
2804:3740:c000::/36RADBValid
2804:3740:d000::/36RADBValid
2804:3740:e000::/35RADBValid
2804:3740:e000::/36RADBValid
2804:3740:f000::/36RADBValid
2804:5858::/32ALTDBNo 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.