Home
Explore Cables Locations Map ISP status Shutdowns
Live Live Map Health Latency Deployments by year Pulse Big screen 🖥
Learn Research Guide Methodology
HomeSubmarine Cables › Circe North

Circe North

In Service

203 km · 2 Landing Points · 2 Countries · Ready for Service: 1999

Ctrl + Scroll to zoom
👆 Tap to interact with map

Specifications

Length203 km
StatusIn Service
Ready for Service1999
Landing Points2
Countries2

Owners

Zayo euNetworks

Landing Points (2)

Location Country Position
Lowestoft, United Kingdom GB United Kingdom 52.4714°, 1.7292°
Zandvoort, Netherlands NL Netherlands 52.3704°, 4.5272°

📡 Live Performance

482
measurements
15
probes
132
days monitored
58.1
ms avg RTT
1
anomalies

Monitored from 2026-03-06 through 2026-07-17 - live ICMP round-trip time measurements via our monitoring probes. All values below are recomputed daily from raw probe data.

Measurement sources

Probe Location Samples Avg Min-Max Last seen
#33205 control probe 263 25.7 ms 10.1-71.6 2026-07-17
#6427 own probe Sydney AU 50 254.1 ms 252.3-257.4 2026-06-23
#1014473 own probe Minsk BY 50 35.0 ms 34.5-36.0 2026-06-23
#1015523 own probe Moscow RU 46 39.0 ms 38.7-41.0 2026-06-09
#37 control probe 36 39.4 ms 23.6-202.8 2026-06-28
#6410 own probe Sao Paulo BR 4 202.8 ms 202.6-202.9 2026-06-09
#6487 own probe Singapore SG 4 161.8 ms 161.7-162.0 2026-06-09
#7062 own probe Cape Town ZA 4 150.3 ms 148.1-152.6 2026-06-09
#1014589 own probe Almaty KZ 4 88.7 ms 88.6-88.8 2026-06-09
#1014597 own probe Tbilisi GE 4 62.6 ms 62.5-62.6 2026-06-09
#1014969 own probe Jerusalem IL 4 61.9 ms 61.8-62.1 2026-06-09
#1015932 own probe Odessa UA 4 41.2 ms 40.9-41.6 2026-06-09
#1015984 own probe Balancer IL 4 61.4 ms 61.2-61.6 2026-06-09
#1016031 own probe Kyiv UA 3 56.9 ms 54.0-61.9 2026-06-23
#1015563 own probe Saint Petersburg RU 2 47.1 ms 47.1-47.2 2026-06-02

About the Circe North Cable System

Circe North: a short trans-North Sea submarine cable

Circe North is a submarine cable connecting Lowestoft in the United Kingdom to Zandvoort in the Netherlands, spanning a relatively short distance of 203 kilometers across the North Sea. It has been in service since 1999, according to GeoCables database records, and is currently owned by Zayo and euNetworks. While its design capacity, fiber pair count, supplier, and underlying technology are not publicly disclosed, the cable is part of a busy corridor with multiple alternatives and landing points. What makes Circe North notable is its role in providing connectivity between the UK and continental Europe through a direct route. However, there are uncertainties surrounding its technical specifications and performance metrics, as well as discrepancies between theoretical latency calculations and real-world measurements.

Quick facts

NameCirce North
Length203 km
Ready-for-service year1999 (GeoCables database value; no conflicting sources identified)
OwnersZayo, euNetworks
StatusIn service
Design capacityNot disclosed
Fiber pairsNot disclosed
SupplierNot disclosed
TechnologyNot disclosed
Landing pointsLowestoft (United Kingdom); Zandvoort (Netherlands)
Alternatives in the same corridorZeus

🗺 Show Circe North on the interactive cable map

Route

Circe North connects Lowestoft on the eastern coast of England to Zandvoort, a coastal town in the Netherlands. Both locations are established landing points for submarine cables, with Lowestoft hosting cables such as IOEMA, Scylla, Tampnet South, Ulysses 2, and Zeus, while Zandvoort serves as a landing site for Concerto and Zeus. The cable spans the North Sea, a relatively shallow body of water, which simplifies cable-laying operations compared to deeper oceanic routes.

Why it was built and what it carries

Circe North was likely built to provide direct connectivity between the UK and the Netherlands, supporting data traffic between two major European economies. It serves as part of the broader infrastructure enabling international telecommunications, data exchange, and internet connectivity. While specific details about its traffic or capacity are not disclosed, its relatively short length suggests it is optimized for low-latency communications.

History: what can be established

Circe North was recorded as ready for service in 1999, according to GeoCables database records. No conflicting information about its RFS year has been identified in publicly available sources. It remains listed as in service, and ownership has been attributed to Zayo and euNetworks, two companies with significant stakes in European and global telecom infrastructure.

Capacity and technology

The design capacity, fiber pair count, supplier, and specific technology used in Circe North are not publicly disclosed. Without operator documentation, it cannot be stated whether the cable has undergone upgrades since its initial deployment or what its current capacity might be. This lack of transparency is not uncommon for older cables, especially those serving regional routes rather than intercontinental ones.

Latency: the physics

Theoretical calculations based on the cable's length of 203 kilometers suggest a one-way light propagation latency of approximately 1.0 milliseconds, with a round-trip time (RTT) floor of about 2.0 milliseconds. However, real-world latency measurements from remote probes show significantly higher values. For example, the minimum observed RTT between Lowestoft and Zandvoort is 10.1 milliseconds, with an average of 25.7 milliseconds over 263 checks. These discrepancies are attributable to additional latency introduced by land tails, terminal equipment, and routing decisions in the broader internet path.

