Skip to main content

AS47600

RUBIXDATACENTER

==================================================================

Registry

Authoritative registration data

AS number
47600
Name
RUBIXDATACENTER
Organisation
==================================================================
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS47600
80.245.58.0/23 IPv4 /23 not checked
185.45.150.0/24 IPv4 /24 not checked
217.71.114.0/24 IPv4 /24 not checked
217.71.122.0/24 IPv4 /24 not checked
80.245.56.0/24 IPv4 /24 not checked
80.91.89.0/24 IPv4 /24 not checked
82.129.65.0/24 IPv4 /24 not checked
82.138.75.0/24 IPv4 /24 not checked
82.138.86.0/24 IPv4 /24 not checked
2a13:cac0::/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

Internet Exchange memberships listed for AS47600
Address families
France-IX AURA: lyonix-peering 100,000 Mbps IPv4 · IPv6
France-IX Paris 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 AS47600 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

27 networks seen before AS47600 in AS paths

No rows match “”.

Showing of

Observed downstreams

3 networks seen after AS47600 in AS paths

Observed downstreams
Families
AS212298 263 666
v4
AS201636 258 334
v4
AS20148 254 332
v4

No rows match “”.

Showing of

Uncertain adjacencies

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