Skip to main content

AS201962

RSM-CONNECT-AS

RSM Connect

Registry

Authoritative registration data

AS number
201962
Name
RSM-CONNECT-AS
Organisation
RSM Connect
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

8

Total announced

14

Announced prefixes

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

Prefixes announced by AS201962
185.58.28.0/22 IPv4 /22 not checked
45.153.176.0/22 IPv4 /22 not checked
91.205.12.0/22 IPv4 /22 not checked
91.205.12.0/24 IPv4 /24 not checked
91.205.13.0/24 IPv4 /24 not checked
91.205.14.0/24 IPv4 /24 not checked
2a04:df80::/29 IPv6 /29 not checked
2a04:df80::/32 IPv6 /32 not checked
2a04:df81::/32 IPv6 /32 not checked
2a04:df82::/32 IPv6 /32 not checked
2a04:df83::/32 IPv6 /32 not checked
2a04:df84::/32 IPv6 /32 not checked
2a04:df85::/32 IPv6 /32 not checked
2a04:df86::/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 AS201962
Address families
DE-CIX Munich: DE-CIX Munich Peering LAN 10,000 Mbps IPv4 · IPv6
SAIX: Public Peering LAN 20,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 AS201962 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS201962 in AS paths

Observed upstreams
Families
AS33891 CORE-BACKBONE 732 5,302
v4 v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS201962 in AS paths

Observed downstreams
Families
AS204218 258 340
v4
AS205687 138 174
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35369 LINZAG-TELEKOM-AS 2 15
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.