Skip to main content

AS269139

ASN269139

AN TELECOM

Registry

Authoritative registration data

AS number
269139
Name
ASN269139
Organisation
AN TELECOM
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS269139
45.180.84.0/22 IPv4 /22 not checked
45.180.84.0/23 IPv4 /23 not checked
45.180.86.0/23 IPv4 /23 not checked
2804:6000::/32 IPv6 /32 not checked

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

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS269139 in AS paths

Observed upstreams
Families
AS52872 ASN52872 2,732 5,622
v4 v6
AS265336 ASN265336 656 1,002
v4 v6
AS14840 ASN14840 3 28
v4 v6

No rows match “”.

Showing of

Observed downstreams

11 networks seen after AS269139 in AS paths

Observed downstreams
Families
AS270293 743 1,589
v4 v6
AS265336 ASN265336 470 1,444
v4 v6
AS269117 544 735
v4 v6
AS270534 264 340
v4
AS14840 ASN14840 86 316
v4
AS269304 158 225
v4 v6
AS270488 157 210
v4
AS268199 ASN268199 153 197
v4
AS268714 77 102
v4
AS52696 ASN52696 56 69
v4
AS52872 ASN52872 2 2
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS52873 ASN52873 3 7
v4 v6
AS28624 ASN28624 3 4
v6
AS271253 ASN271253 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.