Skip to main content

AS56962

RHS

RHS s.r.l.

Registry

Authoritative registration data

AS number
56962
Name
RHS
Organisation
RHS s.r.l.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS56962
141.11.24.0/24 IPv4 /24 not checked
193.35.226.0/24 IPv4 /24 not checked
212.24.121.0/24 IPv4 /24 not checked
31.57.231.0/24 IPv4 /24 not checked
91.124.171.0/24 IPv4 /24 not checked
91.242.235.0/24 IPv4 /24 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 AS56962 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS56962 in AS paths

Observed upstreams
Families
AS34428 EIGHTROUTE 210 1,512
v4
AS12874 40 306
v4
AS8218 NEO-ASN 3 60
v4
AS5405 5 36
v4
AS6204 2 12
v4
AS24961 2 12
v4
AS4455 1 6
v4
AS31543 1 6
v4
AS60171 1 6
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS56962 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

12 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 36
v4
AS12779 ITGATE 1 24
v4
AS49544 i3Dnet 1 12
v4
AS51185 MAINSTREAMING-AS 1 12
v4
AS8660 MATRIX-AS 1 6
v4
AS12637 1 6
v4
AS13237 1 6
v4
AS15605 1 6
v4
AS49605 1 6
v4
AS50877 1 6
v4
AS57111 1 6
v4
AS59919 1 6
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.