Skip to main content

AS39563

UCSYSTEMS

CTA Systems B.V.

Registry

Authoritative registration data

AS number
39563
Name
UCSYSTEMS
Organisation
CTA Systems B.V.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

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

Prefixes announced by AS39563
185.231.16.0/24 IPv4 /24 not checked
185.231.17.0/24 IPv4 /24 not checked
185.231.18.0/24 IPv4 /24 not checked
185.231.19.0/24 IPv4 /24 not checked
185.80.10.0/24 IPv4 /24 not checked
185.80.11.0/24 IPv4 /24 not checked
185.80.8.0/24 IPv4 /24 not checked
185.80.9.0/24 IPv4 /24 not checked
85.8.131.0/24 IPv4 /24 not checked
2a0c:3900::/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 AS39563
Address families
1-IX EU 10,000 Mbps IPv4 · IPv6
1-NL FREE 10,000 Mbps IPv4 · IPv6
ERA-IX Amsterdam 10,000 Mbps IPv4 · IPv6
ERA-IX Frankfurt 10,000 Mbps IPv4 · IPv6
FogIXP 10,000 Mbps IPv4 · IPv6
FogIXP Amsterdam 10,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · IPv6
LSIX: Main 10,000 Mbps IPv4 · IPv6
NL-ix: Main 20,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 10,000 Mbps IPv4 · IPv6
nine 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 AS39563 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

40 networks seen before AS39563 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS39563 in AS paths

Observed downstreams
Families
AS35055 WI-Connect 89 251
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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