Physical Address
Metro Manila, Philippines
Physical Address
Metro Manila, Philippines
On the afternoon of October 2, 2026, I noticed something unusual while working with several servers.
My Internet connection appeared normal. Websites were loading, and I was not seeing any obvious problem with my local connection.
But my servers in Singapore were behaving differently.
SSH sessions became increasingly laggy. Commands took longer to respond, and some connections eventually disconnected.
At first, I wondered whether there was a problem with the Singapore servers themselves.
I then checked a staging server we host in Malaysia.
The connection was perfectly fine.
That immediately changed how I looked at the problem.
Philippines
|
+------> Malaysia
| Normal
|
+------> Singapore
High latency
Lag
DisconnectsIf my Internet connection were the problem, I would expect both destinations to show similar symptoms.
They did not.
My initial suspicion was that something might be happening along the international route between the Philippines and Singapore.
Later that day, I saw a post describing almost exactly what I was experiencing:
“We’re noticing a possible C2C issue affecting SG-PH / HK-PH routes, with some sites not loading while others are working normally.”
That caught my attention because it closely matched what I had already been seeing.
Some destinations worked normally.
Singapore did not.
So I started investigating.
The Malaysia comparison was important because it helped separate a local Internet problem from a destination-specific or international routing problem.
PH -> Malaysia
Normal
Stable SSH
No noticeable connection issue
PH -> Singapore
High latency
Lag
Connection instability
SSH disconnectsIf my router, workstation, or local Internet connection had been the main problem, I would normally expect problems across more than one overseas destination.
Instead, the behavior changed depending on where the traffic was going.
That pointed farther upstream.
Possible causes included:
This also connects with a concept we previously discussed on PinoyLinux. Geographic proximity does not guarantee a better network path. Routing policy, peering, available capacity, and the actual path between networks can matter more than physical distance.
This idea is covered in our DNS steering series, particularly Latency, Geography, And Network Distance: What DNS Can And Cannot Know.
At this stage, however, what I had was still an observation.
I needed independent network data.
The strongest supporting evidence came from CableStatus.
At 07:00 UTC on October 2, or around 3:00 PM Philippine time, CableStatus reported a Philippines-Singapore transit delay advisory based on RIPE Atlas measurements.
The results showed:
| Route | Recent baseline | Observed latency |
|---|---|---|
| Philippines to Singapore | ~53 ms | ~177 ms |
| Malaysia to Singapore | ~11 ms | ~22 ms |
For the PH-SG measurement, CableStatus reported data from 28 independent RIPE Atlas anchors.
That placed average Philippines-to-Singapore latency at more than three times its recent baseline.
Source: CableStatus, Philippines-Singapore Corridor
CableStatus is careful about what this means. It describes the event as a telemetry-inferred transit delay, not confirmation that a particular submarine cable failed.
That distinction is important.
The measurements tell us:
Something abnormal was happening along the Philippines-Singapore network path.
They do not tell us:
A specific submarine cable was definitely cut.
That requires separate evidence.
What made the CableStatus data particularly interesting was how closely it matched my experience.
Before I saw the wider reports:
Malaysia = working normally
Singapore = slow and unstableLater, independent measurements showed that Philippines-Singapore latency had risen sharply.
This did not prove the cause, but it gave much stronger support to the idea that my Singapore servers were not the source of the problem.
The route toward Singapore had become the more likely suspect.
Another important piece of evidence came from Akamai Service Status.
Akamai reported scheduled upstream provider maintenance along network routes connecting Singapore, Hong Kong, and Japan.
According to Akamai, the maintenance window ran from September 18 through October 3, 2026.
Akamai warned that users in affected regions could experience increased latency during peak traffic periods.
More importantly, another Akamai incident update stated that connectivity problems in the APAC region were likely caused by:
upstream congestion related to unexpected maintenance on subsea cables
A later update said the upstream carrier continued maintenance on impacted submarine cables and that intermittent impact could continue until repair work was completed.
Source: Akamai Service Status
This does not prove that Akamai’s maintenance event caused the PH-SG slowdown I experienced on October 2.
But it tells us something important.
Submarine cable capacity and upstream routing around major Asian hubs were already under pressure during the same period.
That becomes relevant when traffic needs to move away from its normal path.
International networks usually have more than one possible path.
If the preferred path becomes unavailable or loses capacity, traffic can move to another route.
That redundancy is important.
But alternate routes do not have unlimited capacity.
Imagine this simplified situation:
Normal:
Philippines
|
+------------------> Singapore
Primary pathIf that path becomes unavailable:
Philippines
|
+----> Alternate carrier
|
+----> Regional hub
|
+----> SingaporeConnectivity remains available.
But now the alternate route must carry traffic it normally would not handle.
If enough traffic is moved onto it, users may begin seeing:
Higher latency
|
Packet loss
|
TCP retransmissions
|
Slow applications
|
SSH / VPN instability
|
TimeoutsThis can make an international routing problem look like an Internet connection that only works sometimes.
As reports circulated, one name repeatedly appeared:
C2C.
C2C stands for City-to-City.
It is an intra-Asia submarine cable system that forms part of the larger EAC-C2C network.
According to Submarine Networks’ C2C Cable System Overview, C2C uses a dual-ring design.
Its northern ring links:
Its southern ring links:
A simplified view of the southern portion looks like this:
Hong Kong
|
|
+-------+-------+
| |
| |
Philippines ---------+
|
|
SingaporeThe cable has landing points in the Philippines and Singapore, among other locations.
Source: C2C Cable System Overview, Submarine Networks
Telstra International confirms that it operates wholly owned EAC and C2C submarine cable systems.
Its network information describes C2C as an intra-Asia cable connecting major Asian business hubs, including the Philippines, Singapore, Hong Kong, Japan, Korea, and Taiwan.
Telstra also states that its Philippine infrastructure connects its EAC and C2C submarine cable landing stations.
Sources:
Telstra International Wholesale Network
Telstra Expands Business Offerings in the Philippines
This made the C2C reports technically plausible because the cable topology corresponds closely with the PH-SG and PH-HK routes users were discussing.
This is where we need to separate what we know from what we suspect.
Reports circulating among Philippine Internet users and network customers referred to a possible problem on the C2C PH-SG route.
Those reports fit what I experienced.
They also fit the independent PH-SG latency measurements.
The physical network topology also makes C2C a reasonable candidate.
However, at the time of writing, I had not found a public Telstra incident notice explicitly saying:
The physical C2C Philippines-Singapore submarine cable segment has been cut or is completely down.
That means we should avoid presenting that as established fact.
We can reasonably say that:
We could not yet independently confirm that:
Until an authoritative carrier or cable operator confirms the exact fault, the safer wording is:
Possible C2C involvement in a wider PH-SG international routing or capacity problem.
One of the most confusing parts of the incident was that the Internet did not appear completely broken.
Some websites loaded normally.
Others were slow.
Some did not load at all.
That actually makes sense when you look at how Internet routing works.
Your ISP does not send every Internet connection through one international path.
Traffic can follow different routes depending on:
A simplified example looks like this:
+--> Philippine CDN
| WORKING
|
Philippine ISP ----------+--> Japan / US route
| WORKING
|
+--> Malaysia
| WORKING
|
+--> Singapore
|
X
degraded
|
alternate path
|
congestion
|
latency / lossA website served through infrastructure inside the Philippines might never use the affected international route.
Another service may depend heavily on Singapore.
Another Singapore-hosted service may use a completely different carrier or cable path and remain reachable.
This is why two overseas websites can behave very differently even when accessed from the same Internet connection.
We previously discussed this concept in DNS Steering 101: How Authoritative DNS Influences Traffic Direction.
DNS steering can return different service endpoints based on signals such as:
For example:
Philippine requester
|
v
Authoritative DNS
|
+----> Manila endpoint
|
+----> Singapore endpoint
|
+----> Tokyo endpointBut the important part is that DNS selects an endpoint.
It does not control every network hop between the user and that endpoint.
So a service can correctly choose Singapore based on geography while the actual Philippines-to-Singapore network path is temporarily performing poorly.
That is one reason network distance matters more than simple geographic distance.
Large Internet platforms usually operate distributed infrastructure.
They may have:
A request from the Philippines might therefore be answered from infrastructure located locally or through a route that does not depend on the affected PH-SG path.
This creates a common troubleshooting mistake.
A user opens Facebook successfully and concludes:
“My Internet is working.”
Technically, that may be true for the path to Facebook.
It says very little about the path to a server in Singapore.
The better question is:
“Which destinations are working?”
Suppose an application operates regional endpoints:
Manila
Singapore
TokyoUnder normal conditions:
PH users -> SingaporeIf Singapore becomes unsuitable:
PH users -> TokyoA DNS steering system can influence future connections by returning another endpoint.
This concept is discussed in Health Checks In DNS Steering: From Origin Status To Answer Policy.
But this incident illustrates an important problem.
A server can be completely healthy while the network path toward it is unhealthy.
For example:
Singapore server:
CPU: Normal
Memory: Normal
Application: Running
HTTPS: Working
Server health: GOODMeanwhile:
Philippines -> Singapore:
Latency: High
Packet loss: Present
SSH: Unstable
User experience: BADBoth observations can be correct.
The server itself is healthy.
The path to the server is not.
Suppose your monitoring server is also in Singapore.
It checks your application:
Singapore monitor
|
+----> Singapore server
Latency: 2 ms
HTTP: 200
Status: HEALTHYBut Philippine users see:
Philippines
|
+----> Singapore server
Latency: 177 ms
Packet loss
TimeoutsYour monitoring platform may continue showing green.
Your users are still having problems.
This is why health measurements from multiple networks and geographic locations can provide a better picture of actual service availability.
The PinoyLinux article Health Checks In DNS Steering: From Origin Status To Answer Policy discusses why endpoint health needs to be translated into actual answer policy rather than treated as a simple green or red status.
Another relevant PinoyLinux article is Why DNS Steering Is Not Load Balancing.
DNS can influence where a client starts its connection.
Once that connection has begun, DNS is no longer carrying the packets.
For example:
DNS:
app.example.com
|
+----> Singapore IPAfter resolution:
User
|
+---- Internet route ----> Singapore IPIf the international route later becomes congested, authoritative DNS cannot repair that existing TCP session.
This matters for:
DNS can help future lookups choose a different endpoint.
It cannot move every existing connection instantly.
At the network level, BGP allows autonomous systems to advertise routes to one another.
When a preferred route disappears, another route may become available or preferred.
Simplified:
Normal:
Philippines ----------> SingaporeAfter a route change:
Philippines
|
+----> Transit Provider A
|
+----> Regional Hub
|
+----> SingaporeThe destination may still be reachable.
But that does not guarantee good performance.
The new path may:
This is one reason a routing incident can result in slow Internet instead of no Internet.
PinoyLinux also discussed this in Designing Fallback Logic For Reliable DNS Steering.
Having a fallback is important.
But having a fallback does not automatically mean that the fallback has enough capacity.
For example:
Preferred:
Singapore
Fallback:
TokyoIf a small amount of traffic fails over, Tokyo may handle it easily.
If nearly all regional traffic suddenly moves there:
Singapore traffic
|
+----------> Tokyo
|
+--> normal Tokyo traffic
|
+--> rerouted trafficthe fallback path itself may become congested.
The same principle applies to carrier networks and submarine cables.
Redundancy matters.
So does spare capacity.
SSH was where I first noticed the incident.
The connection did not immediately disappear.
It became progressively worse.
Commands responded slowly.
Typing began to feel delayed.
Some sessions eventually froze or disconnected.
SSH uses TCP.
When packets are lost, TCP retransmits them.
As packet loss and delay increase, the connection can behave like this:
Normal SSH session
|
Latency increases
|
Commands respond slowly
|
Packet retransmissions
|
Session appears frozen
|
Timeout or disconnectThe same network conditions can affect:
The application may be perfectly healthy.
The path between the two endpoints is the problem.
This incident is also a useful reminder that a speed test does not measure the entire Internet.
Suppose your speed-test server is located inside your ISP network:
Home
|
ISP
|
Local Speedtest server
500 Mbps
5 msThat tells you your local access connection is performing well.
Now consider your Singapore server:
Home
|
ISP
|
Philippine international gateway
|
Transit providers
|
Submarine cable systems
|
SingaporeThat path contains far more infrastructure.
You can therefore see:
Speedtest:
500 Mbps
Excellent
Singapore SSH:
Very slow
DisconnectingThere is no contradiction.
You tested two different network paths.
If I encounter the same situation again, I would begin with destination comparison.
For example:
ping singapore-server.example.com
ping malaysia-server.example.com
ping japan-server.example.comThen examine the route:
traceroute singapore-server.example.comOn Linux, MTR provides useful ongoing measurements:
mtr singapore-server.example.comFor a report:
mtr -rwzc 100 singapore-server.example.comOn Windows:
tracert singapore-server.example.comI would also compare the same destination from:
For example:
ISP A -> Singapore: 180 ms
ISP B -> Singapore: 55 ms
VPN -> Singapore: 60 msIf the destination performs normally through another path, that is strong evidence that the server itself is not the main issue.
Cloudflare’s public status page is another useful source when investigating regional connectivity:
Cloudflare had maintenance scheduled for its Hong Kong location on October 2 from 18:00 to 22:00 UTC, with a warning that traffic could be rerouted and users might experience increased latency.
That maintenance window occurred later than the initial PH-SG symptoms described in this article, so it should not be treated as the cause of the afternoon slowdown.
It is included here because status pages from large network operators are useful when investigating whether a problem is local, regional, or related to wider traffic changes.
After comparing the available information, several pieces line up.
Singapore connections became slow and unstable while a Malaysia-hosted server remained usable.
CableStatus reported approximately 177 ms average PH-SG latency, compared with a recent baseline of around 53 ms, across 28 RIPE Atlas anchors.
Source: CableStatus
Akamai documented upstream maintenance and congestion involving submarine cable routes around Singapore, Hong Kong, and Japan.
Source: Akamai Service Status
C2C’s southern ring connects Hong Kong, the Philippines, and Singapore.
Source: Submarine Networks
Telstra describes EAC and C2C as wholly owned submarine cable systems serving major intra-Asia routes.
Sources:
Telstra International Wholesale
Telstra Philippines Network Expansion
The available evidence does not yet prove that the physical C2C PH-SG cable was cut.
That distinction is important.
A responsible incident analysis should distinguish:
Observed:
PH-SG network degradation
Measured:
Large PH-SG latency increase
Reported:
Possible C2C PH-SG issue
Confirmed:
Regional subsea maintenance
Not yet confirmed:
Physical C2C PH-SG cable breakIf Telstra or another authoritative carrier later releases a detailed incident report, this article can be updated.
Looking back, the most useful early clue was not a complicated monitoring platform.
It was this:
Malaysia = normal
Singapore = slowThat immediately changed the troubleshooting direction.
Instead of asking:
“Why is my Internet slow?”
I started asking:
“Why is this particular destination slow?”
That is a much more useful question for a system administrator or network engineer.
When the Internet behaves strangely, ask:
Which destinations are working, and which ones are not?
Then ask:
Are those destinations using the same network path?
Those two questions can quickly help distinguish a local connection problem from a wider routing or international transit issue.
The October 2 incident provides a practical example of several concepts already covered in the PinoyLinux DNS steering series.
Explains how authoritative DNS can influence which regional endpoint a requester receives, and why the most suitable endpoint is not necessarily determined by geography alone.
Explains why DNS can influence where a connection begins but does not control the network path once the client has connected.
Discusses what should happen when a preferred endpoint becomes unavailable or unsuitable.
Explains why endpoint health needs to influence routing decisions and why a technically running server may still be unsuitable for some users.
Explains the difference between preparing routing decisions and handling live DNS queries.
These articles explain the theory.
The October 2 PH-SG incident gives us a real-world example of why those concepts matter.
CableStatus, Philippines-Singapore Corridor
RIPE Atlas-based measurements showing the October 2 PH-SG transit delay advisory, including approximately 177 ms average latency compared with a recent baseline of approximately 53 ms.
https://cablestatus.com/?corridor=philippines-singapore
Akamai Service Status
Akamai incident and maintenance notices covering upstream provider maintenance, increased APAC latency, congestion, and subsea cable maintenance involving Singapore, Hong Kong, and Japan.
Telstra International Wholesale Network
Telstra information about its wholly owned East Asia Crossing and City-to-City submarine cable systems.
https://www.telstrainternational.com/en/wholesale/wholesale-updates
Telstra Expands Business Offerings in the Philippines
Telstra information about its Philippine infrastructure, EAC and C2C landing stations, and the EAC-C2C network.
Submarine Networks, C2C Cable System Overview
Background, topology, landing stations, and southern-ring information for the C2C submarine cable system.
https://www.submarinenetworks.com/en/systems/intra-asia/eac-c2c/c2c-cable-system-overview
Cloudflare Status
Regional Cloudflare network status and scheduled data-center maintenance information.
https://www.cloudflarestatus.com/
DNS Steering 101: How Authoritative DNS Influences Traffic Direction
https://www.pinoylinux.org/dns-steering-101-how-authoritative-dns-influences-traffic-direction/
Why DNS Steering Is Not Load Balancing
https://www.pinoylinux.org/why-dns-steering-is-not-load-balancing/
Designing Fallback Logic For Reliable DNS Steering
https://www.pinoylinux.org/designing-fallback-logic-for-reliable-dns-steering/
Health Checks In DNS Steering: From Origin Status To Answer Policy
https://www.pinoylinux.org/health-checks-in-dns-steering-from-origin-status-to-answer-policy/
The Control Plane And Data Plane Of DNS Steering
https://www.pinoylinux.org/the-control-plane-and-data-plane-of-dns-steering/