Network · data from 2026-11-12

AS268983 NAXOS TELECOM

Registry name: AS268983 - NAXOS TELECOM, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 66.7% with a route object

2IPv6 routes 100.0% RPKI valid · 50.0% 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

6Route objects not announced registered with origin AS268983, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268983, 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.177.138.0/24	Valid	Nonecovered by 45.177.138.0/23	667 99%	67
2804:5da0:d000::/40	Valid	Nonecovered by 2804:5da0:8000::/33	631 99%	67
45.177.137.0/24	Valid	Other IRR onlyRADB	664 99%	67
2804:5da0::/32	Valid	Other IRR onlyALTDB, RADB, TC	636 100%	67
38.246.87.0/24	Valid	RIR databaseARIN	670 100%	67

AS-SET

AS268983'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 10 are in fix.csv.

Route object: none2
Route object: RIR2
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
Route object: none	45.177.138.0/24	No route object for it. A route object for 45.177.138.0/23 with origin AS268983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268983 in the RIR database for the space.	667 of 673
Route object: none	2804:5da0:d000::/40	No route object for it. A route object for 2804:5da0:8000::/33 with origin AS268983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268983 in the RIR database for the space.	631 of 636
Route object: RIR	45.177.137.0/24	Route object only in RADB. Add it in the RIR database for the space.	664 of 673
Route object: RIR	2804:5da0::/32	Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.	636 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

45.177.138.0/24

No route object for it. A route object for 45.177.138.0/23 with origin AS268983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268983 in the RIR database for the space.

667 of 673

Route object: none

2804:5da0:d000::/40

No route object for it. A route object for 2804:5da0:8000::/33 with origin AS268983 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268983 in the RIR database for the space.

631 of 636

Route object: RIR

45.177.137.0/24

Route object only in RADB. Add it in the RIR database for the space.

664 of 673

Route object: RIR

2804:5da0::/32

Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.

636 of 636

Route objects not announced

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


45.177.136.0/22	ALTDB, RADB, TC	Valid
45.177.136.0/23	RADB	Valid
45.177.138.0/23	RADB	Valid
2804:5da0::/33	RADB	Valid
2804:5da0:8000::/33	RADB	Valid
2804:5da0:c000::/48	RADB	Valid

45.177.136.0/22

ALTDB, RADB, TC

Valid

45.177.136.0/23

RADB

Valid

45.177.138.0/23

RADB

Valid

2804:5da0::/33

RADB

Valid

2804:5da0:8000::/33

RADB

Valid

2804:5da0:c000::/48

RADB

Valid

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.