Skip to main content

AS269089

ASN269089

Hilan Telecom Ltda

Registry

Authoritative registration data

AS number
269089
Name
ASN269089
Organisation
Hilan Telecom Ltda
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS269089
45.179.144.0/22 IPv4 /22 not checked
45.179.144.0/23 IPv4 /23 not checked
45.179.146.0/23 IPv4 /23 not checked
45.179.144.0/24 IPv4 /24 not checked
45.179.145.0/24 IPv4 /24 not checked
45.179.146.0/24 IPv4 /24 not checked
45.179.147.0/24 IPv4 /24 not checked
2804:5f48::/32 IPv6 /32 RPKI not found

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 AS269089
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 200,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 200,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 AS269089 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS269089 in AS paths

Observed upstreams
Families
AS52573 ASN52573 242 1,435
v4 v6
AS1031 PEER1-1031 180 568
v4 v6
AS266167 ASN266167 354 561
v4 v6
AS6939 HURRICANE 159 314
v4 v6
AS3303 SWISSCOM 24 84
v4
AS33891 CORE-BACKBONE 13 65
v4 v6
AS6057 6057 4 22
v4 v6
AS24961 MYLOC-AS 5 20
v4
AS137409 GSLNETWORKS-AS-AP 4 16
v4
AS22356 ASN22356 2 12
v4
AS61626 ASN61626 1 3
v6
AS37468 ORG-AC4-AFRINIC 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS269089 in AS paths

Observed downstreams
Families
AS266114 ASN266114 378 985
v4 v6
AS271637 ASN271637 53 95
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

21 adjacencies that may be an artefact of collector peering

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.