Home
Explore Cables Locations Map ISP status Shutdowns
Live Live Map Health Latency Pulse Big screen 🖥
Learn Research Guide Methodology
HomeSubmarine Cables › Lake Albert 2

Lake Albert 2

In Service

44 km · 2 Landing Points · 2 Countries · Ready for Service: 2020

Ctrl + Scroll to zoom
👆 Tap to interact with map

Specifications

Length44 km
StatusIn Service
Ready for Service2020
Landing Points2
Countries2

Owners

Bandwidth and Cloud Services (BCS)

Landing Points (2)

Location Country Position
Kasenyi, Congo, Dem. Rep. CD Dem. Rep. 1.3934°, 30.4384°
Mpeefu, Uganda UG Uganda 1.1016°, 30.6484°

📡 Live Performance

12
measurements
6
probes
1
days monitored
244.0
ms avg RTT
0
anomalies

Monitored from 2026-07-12 through 2026-07-12 - live ICMP round-trip time measurements via our monitoring probes. All values below are recomputed daily from raw probe data. ✓ No anomalies detected in the monitored period.

Measurement sources

Probe Location Samples Avg Min-Max Last seen
#6410 own probe Sao Paulo BR 2 322.8 ms 320.8-324.9 2026-07-12
#6427 own probe Sydney AU 2 418.9 ms 418.5-419.4 2026-07-12
#7062 own probe Cape Town ZA 2 80.6 ms 80.5-80.6 2026-07-12
#1014597 own probe Tbilisi GE 2 199.0 ms 193.9-204.2 2026-07-12
#1014969 own probe Jerusalem IL 2 219.3 ms 218.6-220.0 2026-07-12
#1015984 own probe Balancer IL 2 223.6 ms 202.5-244.7 2026-07-12

About the Lake Albert 2 Cable System

Lake Albert 2: A regional submarine cable crossing Lake Albert

Lake Albert 2 is a short submarine cable system spanning 44 kilometers across Lake Albert, connecting Kasenyi in the Democratic Republic of Congo to Mpeefu in Uganda. Owned by Bandwidth and Cloud Services (BCS), the cable is listed as in service and was recorded in the GeoCables database as ready for service (RFS) in 2020. While its design capacity, fiber pair count, supplier, and technology details are not publicly disclosed, the cable plays a role in regional connectivity between the two countries. What stands out about Lake Albert 2 is its geographical specificity: it serves as a wet segment link across Lake Albert, a natural border between Uganda and the Democratic Republic of Congo. Its role as part of the Lake Albert cable family, alongside Lake Albert 1, suggests a strategic effort to improve cross-border communication and data transport in this region. However, many technical aspects remain opaque, limiting deeper analysis of its capabilities.

Quick facts

System NameLake Albert 2
Length44 km
Ready for Service (RFS)2020 (GeoCables database)
OwnerBandwidth and Cloud Services (BCS)
StatusIn service
Design CapacityNot disclosed
Fiber PairsNot disclosed
SupplierNot disclosed
TechnologyNot disclosed
Landing PointsKasenyi (Democratic Republic of Congo), Mpeefu (Uganda)
Related SystemsLake Albert 1

Route

Lake Albert 2 connects Kasenyi, located on the eastern shore of Lake Albert in the Democratic Republic of Congo, to Mpeefu, situated on the lake's western shore in Uganda. Lake Albert itself is a prominent geographical feature in the East African Rift system, forming part of the border between the two countries. The cable's route is entirely submerged within the lake, making it a purely wet segment system.

Why it was built and what it carries

The Lake Albert 2 cable was likely built to enhance regional connectivity between Uganda and the Democratic Republic of Congo. By providing a direct link across Lake Albert, it bypasses the need for terrestrial infrastructure that might be hindered by challenging terrain or political complexities. While specific data traffic types carried by the cable are not disclosed, it is reasonable to assume that it supports internet, voice, and data services for local and cross-border communication. The presence of Lake Albert 1 in the same cable family suggests that Lake Albert 2 may be part of a broader strategy by Bandwidth and Cloud Services to establish reliable infrastructure in the region. However, without detailed public disclosures, the specific motivations and technical specifications remain speculative.

History: what can be established

According to GeoCables records, Lake Albert 2 was ready for service in 2020. No conflicting dates from industry sources are currently known, so this year is accepted as accurate. The cable's development and deployment timeline are not documented in public sources, leaving the planning, surveying, and installation phases unclear. As with most submarine cables, the laying process would have involved specialized cable-laying vessels, with potential burial or anchoring to secure the cable on the lakebed. Repairs, if necessary, would likely require similar vessels and expertise, though specific details about maintenance agreements or repair protocols for Lake Albert 2 are not publicly available.

Capacity and technology

The design capacity of Lake Albert 2 is not disclosed in public sources, nor are details about its fiber pair count, supplier, or technology. Without operator documentation, it is impossible to determine the cable's data throughput capabilities or the specific optical technologies employed. This lack of transparency is not uncommon for smaller regional cables, especially those serving localized markets.

Latency: the physics

