Skip to main content

AS59570

Hostingstudio

=== Upstream ===

Registry

Authoritative registration data

AS number
59570
Name
Hostingstudio
Organisation
=== Upstream ===
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS59570
185.197.133.0/24 IPv4 /24 not checked
2001:678:d30::/48 IPv6 /48 not checked
2001:678:d34::/48 IPv6 /48 not checked
2001:67c:2148::/48 IPv6 /48 RPKI valid

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 AS59570
Address families
4b42 Internet Exchange Point: Switzerland 1,000 Mbps IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
NL-ix: Main 100 Mbps IPv4 · IPv6
ONIX 1,000 Mbps IPv4 · IPv6
SBIX Zurich: Switzerland 1,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 10,000 Mbps IPv4 · IPv6
UNM-Exch Canada-West: Main 1,000 Mbps IPv4 · IPv6
ixFabric - Amsterdam 10,000 Mbps IPv6
ixFabric - Toronto 1,000 Mbps IPv6
ixFabric - Zurich 1,000 Mbps 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 AS59570 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

32 networks seen before AS59570 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS59570 in AS paths

Observed downstreams
Families
AS208454 Hostingstudio 253 365
v6
AS112 AS112-PROJECT 2 12
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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