Skip to main content

AS267963

ASN267963

HAYAN TELECOM

Registry

Authoritative registration data

AS number
267963
Name
ASN267963
Organisation
HAYAN TELECOM
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

5

Total announced

10

Announced prefixes

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

Prefixes announced by AS267963
45.166.150.0/23 IPv4 /23 not checked
45.166.148.0/24 IPv4 /24 not checked
45.166.149.0/24 IPv4 /24 not checked
45.166.150.0/24 IPv4 /24 not checked
45.166.151.0/24 IPv4 /24 not checked
2804:55e4::/33 IPv6 /33 not checked
2804:55e4:4000::/34 IPv6 /34 not checked
2804:55e4::/34 IPv6 /34 not checked
2804:55e4:6000::/35 IPv6 /35 not checked
2804:55e4:c000::/35 IPv6 /35 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 AS267963 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS267963 in AS paths

Observed upstreams
Families
AS263661 ASN263661 552 724
v4 v6
AS262901 445 582
v4 v6
AS6939 HURRICANE 172 542
v4 v6
AS263075 317 408
v4 v6
AS262317 246 310
v4
AS52965 181 240
v4 v6
AS6057 6057 7 13
v4 v6
AS7195 7195 2 4
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS267963 in AS paths

Observed downstreams
Families
AS271732 157 201
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS264479 3 6
v4 v6
AS61573 2 4
v4 v6
AS262427 2 3
v4
AS28624 1 2
v6
AS52873 ASN52873 1 2
v6

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.