Home
Explore What GeoCables can do Cables Locations Map My path ISP status Country resilience Check my connection Blocked websites
Live Network radar Live Map Cable monitoring Events log Cable incidents Big screen
Learn Research Guide Methodology Latency Overland links Deployments by year Pulse Open dataset API Widgets What's new About Contact

MIST

In Service

8,100 km · 5 landing points · 4 countries · Ready for Service: 2024

Follow MIST
In TelegramCheck my routeAlerts for incidents on this cable and outages in its countries.
Ask about this
Answers come from the data on this site; the assistant does not know anything else.

Reliability passport

90 out of 100
Reliability index
80%
Stability
checks within 1.2x of the route baseline, last 365 days
0
Significant incidents
last 365 days
2
Age
years in service, typical design life 25
0
Countries routing through it
would see a longer path if it broke
1201022026-03: 52%, n=24032026-04: 77%, n=86042026-05: 66%, n=58052026-06: 82%, n=38062026-07: 63%, n=46072026-08: 73%, n=43082026-09: 94%, n=77092026-10: 96%, n=49102026-11: 100%, n=4711

Share of stable checks by month; marks are significant incidents

How the index is computed

100 minus: anomalous checks share x 300 (max 30); significant incidents x 8 (max 40); (95th percentile of latency to baseline - 1.3) x 50 when above 1.3 (max 15); (age - 20 years) x 1.5 when older than 20 (max 15). Latency is measured as a ratio to each route's own baseline, so cables of different length compare fairly. A significant incident is unavailability or a latency peak of 1.5x lasting an hour or more, confirmed by more than one vantage point.

Ctrl + Scroll to zoom
Tap to interact with map

Specifications

Length8,100 km
StatusIn Service
Ready for Service2024
Landing Points5
Countries4

Owners

Orient Link

Internet outages by country

IndiaMalaysiaSingaporeThailand
Advertisement
Advertisement

Landing Points (5)

Location Country Position
Chennai, India IN India 13.0635°, 80.2431°
Morib, Malaysia MY Malaysia 2.7512°, 101.4436°
Mumbai, India IN India 19.0761°, 72.8759°
Satun, Thailand TH Thailand 6.6135°, 100.0661°
Tuas, Singapore SG Singapore 1.3382°, 103.6471°

If this cable is cut

What each country and landing point keeps if MIST goes down. A calculation from our cable and landing-point database, not a forecast.

CountryOther international cablesLand linksWhat remains
Thailand15 yes reserve of 15 cables
India22 yes reserve of 22 cables
Malaysia29 yes reserve of 29 cables
Singapore46 no reserve of 46 cables

Landing points with no other cable nearby

Every landing point of this cable has another cable within 50 km.

No alerts from our monitoring on this cable in the last 180 days. Events feed →

Counted: other international cables landing in the same country (domestic cables between points of one country are not a way out), other cables at landing points within 50 km, and whether the country has land links. Not counted: cable capacity, operator contracts and satellite. Use as a first look at dependence, not as a statement of what would happen.

Live Performance

354
measurements
10
probes
254
days monitored
115.5
ms avg RTT
0
anomalies

Monitored from 2026-03-06 through 2026-11-16 - 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.

About the MIST Cable System

Based on 47 measurements from GeoCables monitoring infrastructure, March-April 2026.

When you read the technical sheet for the MIST cable - Malaysia-India-Singapore-Thailand, brought into service in 2024 by Orient Link - you'll find an unambiguous number: 8,100 kilometres of fibre, 12 pairs, five landing stations across four countries. It's the kind of specification that invites an obvious expectation: packets travelling across MIST should spend a certain minimum amount of time in the glass, and that minimum should track the cable's length.

Our probes don't quite agree.

Across 47 measurements from Tuas, Singapore to Mumbai, India - the one direction our probe geography currently exercises on MIST - the fastest observed round-trip is 42.88 ms. At the speed of light in silica fibre (about 200,000 km/s), that works out to roughly 4,290 km of optical path end-to-end. Less than 54% of what the cable's headline length suggests.

This is the kind of reading that, a year ago, would have sent us hunting for a measurement bug. Today, it's the most interesting thing about the cable.

The two lengths

The discrepancy isn't an error - it's geometry. When a consortium announces an 8,100 km cable, that number totals every kilometre of fibre that the construction ship laid down, including branches. MIST's five landings aren't in a straight line. Chennai and Mumbai sit on opposite coasts of India, separated by 1,300 km of peninsular terrain. Satun and Morib anchor the Southeast Asian stretch. Tuas hangs off the southern tip of Singapore. These aren't all reachable through a single spine of fibre.

