Skip to main content

AS20893

SYSTEM-CLINCH-AS

----------------------------------------------------

Registry

Authoritative registration data

AS number
20893
Name
SYSTEM-CLINCH-AS
Organisation
----------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS20893
217.27.96.0/20 IPv4 /20 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 AS20893
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 AS20893 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS20893 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 190 257
v4
AS174 COGENT-174 36 44
v4
AS34019 HIVANE 3 5
v4
AS13030 INIT7 2 5
v4
AS5405 INTERDOTLINK 2 2
v4
AS24961 MYLOC-AS 2 2
v4
AS29075 IELO 2 2
v4
AS39351 ESAB-AS 2 2
v4
AS1764 NEXTLAYER-AS 1 1
v4
AS1836 GREEN 1 1
v4
AS33891 CORE-BACKBONE 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS20893 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.