Skip to main content

AS213028

CLYVO-AS

Clyvo Networks

Registry

Authoritative registration data

AS number
213028
Name
CLYVO-AS
Organisation
Clyvo Networks
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS213028
193.93.180.0/24 IPv4 /24 not checked
2a0c:a180::/29 IPv6 /29 not checked
2a0c:a180:10::/48 IPv6 /48 not checked
2a0c:a180:50::/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 AS213028
Address families
FogIXP 1,000 Mbps IPv4 · IPv6
Frys-IX 10,000 Mbps IPv4 · IPv6
INTERIX 10,000 Mbps IPv4 · IPv6
Speed-IX: SPEED-IX 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 AS213028 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS213028 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS213028 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 10
v4 v6
AS3399 OBE-NET 1 4
v4 v6
AS24961 MYLOC-AS 1 3
v6
AS49544 i3Dnet 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 2
v4 v6
AS263152 ASN263152 1 1
v4

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.