Skip to main content

AS269668

ASN269668

NAZASEG TELECOM

Registry

Authoritative registration data

AS number
269668
Name
ASN269668
Organisation
NAZASEG TELECOM
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

7

Total announced

14

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS269668
45.191.28.0/22 IPv4 /22 not checked
45.191.28.0/23 IPv4 /23 not checked
45.191.30.0/23 IPv4 /23 not checked
45.191.28.0/24 IPv4 /24 not checked
45.191.29.0/24 IPv4 /24 not checked
45.191.30.0/24 IPv4 /24 not checked
45.191.31.0/24 IPv4 /24 not checked
2804:6814::/32 IPv6 /32 not checked
2804:6814:8000::/33 IPv6 /33 not checked
2804:6814::/33 IPv6 /33 not checked
2804:6814:4000::/34 IPv6 /34 not checked
2804:6814:8000::/34 IPv6 /34 not checked
2804:6814::/34 IPv6 /34 not checked
2804:6814:c000::/34 IPv6 /34 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS269668
Address families
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS269668 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS269668 in AS paths

Observed upstreams
Families
AS266181 ASN266181 348 1,540
v4 v6
AS6939 HURRICANE 144 993
v4 v6
AS61582 ASN61582 74 300
v4
AS35280 F5 8 74
v4 v6
AS14840 ASN14840 2 48
v4 v6
AS6057 6057 3 25
v4 v6
AS52468 1 4
v6
AS53013 ASN53013 1 4
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS269668 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS264479 1 10
v4 v6
AS52873 ASN52873 1 9
v4 v6
AS52320 52320 1 5
v6
AS262427 1 5
v4
AS271253 1 5
v4
AS263152 1 4
v4

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.