Semaphore incident

Slow job processing on e2 machine types

Minor Vendor's status page →

Resolved after 3 hours 38 minutes, affecting Semaphore, on October 2, 2025.

monitoring Oct 02, 2025, 09:56 PM UTC

A fix has been implemented and we are monitoring the results.

Started
Oct 02, 2025, 06:48 PM UTC
Resolved
Oct 02, 2025, 10:26 PM UTC
Duration
3h 38m
Detected by Pingoru
Oct 02, 2025, 06:48 PM UTC

Affected components

Semaphore

Update timeline

  1. investigating Oct 02, 2025, 06:48 PM UTC

    We are currently investigating this issue.

  2. investigating Oct 02, 2025, 07:27 PM UTC

    We are continuing investigating this issue.

  3. identified Oct 02, 2025, 08:00 PM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Oct 02, 2025, 08:46 PM UTC

    We are continuing to work on a fix for this issue.

  5. identified Oct 02, 2025, 09:18 PM UTC

    We're finalizing a fix for this issue.

  6. identified Oct 02, 2025, 09:52 PM UTC

    We are continuing to work on a fix for this issue.

  7. monitoring Oct 02, 2025, 09:56 PM UTC

    A fix has been implemented and we are monitoring the results.

  8. resolved Oct 02, 2025, 10:26 PM UTC

    This incident has been resolved.

Your product runs on more than Semaphore

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Cloudflare Amazon Web Services Twilio Stripe Slack Okta Figma GitHub Datadog Vercel OpenAI Google Cloud
Add your stack →