Redundancy: what happens if it breaks

In the event of a failure, connectivity between the UK and the Netherlands can rely on alternative cables in the same corridor, such as Zeus. Both Lowestoft and Zandvoort are well-connected landing points with multiple cables, reducing the risk of prolonged outages. Standard industry practices for submarine cable repair, including the use of cable ships and remotely operated vehicles (ROVs), would apply to Circe North.

Bottom line

  • Circe North connects Lowestoft in the UK to Zandvoort in the Netherlands, spanning 203 kilometers.
  • It has been in service since 1999, with ownership attributed to Zayo and euNetworks.
  • Technical specifications such as design capacity, fiber pairs, supplier, and technology are not publicly disclosed.
  • Theoretical latency is approximately 2.0 ms RTT, but real-world measurements are significantly higher due to land tails and routing.
  • Redundancy is supported by alternative cables in the same corridor, such as Zeus.

📡 Health

Status✓ Normal
RTT31.36 ms / base 33.41 ms
Last checked2026-07-17 08:31

Monitored by our probe network. Open monitoring →

📊 RTT History

Route: #33205 → Zandvoort Measured: 2026-07-17 08:31
31.4 ms
Min Avg Max #
7 days 31.1 31.3 31.4 4
30 days 30.5 34.3 40.9 14
60 days 10.1 25.7 71.6 263

Health Timeline

Sat, Jun 27
View full event log →
🔗
Hop Anomaly
11ms → 52ms (4.84×)
21:00
Sat, Jun 20
View full event log →
🔗
Hop Anomaly
6ms → 27ms (4.46×)
09:01
Tue, Jun 16
View full event log →
🔗
Hop Anomaly
7ms → 45ms (6.04×)
12:30
Tue, Jun 9
View full event log →
Lowestoft
RTT Spike
40ms → 120ms (2.99×)
10:31
Lowestoft
RTT Spike
40ms → 120ms (2.99×)
10:31
Zandvoort
Resolved
35ms → 32ms
01:02
📊
Zandvoort
Improving
35ms → 31ms
00:32
Mon, Jun 8
View full event log →
📊
Zandvoort
Improving
35ms → 31ms
23:02
🚨
Zandvoort
Alert Created
35ms → 69ms (2.00×)
21:01
🔴
Zandvoort
Anomaly Confirmed
35ms → 69ms (2.00×)
21:01
Zandvoort
RTT Spike
35ms → 69ms (2.00×)
21:01
Zandvoort
RTT Spike
33ms → 68ms (2.07×)
20:31
Wed, Jun 3
View full event log →
🔗
Hop Anomaly
22ms → 153ms (6.86×)
02:31
Tue, Jun 2
View full event log →
🔗
Hop Anomaly
29ms → 179ms (6.09×)
08:30
Fri, May 29
View full event log →
🔗
Hop Anomaly
3ms → 41ms (11.77×)
22:33
Thu, May 28
View full event log →
Zandvoort
RTT Spike
24ms → 64ms (2.72×)
20:32
Zandvoort
RTT Spike
16ms → 31ms (2.00×)
04:30
Wed, May 27
View full event log →
🔗
Hop Anomaly
6ms → 237ms (40.23×)
03:00
Thu, May 21
View full event log →
Zandvoort
RTT Spike
16ms → 34ms (2.16×)
00:31
Wed, May 20
View full event log →
Zandvoort
RTT Spike
15ms → 34ms (2.29×)
22:30
Wed, May 13
View full event log →
Zandvoort
RTT Spike
15ms → 41ms (2.79×)
14:30
Tue, May 5
View full event log →
Zandvoort
RTT Spike
21ms → 48ms (2.32×)
22:30
Sun, May 3
View full event log →
🔗
Hop Anomaly
14ms → 81ms (5.70×)
11:00
Wed, Apr 29
View full event log →
🔗
Hop Anomaly
10ms → 40ms (3.96×)
11:00
Sun, Apr 19
View full event log →
🔗
Hop Anomaly
13ms → 96ms (7.21×)
13:00
Mon, Apr 13
View full event log →
🔗
Hop Anomaly
6ms → 343ms (60.54×)
19:00
Mon, Apr 6
View full event log →
🔗
Hop Anomaly
23ms → 586ms (25.46×)
02:31
Sun, Mar 15
View full event log →
Lowestoft
RTT Spike
65ms → 182ms (2.79×)
10:03

FAQ

What is the length of the Circe North cable?
The Circe North submarine cable is 203 km long.
Which countries does Circe North connect?
Circe North connects 2 countries via 2 landing points.
Who owns the Circe North cable?
Circe North is owned by a consortium including Zayo, euNetworks.
When was Circe North put into service?
The Circe North cable entered service in 1999.
Circe North
  • Length203 km
  • StatusIn Service
  • Ready for Service1999

Calculate Cable Distance

Find the actual cable routing distance between any two cities

Open Calculator →
🌊 Submarine cables 🛤 Land fiber 📡 Live probes
Explore GeoCables: interactive submarine cable map · all 700+ submarine cables · live internet latency map · cable landing points worldwide

🌐 Log In

Access your routes, favorites, and API key

Create account Forgot password?