Network · data from 2026-11-12

AS269668 NAZASEG TELECOM

Registry name: AS269668 - NAZASEG TELECOM, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 42.9% with a route object

7IPv6 routes 100.0% RPKI valid · 42.9% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 8 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS269668, seen from no peer

Announced routes

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


2804:6814::/34	Valid	Nonecovered by 2804:6814::/33	330 52%	64
2804:6814:4000::/34	Valid	Nonecovered by 2804:6814::/33	330 52%	64
2804:6814:8000::/34	Valid	Nonecovered by 2804:6814:8000::/33	330 52%	64
2804:6814:c000::/34	Valid	Nonecovered by 2804:6814:8000::/33	330 52%	64
45.191.28.0/24	Valid	Nonecovered by 45.191.28.0/23	154 23%	51
45.191.29.0/24	Valid	Nonecovered by 45.191.28.0/23	154 23%	51
45.191.30.0/24	Valid	Nonecovered by 45.191.30.0/23	154 23%	51
45.191.31.0/24	Valid	Nonecovered by 45.191.30.0/23	154 23%	51
45.191.28.0/22	Valid	Other IRR onlyRADB, TC	671 100%	67
45.191.28.0/23	Valid	Other IRR onlyRADB	669 99%	67
45.191.30.0/23	Valid	Other IRR onlyRADB	669 99%	67
2804:6814::/32	Valid	Other IRR onlyTC	634 100%	67
2804:6814::/33	Valid	Other IRR onlyRADB	634 100%	67
2804:6814:8000::/33	Valid	Other IRR onlyRADB	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS269668: AS-269668-NAZASEG. 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 (AS269668 isn't in the set, or no route object for AS269668 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.

Name	Database	ASNs	Sets	Route objects	AS269668 in it	Not covered
AS-269668-NAZASEG	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS269668 in it

Not covered

AS-269668-NAZASEG

In no IRR database read today.

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

Route object: none8
Route object: RIR6
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:6814::/34	No route object for it. A route object for 2804:6814::/33 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	330 of 636
Route object: none	2804:6814:4000::/34	No route object for it. A route object for 2804:6814::/33 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	330 of 636
Route object: none	2804:6814:8000::/34	No route object for it. A route object for 2804:6814:8000::/33 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	330 of 636
Route object: none	2804:6814:c000::/34	No route object for it. A route object for 2804:6814:8000::/33 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	330 of 636
Route object: none	45.191.28.0/24	No route object for it. A route object for 45.191.28.0/23 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	154 of 673
Route object: none	45.191.29.0/24	No route object for it. A route object for 45.191.28.0/23 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	154 of 673
Route object: none	45.191.30.0/24	No route object for it. A route object for 45.191.30.0/23 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	154 of 673
Route object: none	45.191.31.0/24	No route object for it. A route object for 45.191.30.0/23 with origin AS269668 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269668 in the RIR database for the space.	154 of 673
Route object: RIR	45.191.28.0/22	Route object only in RADB, TC. Add it in the RIR database for the space.	671 of 673
Route object: RIR	45.191.28.0/23	Route object only in RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	45.191.30.0/23	Route object only in RADB. Add it in the RIR database for the space.	669 of 673
Route object: RIR	2804:6814::/32	Route object only in TC. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:6814::/33	Route object only in RADB. Add it in the RIR database for the space.	634 of 636
Route object: RIR	2804:6814:8000::/33	Route object only in RADB. Add it in the RIR database for the space.	634 of 636
AS-SET: not found	AS-269668-NAZASEG	PeeringDB names AS-269668-NAZASEG; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:6814::/34

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

330 of 636

Route object: none

2804:6814:4000::/34

330 of 636

Route object: none

2804:6814:8000::/34

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

330 of 636

Route object: none

2804:6814:c000::/34

330 of 636

Route object: none

45.191.28.0/24

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

154 of 673

Route object: none

45.191.29.0/24

154 of 673

Route object: none

45.191.30.0/24

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

154 of 673

Route object: none

45.191.31.0/24

154 of 673

Route object: RIR

45.191.28.0/22

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

671 of 673

Route object: RIR

45.191.28.0/23

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

669 of 673

Route object: RIR

45.191.30.0/23

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

669 of 673

Route object: RIR

2804:6814::/32

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

634 of 636

Route object: RIR

2804:6814::/33

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

634 of 636

Route object: RIR

2804:6814:8000::/33

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

634 of 636

AS-SET: not found

AS-269668-NAZASEG

PeeringDB names AS-269668-NAZASEG; no IRR database read has it.

Route objects not announced

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