outages.live
Live

Unkey

Unkey is operational

Checked 49 s ago Operational

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

36 min

Longest incident

36 min

Components

19
App Operational
90 days agoNo incidentsToday
aws us-east-1 Operational
90 days agoNo incidentsToday
aws us-east-2 Operational
90 days agoNo incidentsToday
aws us-west-2 Operational
90 days agoNo incidentsToday
awseu-central-1 Operational
90 days agoNo incidentsToday
awsap-northeast-1 Operational
90 days agoNo incidentsToday
aws ap-south-1 Operational
90 days agoNo incidentsToday
aws sa-east-1 Operational
90 days agoNo incidentsToday
aws ap-southeast-2 Operational
90 days agoNo incidentsToday
GitHub Hooks Operational
90 days agoNo incidentsToday
Builds Operational
90 days agoNo incidentsToday
aws us-west-2 Operational
90 days agoNo incidentsToday
aws eu-central-1 Operational
90 days agoNo incidentsToday
aws us-east-1 Operational
90 days agoNo incidentsToday
aws ap-southeast-1 Operational
90 days agoNo incidentsToday
aws us-east-1 Operational
90 days agoNo incidentsToday
aws us-west-2 Operational
90 days agoNo incidentsToday
aws eu-central-1 Operational
90 days agoNo incidentsToday
aws ap-southeast-1 Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 26, 2026

Duration36 min15:36 to 16:12New deployments timing out in ap-southeast-1Partial outage

New deployments to ap-southeast-1 are working again.

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=unkey
Slack
/feed subscribe https://outages.live/feed.xml?providers=unkey

Go from tracking outages to fixing production issues with Polylane.

Try Polylane