Skip to main content

AS212200

EUCLID-INFRA

EUCLID SERVICES LIMITED

Registry

Authoritative registration data

AS number
212200
Name
EUCLID-INFRA
Organisation
EUCLID SERVICES LIMITED
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS212200
185.140.166.0/24 IPv4 /24 not checked
185.140.167.0/24 IPv4 /24 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 AS212200
Address families
GR-IX::Athens: Peering Lan 1,000 Mbps IPv4
KleyReX: Peering LAN 100 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 AS212200 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS212200 in AS paths

Observed upstreams
Families
AS174 COGENT-174 259 335
v4
AS12713 OTEGlobe 254 325
v4
AS14840 ASN14840 2 5
v4
AS50877 AIRBEAM-AS 2 2
v4
AS8280 SYNAPSECOM-AS 1 1
v4
AS22356 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS212200 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS212483 level86 1 2
v4
AS51185 MAINSTREAMING-AS 1 1
v4
AS56457 1 1
v4
AS198150 SIACOM-AS 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.