Skip to main content

AS216193

AS-HYPERION-CLOUD

HYPERION CLOUD SAS

Registry

Authoritative registration data

AS number
216193
Name
AS-HYPERION-CLOUD
Organisation
HYPERION CLOUD SAS
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS216193
154.16.229.0/24 IPv4 /24 not checked
154.16.254.0/24 IPv4 /24 not checked
2a13:1c47:c0d0::/44 IPv6 /44 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 AS216193
Address families
nine 10,000 Mbps IPv4 · IPv6
nine - six in Paris 200,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 AS216193 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS216193 in AS paths

Observed upstreams
Families
AS62000 AS62000 667 1,398
v4 v6
AS6939 HURRICANE 15 16
v4
AS34019 HIVANE 5 12
v4
AS25091 IP-Max 2 4
v4
AS47160 MOJI 1 2
v6
AS6204 ZET-NET 1 1
v4
AS6696 VERIXI 1 1
v4
AS215596 Kissgroup 1 1
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS216193 in AS paths

Observed downstreams
Families
AS214154 283 360
v4

No rows match “”.

Showing of

Uncertain adjacencies

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