Skip to main content

AS203391

CLOUDNSNET

Cloud DNS Ltd.

Registry

Authoritative registration data

AS number
203391
Name
CLOUDNSNET
Organisation
Cloud DNS Ltd.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

4

Total announced

12

Announced prefixes

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

Prefixes announced by AS203391
185.136.96.0/24 IPv4 /24 not checked
185.136.97.0/24 IPv4 /24 not checked
185.136.98.0/24 IPv4 /24 not checked
185.136.99.0/24 IPv4 /24 not checked
45.83.248.0/24 IPv4 /24 not checked
45.83.249.0/24 IPv4 /24 not checked
45.83.250.0/24 IPv4 /24 not checked
45.83.251.0/24 IPv4 /24 not checked
2a06:fb00:1::/48 IPv6 /48 not checked
2a06:fb00:2::/48 IPv6 /48 not checked
2a06:fb00:3::/48 IPv6 /48 not checked
2a06:fb00:4::/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 AS203391
Address families
BIX.BG: Main — IPv4 · IPv6
ERA-IX Amsterdam — IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA — IPv4 · IPv6
NetIX: NetIX — IPv4 · IPv6
RTIX — IPv4 · IPv6
SAIX Saudi Arabia Riyadh — IPv4 · IPv6
TPIX-TW — 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 AS203391 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

31 networks seen before AS203391 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS203391 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS61573 ASN61573 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.