LandingCountryRole
MumbaiIndiaWestern terminus, Arabian Sea side
ChennaiIndiaBay of Bengal spur landing
SatunThailandAndaman Sea branch
MoribMalaysiaStrait of Malacca node
TuasSingaporeEastern terminus

Show MIST on the interactive cable map

A cable connecting those five points inevitably has branches. The construction cost of 8,100 km is real. What isn't real is the idea that any one packet traverses all of it. Packets pick the shortest segment that connects their endpoints - and between Tuas and Mumbai, that segment is the arc across the northern Bay of Bengal and the Arabian Sea, skipping the Indian peninsular detour and the Chennai landing entirely.

Orient Link, the company that owns MIST, is a single-purpose operator built around this specific cable. Its commercial model depends on the fact that a cable's value to customers comes from the number of regional points of presence it offers, not from the straight-line distance between any two of them. Two Indian landings let the operator sell connectivity on both coasts of the subcontinent without forcing customers to build their own backhaul across peninsular India. Satun and Morib add optionality for Thai and Malaysian traffic. Five landings are five markets, and it's five markets of demand that justified the capital to lay 8,100 km.

Great-circle distance between Tuas and Mumbai is about 3,900 km. Adding the roughly 10% overhead that real cable routes incur over the geodesic - cables hug continental shelves, avoid seismic zones, curve around territorial waters - gets us to 4,290 km. That's the 42.88 ms reading, almost exactly.

Why this isn't a problem

It's tempting to read a "below floor" measurement as a sign that something is wrong with either the calculation or the cable. Neither is true. MIST is working as designed. Orient Link built a cable with five landings because they wanted five points of presence, not because they wanted every landing to be in the path of every packet. A trunk-and-branch topology - a main lane of fibre with spurs leading to secondary landings - is the standard way to offer regional coverage without forcing every user onto a single linear highway.

This is the same architecture that shapes several of the cables we've written about. Apricot is explicitly hub-and-spoke: a Japan-Indonesia spine with branches to Guam, the Philippines, Taiwan, and Singapore. Bifrost uses a trunk with branches for its North American-Southeast Asian reach. TAM-1, the Trans Americas pure-play cable, presents as a hub whose sub-arcs consistently measure below any length-derived floor. All three, like MIST, accept that their headline kilometre count is a statement about the cable's footprint, not the distance any single packet travels through it.

What the 47 measurements actually show

The floor, at 42.88 ms, is stable: the lowest ten readings cluster between 42.88 and 46.1 ms. Above that floor, variance is significant. Average RTT is 101.93 ms, standard deviation 44.17, maximum 290.77. A 2.4× spread between minimum and average is the signature of a path where the baseline is fast and well-defined, but where individual measurements occasionally take a longer detour - likely hitting congestion at one of the transit points in either Singapore or Mumbai, or being briefly routed around a busy node by one of the operators running traffic over the cable.

None of this suggests a fault. A 2024 cable, not yet two years into service, is still in the period where transit providers are tuning their BGP preferences and discovering what traffic patterns actually work. Variance like this flattens over the following year or two as routing settles.

MetricValueInterpretation
Minimum RTT42.88 msFloor; matches ~4,290 km optical path
Average RTT101.93 msIncludes congestion and re-routing excursions
Maximum RTT290.77 msWorst-case detour (likely BGP re-route)
Standard deviation44.17 msHigh but concentrated above floor
Cable length (nominal)8,100 kmTotal fibre including branches
Traffic path (Tuas→Mumbai)~4,290 kmMain lane without eastern spur

The India-Singapore corridor

MIST joins a cluster of recent cables addressing the India-Southeast Asia corridor: India-Europe Xpress, AAE-1, SeaMeWe-6. These cables compete for the same broad purpose - delivering low-latency transit between the Indian subcontinent and the Southeast Asian hub cities - but each takes a different geometric bet. AAE-1 and SeaMeWe-6 route westward through the Suez corridor and back out toward Europe. MIST stays in the Indian Ocean, serving India-to-Singapore traffic directly.

The reason this corridor has attracted so many new cables in the last five years is a structural shift in regional traffic. Indian data centres - in Mumbai, Chennai, Bangalore - have grown by order of magnitude over that period, and a large share of their traffic terminates in Singapore, where AWS, Google Cloud, and Microsoft Azure run their primary South and Southeast Asian regions. MIST is the infrastructure response: the shortest feasible path between two poles of that corridor, without intermediate geography and without competing for capacity with Europe-bound flows.

