Skip to main content

AS64457

PIPEHOST-AS

PIPEHOST

Registry

Authoritative registration data

AS number
64457
Name
PIPEHOST-AS
Organisation
PIPEHOST
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

2

Total announced

12

Announced prefixes

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

Prefixes announced by AS64457
151.242.144.0/24 IPv4 /24 not checked
178.211.159.0/24 IPv4 /24 not checked
185.224.3.0/24 IPv4 /24 not checked
188.137.158.0/24 IPv4 /24 not checked
51.241.7.0/24 IPv4 /24 not checked
82.41.3.0/24 IPv4 /24 not checked
94.194.248.0/24 IPv4 /24 not checked
94.194.249.0/24 IPv4 /24 not checked
94.194.250.0/24 IPv4 /24 not checked
94.194.251.0/24 IPv4 /24 not checked
2a14:7c0:f100::/40 IPv6 /40 not checked
2a14:7c0:f300::/40 IPv6 /40 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 AS64457
Address families
ERA-IX Vienna 100,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 AS64457 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS64457 in AS paths

Observed upstreams
Families
AS215120 1,227 8,655
v4 v6
AS49581 270 1,372
v4
AS6939 HURRICANE 114 602
v4
AS51396 263 381
v6
AS216265 ARISTO-NET 6 34
v4
AS6204 6 28
v4 v6

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS64457 in AS paths

Observed downstreams
Families
AS199550 262 3,358
v4
AS51396 264 3,276
v6
AS203156 316 1,002
v4

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS40994 4 27
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.