Unkey logo

Is Unkey Down?

Developer ToolsLive status, outages, and incident history

No. Unkey is up right now.

Every monitored Unkey system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Unkey breaks

Unkey is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Unkey status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Unkey Status Summary

As of 17:16 UTC on 14 November 2026, Unkey is operational. PulsAPI checked Unkey's official status page and found 13 of 13 components operational, with no active incidents. The latest incident, "New deployments timing out in ap-southeast-1", was on Sep 26, 2026 and lasted 35 min.

Cite as: PulsAPI, “Unkey status”, checked 14 November 2026, 17:16 UTC. https://www.pulsapi.com/services/unkey

Unkey Component Status

The main Unkey systems on this page. All 13 are operational right now.

13operational
App
Operational
aws ap-south-1
Operational
aws ap-southeast-1
Operational

10 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking aws ap-southeast-2, aws eu-central-1, aws sa-east-1, aws us-east-1, aws us-east-2, aws us-west-2, awsap-northeast-1, awseu-central-1, Builds, GitHub Hooks.

See all of them free

Component statuses may change independently during partial outages.

Recent Unkey Outages & Incidents

Incident history from the official Unkey status page, including resolution updates.

New deployments timing out in ap-southeast-1Resolved Sep 26, 2026 · 35 minResolved

New deployments to ap-southeast-1 are working again. --- [2026-09-26T15:56:43Z] (monitoring) We have switched out the CDN layer in our registry provider and are seeing deployments recover. --- [2026-09-26T15:36:26Z] (investigating) 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 Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Unkey incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Unkey Outage Reports

Problems reported by engineers using Unkey. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Unkey problems reported yet.

Something wrong with Unkey on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Unkey

Is Unkey down? Its official status page at status.unkey.com reports on 13 components, including App, Builds and GitHub Hooks. PulsAPI checks it every few minutes and can alert you when Unkey reports an incident.

Unkey Status FAQ

Is Unkey down right now?

The verdict at the top of this page comes from the latest poll of the official Unkey status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Unkey is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Unkey recovers.

How do I check Unkey uptime history?

PulsAPI tracks Unkey uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Unkey changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Unkey outages?

PulsAPI reads the official Unkey status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Unkey components?

Yes. PulsAPI monitors 13 individual Unkey components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Unkey goes down?

Yes. Create a free account and subscribe to Unkey: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Unkey to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Unkey problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Unkey?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Unkey plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Unkey with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services