Skip to main content

AS209523

HOPUS-SERVICES

HOPUS SAS

Registry

Authoritative registration data

AS number
209523
Name
HOPUS-SERVICES
Organisation
HOPUS SAS
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

2

Total announced

8

Announced prefixes

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

Prefixes announced by AS209523
5.198.192.0/19 IPv4 /19 not checked
185.97.140.0/22 IPv4 /22 not checked
45.158.68.0/22 IPv4 /22 not checked
185.97.141.0/24 IPv4 /24 not checked
5.198.193.0/24 IPv4 /24 not checked
5.198.194.0/24 IPv4 /24 not checked
2a02:e58::/32 IPv6 /32 not checked
2a02:e58:2::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS209523 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS209523 in AS paths

Observed upstreams
Families
AS34019 HIVANE 266 870
v4 v6
AS29075 IELO 285 610
v4 v6
AS44530 HOPUS 74 226
v4 v6
AS25091 IP-Max 7 22
v4 v6
AS29222 Infomaniak-AS 2 10
v4 v6
AS41327 FIBERTELECOM-AS 3 9
v4 v6
AS35280 F5 3 4
v6
AS215596 Kissgroup 1 3
v4 v6
AS30972 BEDROCK 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS209523 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS209823 ENKI-AS 1 8
v4 v6
AS56987 AS-ABACLOUDA 1 5
v4 v6
AS49028 D-LAKE 1 4
v4 v6
AS50628 Leonix-Telecom 1 3
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.