Skip to main content

AS203917

Hashlink

Hashlink Ltd

Registry

Authoritative registration data

AS number
203917
Name
Hashlink
Organisation
Hashlink Ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS203917
185.227.6.0/24 IPv4 /24 not checked
194.38.37.0/24 IPv4 /24 not checked
212.70.156.0/24 IPv4 /24 not checked
78.108.251.0/24 IPv4 /24 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 AS203917 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS203917 in AS paths

Observed upstreams
Families
AS57344 TELEHOUSE-AS 265 1,355
v4
AS60349 VARTEH-AS 76 101
v4
AS12615 GCN-AS 65 89
v4
AS14840 ASN14840 2 20
v4
AS20764 RASCOM-AS 3 12
v4
AS44814 BTEL-BG-AS 7 7
v4
AS15958 CETIN_doo_AS 1 4
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS203917 in AS paths

Observed downstreams
Families
AS51855 136 168
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS212483 level86 1 8
v4
AS13004 SOX 1 4
v4
AS198150 SIACOM-AS 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.