The computed one-way light propagation latency over the 44 km wet segment of Lake Albert 2 is approximately 0.2 milliseconds, with a theoretical round-trip time (RTT) floor of 0.4 milliseconds. This calculation assumes light traveling through fiber at speeds between 200,000 and 204,000 km/s. However, real-world latency is higher due to additional factors such as land tails, terminal equipment, and routing inefficiencies. Live measurements from GeoCables' remote probes provide insights into end-to-end latency from various global locations to Kasenyi. For example:
  • Jerusalem -> Kasenyi: Minimum 218.6 ms, average 219.3 ms
  • Cape Town -> Kasenyi: Minimum 80.5 ms, average 80.6 ms
  • Sydney -> Kasenyi: Minimum 418.5 ms, average 418.9 ms
These figures reflect the full internet path, not the cable itself, and include latency contributions from terrestrial networks, routing, and intermediate hops.

Redundancy: what happens if it breaks

If Lake Albert 2 were to experience a fault, redundancy would depend on alternative infrastructure in the region. The Lake Albert 1 cable, part of the same family, may provide some backup capacity, though its route and specifications are not detailed in the available data. Repair logistics for Lake Albert 2 would likely involve specialized vessels capable of accessing the lake and conducting underwater repairs. Given the relatively short length of the cable, repair times might be quicker compared to longer submarine systems. However, the availability of equipment and expertise in the region would be critical factors.

Bottom line

  • Lake Albert 2 spans 44 km across Lake Albert, connecting Kasenyi (DR Congo) to Mpeefu (Uganda).
  • Owned by Bandwidth and Cloud Services (BCS), it was recorded as ready for service in 2020.
  • Design capacity, fiber pairs, supplier, and technology are not publicly disclosed.
  • Computed latency over the wet segment is approximately 0.4 ms RTT, though real-world measurements are higher due to network factors.
  • Redundancy may rely on Lake Albert 1 or other regional infrastructure.

📡 Health

Status✓ Normal
RTT324.87 ms
Last checked2026-07-12 20:32

Monitored by our probe network. Open monitoring →

Health Timeline

Sun, Jul 12
View full event log →
🔗
Hop Anomaly
20ms → 72ms (3.54×)
20:30
Sun, Jun 21
View full event log →
🔗
Hop Anomaly
9ms → 72ms (7.69×)
21:31
Sat, Jun 13
View full event log →
🔗
Hop Anomaly
17ms → 188ms (11.35×)
23:01
Thu, Jun 4
View full event log →
🔗
Hop Anomaly
16ms → 801ms (50.41×)
21:01
Wed, Jun 3
View full event log →
🔗
Hop Anomaly
6ms → 78ms (12.96×)
13:01
Sun, May 17
View full event log →
🔗
Hop Anomaly
21ms → 75ms (3.50×)
13:00
Sat, May 16
View full event log →
🔗
Hop Anomaly
21ms → 72ms (3.35×)
15:00
Thu, May 14
View full event log →
🔗
Hop Anomaly
18ms → 85ms (4.80×)
19:00
Fri, May 8
View full event log →
🔗
Hop Anomaly
5ms → 391ms (80.00×)
05:00
Wed, May 6
View full event log →
🔗
Hop Anomaly
4ms → 61ms (14.16×)
05:00
Tue, May 5
View full event log →
🔗
Hop Anomaly
17ms → 65ms (3.79×)
19:00
Fri, Apr 24
View full event log →
🔗
Hop Anomaly
12ms → 45ms (3.85×)
15:00
🔗
Hop Anomaly
4ms → 26ms (6.89×)
13:00
Thu, Apr 23
View full event log →
🔗
Hop Anomaly
12ms → 265ms (22.25×)
21:00
Sat, Apr 18
View full event log →
🔗
Hop Anomaly
5ms → 67ms (14.84×)
15:00
Wed, Apr 15
View full event log →
🔗
Hop Anomaly
5ms → 19ms (3.78×)
23:01
🔗
Hop Anomaly
5ms → 19ms (3.74×)
05:01
Sun, Apr 12
View full event log →
🔗
Hop Anomaly
11ms → 213ms (19.62×)
06:34
Sat, Apr 11
View full event log →
🔗
Hop Anomaly
6ms → 40ms (6.97×)
17:00
🔗
Hop Anomaly
5ms → 18ms (3.34×)
15:00
Fri, Apr 10
View full event log →
🔗
Hop Anomaly
8ms → 56ms (6.62×)
20:51
Thu, Apr 9
View full event log →
🔗
Hop Anomaly
4ms → 15ms (3.73×)
11:00
Wed, Apr 8
View full event log →
🔗
Hop Anomaly
5ms → 39ms (7.64×)
23:00

FAQ

What is the length of the Lake Albert 2 cable?
The Lake Albert 2 submarine cable is 44 km long.
Which countries does Lake Albert 2 connect?
Lake Albert 2 connects 2 countries via 2 landing points.
Who owns the Lake Albert 2 cable?
Lake Albert 2 is owned by a consortium including Bandwidth and Cloud Services (BCS).
When was Lake Albert 2 put into service?
The Lake Albert 2 cable entered service in 2020.
Lake Albert 2
  • Length44 km
  • StatusIn Service
  • Ready for Service2020

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?