Skip to main content

AS50113

SuperServersDatacenter

*** updated ***

Registry

Authoritative registration data

AS number
50113
Name
SuperServersDatacenter
Organisation
*** updated ***
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

18

IPv6 prefixes

28

Total announced

46

Announced prefixes

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

Prefixes announced by AS50113
132.243.27.0/24 IPv4 /24 not checked
185.174.139.0/24 IPv4 /24 not checked
185.180.230.0/24 IPv4 /24 not checked
185.188.180.0/24 IPv4 /24 not checked
192.162.100.0/24 IPv4 /24 not checked
192.162.101.0/24 IPv4 /24 not checked
192.162.102.0/24 IPv4 /24 not checked
192.162.103.0/24 IPv4 /24 not checked
193.0.200.0/24 IPv4 /24 not checked
193.0.202.0/24 IPv4 /24 not checked
193.0.203.0/24 IPv4 /24 not checked
193.168.226.0/24 IPv4 /24 not checked
194.63.140.0/24 IPv4 /24 RPKI valid
194.63.141.0/24 IPv4 /24 not checked
194.63.142.0/24 IPv4 /24 RPKI valid
194.63.143.0/24 IPv4 /24 not checked
5.101.88.0/24 IPv4 /24 RPKI invalid
91.217.77.0/24 IPv4 /24 not checked
2a0f:df40::/29 IPv6 /29 not checked
2a04:5200::/32 IPv6 /32 RPKI valid
2a04:5202::/32 IPv6 /32 RPKI valid
2a04:5203::/32 IPv6 /32 RPKI valid
2a04:5204::/32 IPv6 /32 RPKI valid
2a04:5205::/32 IPv6 /32 RPKI valid
2a04:5206::/32 IPv6 /32 RPKI valid
2a04:5207::/32 IPv6 /32 RPKI valid
2a0a:981::/32 IPv6 /32 not checked
2a04:5200:121::/48 IPv6 /48 not checked
2a04:5200:1::/48 IPv6 /48 RPKI valid
2a04:5200:20a::/48 IPv6 /48 not checked
2a04:5200:3405::/48 IPv6 /48 RPKI valid
2a04:5200:3::/48 IPv6 /48 RPKI valid
2a04:5200:4::/48 IPv6 /48 RPKI valid
2a04:5200:50::/48 IPv6 /48 RPKI valid
2a04:5200:7::/48 IPv6 /48 RPKI valid
2a04:5200:9::/48 IPv6 /48 RPKI valid
2a04:5200:a050::/48 IPv6 /48 not checked
2a04:5200:ad09::/48 IPv6 /48 RPKI valid
2a04:5200:c068::/48 IPv6 /48 not checked
2a04:5200:d21::/48 IPv6 /48 not checked
2a04:5200:fa08::/48 IPv6 /48 RPKI valid
2a04:5200:fe6::/48 IPv6 /48 not checked
2a0a:9300::/48 IPv6 /48 RPKI valid
2a0a:9300:aaaa::/48 IPv6 /48 not checked
2a0c:5d00:1001::/48 IPv6 /48 RPKI valid
2a04:5200:dc77::/64 IPv6 /64 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 AS50113
Address families
Eurasia Peering IX: Peering LAN — 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 AS50113 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS50113 in AS paths

Observed upstreams
Families
AS35598 INETCOM 818 11,555
v4 v6
AS1299 TWELVE99 97 3,219
v4
AS29076 CITYTELECOM-AS 78 2,502
v4
AS6939 HURRICANE 136 2,383
v4 v6
AS31500 GNM-AS 89 2,067
v4
AS62255 BEMYLINK 170 1,856
v4 v6
AS51601 IPTP 52 990
v4 v6
AS25091 IP-Max 18 620
v4 v6
AS202984 team-host 225 479
v4
AS56630 MELBICOM-EU-AS 117 356
v4
AS47692 NESSUS 10 252
v4 v6
AS209641 I-SERVERS-EAST 177 220
v4
AS8218 NEO-ASN 10 179
v4 v6
AS13194 BITE 3 120
v4
AS50673 Serverius-as 4 28
v4
AS6204 ZET-NET 3 26
v4
AS56655 GIGAHOST 2 16
v6
AS50629 LWLCOM 2 2
v6
AS8732 COMCOR-AS 1 2
v4
AS33891 CORE-BACKBONE 1 1
v6
AS39351 ESAB-AS 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

8 networks seen after AS50113 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 7 877
v4 v6
AS34927 iFog-GmbH 3 240
v4
AS37721 ORG-VTS1-AFRINIC 7 221
v4 v6
AS49544 i3Dnet 4 89
v4
AS205112 PHILUNET 5 63
v4 v6
AS200612 GulfBridgeInternational 3 27
v4
AS208972 3 27
v4
AS49673 TRUENETWORK 3 26
v4
AS199524 GCORE 2 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.