Skip to main content

AS206281

AS-ZXCS

Stichting DIGI NL

Registry

Authoritative registration data

AS number
206281
Name
AS-ZXCS
Organisation
Stichting DIGI NL
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

3

Total announced

12

Announced prefixes

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

Prefixes announced by AS206281
185.104.28.0/24 IPv4 /24 not checked
185.104.29.0/24 IPv4 /24 not checked
185.104.30.0/24 IPv4 /24 not checked
185.104.31.0/24 IPv4 /24 not checked
185.177.144.0/24 IPv4 /24 not checked
185.220.172.0/24 IPv4 /24 not checked
185.220.173.0/24 IPv4 /24 not checked
185.220.174.0/24 IPv4 /24 not checked
185.220.175.0/24 IPv4 /24 not checked
2a02:f5c0::/32 IPv6 /32 not checked
2a06:2ec0::/32 IPv6 /32 not checked
2a0a:4f80::/32 IPv6 /32 RPKI valid

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 AS206281
Address families
NL-ix: Main 10,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 AS206281 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

20 networks seen before AS206281 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS206281 in AS paths

Observed downstreams
Families
AS60775 GxW 365 689
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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