New deployments timing out in ap-southeast-1
New deployments to ap-southeast-1 are working again.
The latest update from Unkey.
State
Resolved
Started
36 d ago
2026-09-26 15:36 UTC
Lasted
36 min
until 2026-09-26 16:12 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
20 min 56%
Monitoring
16 min 44%
Updates
Times in UTCAs posted by Unkey
New deployments to ap-southeast-1 are working again.
We have switched out the CDN layer in our registry provider and are seeing deployments recover.
The network between our image registry and our ap-southeast-1 clusters has slowed down. You may see deployments in that region timing out. Other regions and running applications are not affected
Unkey in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
36 min
This incident
About the median
Follow Unkey
Your coding agent knows when Unkey is down, and tells you when a failure is theirs, not yours. You can also get Unkey incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "unkey" and tell me if Unkey has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=unkey/feed subscribe https://outages.live/feed.xml?providers=unkeyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane