Skip to main content

AS52657

ASN52657

NORTE TELECOMUNICAÇÕES SERVIÇOS DE INTERNET LTDA

Registry

Authoritative registration data

AS number
52657
Name
ASN52657
Organisation
NORTE TELECOMUNICAÇÕES SERVIÇOS DE INTERNET LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

17

IPv6 prefixes

20

Total announced

37

Announced prefixes

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

Prefixes announced by AS52657
177.104.240.0/20 IPv4 /20 RPKI valid
177.104.240.0/24 IPv4 /24 RPKI valid
177.104.241.0/24 IPv4 /24 RPKI valid
177.104.242.0/24 IPv4 /24 RPKI valid
177.104.243.0/24 IPv4 /24 RPKI valid
177.104.244.0/24 IPv4 /24 RPKI valid
177.104.245.0/24 IPv4 /24 not checked
177.104.246.0/24 IPv4 /24 RPKI valid
177.104.247.0/24 IPv4 /24 RPKI valid
177.104.248.0/24 IPv4 /24 not checked
177.104.249.0/24 IPv4 /24 not checked
177.104.250.0/24 IPv4 /24 RPKI valid
177.104.251.0/24 IPv4 /24 not checked
177.104.252.0/24 IPv4 /24 RPKI valid
177.104.253.0/24 IPv4 /24 RPKI valid
177.104.254.0/24 IPv4 /24 not checked
177.104.255.0/24 IPv4 /24 not checked
2804:5bcc::/32 IPv6 /32 RPKI valid
2804:5bcc:1000::/36 IPv6 /36 RPKI valid
2804:5bcc:2000::/36 IPv6 /36 RPKI valid
2804:5bcc:3000::/36 IPv6 /36 RPKI valid
2804:5bcc:4000::/36 IPv6 /36 RPKI valid
2804:5bcc:5000::/36 IPv6 /36 RPKI valid
2804:5bcc:6000::/36 IPv6 /36 RPKI valid
2804:5bcc:7000::/36 IPv6 /36 RPKI valid
2804:5bcc:8000::/36 IPv6 /36 RPKI valid
2804:5bcc:9000::/36 IPv6 /36 RPKI valid
2804:5bcc::/36 IPv6 /36 RPKI valid
2804:5bcc:a000::/36 IPv6 /36 RPKI valid
2804:5bcc:b000::/36 IPv6 /36 RPKI valid
2804:5bcc:c000::/36 IPv6 /36 RPKI valid
2804:5bcc:d000::/36 IPv6 /36 RPKI valid
2804:5bcc:e000::/36 IPv6 /36 not checked
2804:5bcc:f000::/36 IPv6 /36 not checked
2804:5bcc:6e00::/40 IPv6 /40 RPKI valid
2804:5bcc:6f00::/40 IPv6 /40 RPKI valid
2804:5bcc:7100::/40 IPv6 /40 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS52657 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS52657 in AS paths

Observed upstreams
Families
AS4230 ASN4230 987 5,588
v4 v6
AS28598 ASN28598 691 3,412
v4 v6
AS6939 HURRICANE 53 1,217
v4 v6
AS10429 ASN10429 167 871
v4 v6
AS26615 ASN26615 206 641
v4 v6
AS6057 6057 3 69
v4 v6
AS61626 ASN61626 1 32
v4 v6
AS18881 ASN18881 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

8 networks seen after AS52657 in AS paths

Observed downstreams
Families
AS264985 ASN264985 222 1,362
v4 v6
AS268324 ASN268324 285 1,220
v4 v6
AS267954 ASN267954 163 1,119
v4
AS262727 ASN262727 160 825
v4
AS266422 ASN266422 147 671
v4
AS275749 ASN275749 381 519
v4 v6
AS273532 ASN273532 156 345
v4
AS28590 ASN28590 1 1
v4

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 1 102
v4 v6
AS24482 SGGS-AS-AP 1 64
v4 v6
AS264479 ASN264479 1 34
v4 v6
AS61573 ASN61573 1 33
v4 v6
AS6424 EDGOO 1 32
v4 v6
AS22548 ASN22548 1 32
v4 v6
AS28624 ASN28624 1 32
v4 v6
AS35280 F5 1 32
v4 v6
AS51185 MAINSTREAMING-AS 1 32
v4 v6
AS263152 ASN263152 1 32
v4 v6
AS263237 263237 1 32
v4 v6
AS28634 ASN28634 1 24
v4
AS271253 ASN271253 1 24
v4
AS199524 GCORE 1 23
v4 v6
AS262427 ASN262427 1 14
v4
AS60503 FNXTEC 1 6
v4
AS37721 ORG-VTS1-AFRINIC 1 1
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.