For operators who want the shortest path between Mumbai and Singapore - specifically the path that doesn't hairpin through an intermediate geography - MIST is the answer. And our 42.88 ms floor is the evidence that, for at least one direction of traffic on at least one transit provider, the cable delivers exactly the path its geometry suggests it should.

What we're watching next

The one missing element is the reverse direction. Our current probe footprint gives us Tuas→Mumbai but not Mumbai→Tuas. Once a Mumbai-based probe joins the measurement rotation, we'll know whether the path is symmetric (the floor stays at 42.88 ms either way) or whether there's a systematic asymmetry from different transit provider preferences on the two ends. That's the kind of cross-check that turns a single-direction reading into a complete picture of how an 8,100 km cable chooses to behave in practice.

Health

Status✓ Normal
RTT66.08 ms / base 62.21 ms
Last checked2026-11-16 04:31

Monitored by our probe network. Open monitoring →

RTT History

Route: #1033 → Mumbai Measured: 2026-11-16 04:31
66.1 ms
Min Avg Max #
7 days 61.2 77.7 121.3 4
30 days 58.7 76.8 132.0 22
60 days 42.7 94.1 368.7 276

Health Timeline

Thu, Oct 29
View full event log →
Hop Anomaly
4ms → 18ms (4.68×)
21:01
Hop Anomaly
7ms → 41ms (6.21×)
17:01
Fri, Oct 23
View full event log →
Hop Anomaly
18ms → 57ms (3.16×)
11:01
Sun, Sep 27
View full event log →
Hop Anomaly
4ms → 15ms (3.80×)
03:03
Sat, Sep 26
View full event log →
Hop Anomaly
3ms → 13ms (4.23×)
07:01
Tue, Sep 22
View full event log →
Hop Anomaly
4ms → 13ms (3.68×)
04:30
Sun, Sep 20
View full event log →
Mumbai
RTT Spike
95ms → 197ms (2.07×)
22:31
Sun, Aug 23
View full event log →
Hop Anomaly
5ms → 347ms (67.48×)
07:01
Sun, Aug 9
View full event log →
Hop Anomaly
17ms → 237ms (14.34×)
07:01
Fri, Aug 7
View full event log →
Hop Anomaly
13ms → 206ms (15.86×)
21:01
Tue, Jun 16
View full event log →
Hop Anomaly
40ms → 263ms (6.54×)
01:01
Thu, Jun 4
View full event log →
Hop Anomaly
10ms → 30ms (3.10×)
17:02
Sat, May 30
View full event log →
Hop Anomaly
10ms → 47ms (4.82×)
02:30
Sat, May 23
View full event log →
Hop Anomaly
5ms → 39ms (8.22×)
13:00
Thu, May 7
View full event log →
Hop Anomaly
46ms → 177ms (3.81×)
05:00
Sun, May 3
View full event log →
Mumbai
RTT Spike
98ms → 369ms (3.77×)
18:31
Fri, Apr 24
View full event log →
Hop Anomaly
3ms → 14ms (4.17×)
11:00
Mumbai
RTT Spike
101ms → 213ms (2.12×)
10:31
Sat, Apr 18
View full event log →
Hop Anomaly
7ms → 23ms (3.32×)
15:01
Thu, Apr 16
View full event log →
Hop Anomaly
7ms → 69ms (9.63×)
19:00
Mon, Apr 13
View full event log →
Mumbai
RTT Spike
106ms → 291ms (2.74×)
04:31

FAQ

Who owns and operates the MIST submarine cable?
The MIST submarine cable is owned by Orient Link.
When did the MIST cable come into service?
The MIST cable came into service in 2024.
What countries does the MIST cable route through?
The MIST cable routes through India, Malaysia, Singapore, and Thailand.
How much data capacity does the MIST cable have?
The MIST cable has a capacity of 12 fibre pairs.
Are there any notable incidents or cuts with the MIST cable?
There are no widely known notable cuts or incidents reported for the MIST cable as of its current status.
MIST
  • Length8,100 km
  • StatusIn Service
  • Ready for Service2024

Calculate Cable Distance

Find the actual cable routing distance between any two cities

Open Calculator →
Submarine cables Land fiber Live probes
Advertisement
Explore GeoCables: interactive submarine cable map, all 728 submarine cables, live internet latency map, cable landing points worldwide

Log In

Access your routes, favorites, and API key

Create account Forgot password?