Skip to main content

AS47302

CYON

cyon AG

Registry

Authoritative registration data

AS number
47302
Name
CYON
Organisation
cyon AG
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

2

Total announced

7

Announced prefixes

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

Prefixes announced by AS47302
149.126.0.0/21 IPv4 /21 not checked
185.174.216.0/22 IPv4 /22 not checked
91.206.24.0/23 IPv4 /23 not checked
185.174.216.0/24 IPv4 /24 RPKI valid
194.126.200.0/24 IPv4 /24 RPKI valid
2a01:ab20::/32 IPv6 /32 not checked
2001:67c:234::/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 AS47302
Address families
SwissIX: Peering 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 AS47302 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS47302 in AS paths

Observed upstreams
Families
AS13030 INIT7 99 756
v4 v6
AS33891 CORE-BACKBONE 112 753
v4 v6
AS3303 SWISSCOM 51 317
v4 v6
AS6939 HURRICANE 54 193
v4 v6
AS34019 HIVANE 4 42
v4 v6
AS47147 AS-ANX 2 27
v4 v6
AS9002 RETN-AS 5 18
v6
AS24961 MYLOC-AS 2 14
v4 v6
AS39351 ESAB-AS 2 14
v4 v6
AS1764 NEXTLAYER-AS 1 7
v4 v6
AS1836 GREEN 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS47302 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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