Skip to main content

AS203851

as_csd001

CSD Network Services Ltd

Registry

Authoritative registration data

AS number
203851
Name
as_csd001
Organisation
CSD Network Services Ltd
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

0

Total announced

8

Announced prefixes

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

Prefixes announced by AS203851
185.154.48.0/24 IPv4 /24 not checked
185.154.49.0/24 IPv4 /24 not checked
185.154.50.0/24 IPv4 /24 not checked
185.154.51.0/24 IPv4 /24 not checked
185.87.212.0/24 IPv4 /24 not checked
185.87.213.0/24 IPv4 /24 not checked
185.87.214.0/24 IPv4 /24 not checked
185.87.215.0/24 IPv4 /24 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 AS203851
Address families
LINX LON1: Main 4,000 Mbps IPv4
LINX LON2 4,000 Mbps IPv4

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 AS203851 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS203851 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS203851 in AS paths

Observed downstreams
Families
AS205900 APC-Solutions 281 1,143
v4
AS210206 METROSECURITY-AS 280 382
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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