Philippines Internet Restored

The internet is up globally on Sunday, October 4. The main story is a recovery: Philippine carriers say service is back to normal after Friday's subsea cable cut. The major cloud providers (AWS, Google Cloud, Azure) report no active incidents. The issues still open elsewhere are minor and product-specific.

**Philippines: service restored after subsea cable cut (recovering)**

The Philippines–Singapore cable segment went offline on October 2, and the Philippines–Hong Kong link was also affected. For two days, users had slow and intermittent access to overseas content. As of 4:30 p.m. local time today (08:30 UTC), PLDT reports full restoration of its network services nationwide. Globe says it has restored mobile and broadband service after the cable landing station in the Philippines reactivated the system, and it is still investigating the exact nature and location of the fault. Converge moved affected traffic onto alternative submarine cables and is monitoring connections to Singapore-hosted apps and sites. No cause has been confirmed, and it is not yet clear whether the cable itself has been physically repaired, so some performance variation is possible while operators keep monitoring. Sources: [NewsBytes.PH](newsbytes.ph), [Rappler](rappler.com), [GizGuide](gizguide.com).

**Other open, limited-scope issues**

**Cloudflare:** the Workers Builds problem that began at 05:55 UTC on October 3 (builds failing to start) has had a fix in place since 08:55 UTC that day and is still marked as monitoring. Deployed Workers were not reported as affected. Cloudflare's network map also shows its usual scattered data-center reroutes and maintenance, with no broad incident declared. ([Cloudflare Status](cloudflarestatus.com))

**Twilio:** a new carrier-specific issue opened today, with SMS delivery delays from some Twilio numbers to Cellcom Israel (monitoring). Older MMS issues with GCI (US) and Australian carriers are still open. ([Twilio Status](status.twilio.com))

**Akamai:** the APAC origin-connectivity incident that has been open since September 22 is still in monitoring. ([Akamai Status](akamaistatus.com))

**Zoom:** some Polycom devices are still going offline (open since September 25). ([Zoom Status](zoomstatus.com))

**Regional connectivity signals**

IODA flagged a connectivity drop in Vientiane, Laos, starting around 07:55 UTC today. It is a low-confidence, single-measurement signal, and Laos has had several similar short disruptions since August, so treat it as unconfirmed. ([IODA via Voidly](voidly.ai))

**Recently resolved (past 72 hours)**

**Cloudflare:** from 21:46 to 21:57 UTC on October 2, CDN configuration changes and cache purges issued from the dashboard saw elevated errors. API purges were unaffected. ([Cloudflare incident](cloudflarestatus.com))

**All clear at:** AWS, Google Cloud, Azure, Azure DevOps, GitHub, OpenAI, Anthropic (Claude), Discord, Atlassian, Slack, Vercel, Heroku, DigitalOcean, Stripe, Cursor, Groq, ElevenLabs, Cohere and Stability AI. Meta's status page could not be read on this run, and none of the outage reports we checked mentioned a Facebook, Instagram or WhatsApp disruption.