Is Unkey down?

Last checked 4m ago
Current status
Unkey is up

No incidents right now.

  • Official status page: status.unkey.com
  • Checked every 5 minutes
  • 19 components tracked

Unkey is operational right now. Last checked 4m ago; the most recent incident resolved 35d ago.

Real-time Unkey status, recent outages, and incident history: pulled directly from Unkey's official status page at status.unkey.com every 5 minutes. Pingoru tracks 19 Unkey services and has captured 2 incidents in the last 90 days (98.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Unkey reports a new incident, free for 3 monitors, no credit card.

Users who monitor Unkey also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Unkey uptime 98.83% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 35m
    Started Sep 26, 2026, 03:36 PM UTC · Resolved Sep 26, 2026, 04:12 PM UTC
    Builds
    Timeline · 3 updates
    • investigating · Sep 26, 2026, 03:36 PM UTC

      Status: 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 Affected components Builds (Partial outage)

    • monitoring · Sep 26, 2026, 03:56 PM UTC

      Status: Monitoring We have switched out the CDN layer in our registry provider and are seeing deployments recover. Affected components Builds (Partial outage)

    • resolved · Sep 26, 2026, 04:12 PM UTC

      Status: Resolved New deployments to ap-southeast-1 are working again. Affected components Builds (Operational)

    Latest: Status: Resolved New deployments to ap-southeast-1 are working again. Affected components Builds (Operational)

  2. Resolved –
    Started Aug 04, 2026, 11:05 AM UTC · Resolved Aug 04, 2026, 11:05 AM UTC
    Appaws us-east-1aws us-east-2aws us-west-2awseu-central-1awsap-northeast-1aws ap-south-1aws sa-east-1aws ap-southeast-2GitHub Hooks
    Timeline · 2 updates
    • resolved · Aug 04, 2026, 11:05 AM UTC

      Status: Resolved Problem: A brief connectivity issue between our control plane and data plane prevented users from creating or deploying new applications. Impact: For about 15 minutes, users were unable to create or deploy new applications, and stale application states could be shown in the dashboard. Existing applications were not affected. Causes: An uncoordinated rollout of two separate systems caused a brief connectivity issue between our control plane and data plane. Affected components awseu-central-1 (Operational) aws us-west-2 (Operational) aws us-west-2 (Operational) aws ap-southeast-1 (Operational) App (Operational) aws ap-south-1 (Operational) aws us-west-2 (Operational) aws eu-central-1 (Operational) aws us-east-1 (Operational) aws sa-east-1 (Operational) Builds (Operational) awsap-northeast-1 (Operational) GitHub Hooks (Operational) aws us-east-1 (Operational) aws eu-central-1 (Operational) aws ap-southeast-1 (Operational) aws us-east-1 (Operational) aws us-east-2 (Operational) aws ap-southeast-2 (Operational)

    • resolved · Aug 04, 2026, 11:21 AM UTC

      Status: Resolved Problem: A brief connectivity issue between our control plane and data plane prevented users from creating or deploying new applications. Impact: For about 15 minutes, users were unable to create or deploy new applications, and stale application states could be shown in the dashboard. Existing applications were not affected. Causes: An uncoordinated rollout of two separate systems caused a brief connectivity issue between our control plane and data plane. Affected components aws us-east-1 (Operational) aws us-east-2 (Operational) aws us-east-1 (Operational) aws us-west-2 (Operational) aws ap-southeast-1 (Operational) awseu-central-1 (Operational) awsap-northeast-1 (Operational) aws ap-southeast-1 (Operational) aws ap-south-1 (Operational) aws sa-east-1 (Operational) GitHub Hooks (Operational) Builds (Operational) aws us-east-1 (Operational) aws ap-southeast-2 (Operational) aws us-west-2 (Operational) aws us-west-2 (Operational) aws eu-central-1 (Operational) aws eu-central-1 (Operational) App (Operational)

    Latest: Status: Resolved Problem: A brief connectivity issue between our control plane and data plane prevented users from creating or deploying new applications. Impact: For about 15 minu…

Incident record

Since April 2026 · incident.io · 19 components checked every 5 minutes
2incidents recorded
2last 12 months
2last 90 days
18 minutestypical duration, 12 months

The longest incident in the last year, New deployments timing out in ap-southeast-1 on September 26, 2026, ran for 35 minutes.

Most affected components, last 12 months

  • Builds2
  • App1
  • GitHub Hooks1
  • aws ap-south-11
  • aws ap-southeast-11

Latest incidents

  • New deployments timing out in ap-southeast-1 September 26, 2026 · 35 minutes · degraded service

    Status: Investigating The network between our image registry and our ap-southeast-1 clusters has slowed down. You may see deployments in that region timing…

  • Unable to create or deploy new apps August 4, 2026 · under a minute · degraded service

    Status: Resolved Problem: A brief connectivity issue between our control plane and data plane prevented users from creating or deploying new applications.…

Outage history

Past 90 days · 2 incidents View full outage history →