Skip to main content

AS210966

DCsolutions

--------------------------------------------------------------

Registry

Authoritative registration data

AS number
210966
Name
DCsolutions
Organisation
--------------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS210966
185.25.106.0/24 IPv4 /24 not checked
2a11:540::/30 IPv6 /30 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 AS210966
Address families
BIX 10,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 AS210966 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS210966 in AS paths

Observed upstreams
Families
AS206892 RENDSZERINF 287 443
v4 v6
AS6939 HURRICANE 85 115
v4 v6
AS47692 NESSUS 2 6
v4 v6
AS6663 TTI-NET 1 1
v4
AS33891 CORE-BACKBONE 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS210966 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS40994 Alwyzon 1 2
v4 v6
AS49544 i3Dnet 1 2
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.