Skip to main content

AS59816

BLYNX

4on LTD

Registry

Authoritative registration data

AS number
59816
Name
BLYNX
Organisation
4on LTD
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

1

Total announced

11

Announced prefixes

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

Prefixes announced by AS59816
185.251.224.0/22 IPv4 /22 not checked
185.254.88.0/22 IPv4 /22 not checked
185.70.132.0/22 IPv4 /22 not checked
194.147.120.0/22 IPv4 /22 not checked
193.169.216.0/23 IPv4 /23 not checked
185.241.36.0/24 IPv4 /24 not checked
185.241.37.0/24 IPv4 /24 not checked
185.241.38.0/24 IPv4 /24 not checked
185.241.39.0/24 IPv4 /24 not checked
185.251.225.0/24 IPv4 /24 not checked
2a05:2a00::/29 IPv6 /29 not checked

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 AS59816
Address families
LONAP: LON0 10,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 AS59816 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS59816 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 537 2,307
v4
AS39175 CONNECTIVE 296 696
v4
AS39545 FLUIDATA 273 342
v4
AS6939 HURRICANE 206 287
v6
AS3257 GTT-BACKBONE 39 89
v4 v6
AS8218 NEO-ASN 3 58
v4 v6
AS14840 ASN14840 2 34
v4
AS34927 iFog-GmbH 2 22
v4 v6
AS39351 ESAB-AS 2 16
v4 v6
AS33891 CORE-BACKBONE 2 14
v4
AS4455 BSO 1 7
v4
AS286 KPN 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS59816 in AS paths

Observed downstreams
Families
AS215675 perceptiontvcdn 255 333
v4
AS39175 CONNECTIVE 4 4
v4

No rows match “”.

Showing – of

Uncertain adjacencies

17 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.