Skip to main content

AS57222

HAASE-IT-AS

Olaf Haase IT-Services AS

Registry

Authoritative registration data

AS number
57222
Name
HAASE-IT-AS
Organisation
Olaf Haase IT-Services AS
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

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

Prefixes announced by AS57222
195.162.4.0/23 IPv4 /23 not checked
195.162.4.0/24 IPv4 /24 not checked
195.162.5.0/24 IPv4 /24 not checked
2a06:de01:a0::/44 IPv6 /44 not checked
2a06:de01:a4::/46 IPv6 /46 not checked
2a06:de01:a8::/46 IPv6 /46 not checked
2a06:de01:ac::/46 IPv6 /46 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 AS57222
Address families
CHIX-CH: Main 1,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
FogIXP Frankfurt 1,000 Mbps IPv4 · IPv6
FogIXP Zurich 1,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 AS57222 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS57222 in AS paths

Observed upstreams
Families
AS34927 iFog-GmbH 295 995
v4 v6
AS6939 HURRICANE 10 19
v4
AS14840 ASN14840 2 8
v4
AS39351 ESAB-AS 1 2
v4
AS205794 RTTW-AS 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS57222 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS58299 OPENFACTORY-AS 1 4
v4 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.