Skip to main content

AS34144

EUSIP-RACK66

****** NETWORK ******

Registry

Authoritative registration data

AS number
34144
Name
EUSIP-RACK66
Organisation
****** NETWORK ******
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS34144
185.89.20.0/24 IPv4 /24 not checked
194.176.106.0/24 IPv4 /24 not checked
195.18.24.0/24 IPv4 /24 not checked
2a01:aa00::/32 IPv6 /32 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 AS34144
Address families
BNIX 100 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 AS34144 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS34144 in AS paths

Observed upstreams
Families
AS6696 VERIXI 655 1,590
v4 v6
AS6939 HURRICANE 23 48
v4
AS8218 NEO-ASN 2 16
v4
AS3303 SWISSCOM 6 14
v4
AS34019 HIVANE 3 10
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS34144 in AS paths

Observed downstreams
Families
AS47861 260 337
v4

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS48185 team_blue 1 6
v4
AS45049 1 2
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.