Semaphore incident

Degraded performance on r1-standard machines

Resolved after 6 hours 11 minutes, affecting Semaphore, on August 25, 2026.

identified Aug 25, 2026, 02:17 PM UTC

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

Started
Aug 25, 2026, 08:35 AM UTC
Resolved
Aug 25, 2026, 02:47 PM UTC
Duration
6h 11m
Detected by Pingoru
Aug 25, 2026, 08:35 AM UTC

Affected components

Semaphore

Update timeline

  1. investigating Aug 25, 2026, 08:35 AM UTC

    We are currently investigating this issue.

  2. identified Aug 25, 2026, 08:44 AM UTC

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

  3. monitoring Aug 25, 2026, 09:19 AM UTC

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

  4. monitoring Aug 25, 2026, 12:57 PM UTC

    We are continuing to monitor for any further issues.

  5. identified Aug 25, 2026, 02:00 PM UTC

    We have observed continued impact while monitoring. The issue remains identified, and our team is working on a resolution.

  6. identified Aug 25, 2026, 02:17 PM UTC

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

  7. resolved Aug 25, 2026, 02:47 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.

Add your stack →