Skip to main content

AS15398

CYBERCORE-AS

Werft22 AG

Registry

Authoritative registration data

AS number
15398
Name
CYBERCORE-AS
Organisation
Werft22 AG
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 AS15398
195.234.163.0/24 IPv4 /24 not checked
2001:918:ff5d::/48 IPv6 /48 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 AS15398
Address families
SwissIX: Peering 1,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 AS15398 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS15398 in AS paths

Observed upstreams
Families
AS3303 SWISSCOM 214 396
v4 v6
AS6939 HURRICANE 77 107
v4 v6
AS9002 RETN-AS 14 18
v6
AS34019 HIVANE 4 12
v4 v6
AS5405 INTERDOTLINK 7 10
v4 v6
AS48362 TKSWF-AS 2 8
v4 v6
AS25091 IP-Max 2 7
v4 v6
AS47147 AS-ANX 2 6
v4 v6
AS1764 NEXTLAYER-AS 2 4
v4 v6
AS24961 MYLOC-AS 2 4
v4 v6
AS39351 ESAB-AS 2 4
v4 v6
AS29075 IELO 2 3
v4 v6
AS1836 GREEN 1 2
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS15398 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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