Skip to content

Incident detail

Delays in job processing

Resolved incidentCritical1 affected service

Timeline window

to

Get alerted the next time Semaphore breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update Semaphore posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    We are currently investigating this issue.

  2. Identified

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

  3. Identified

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

  4. Identified

    We’ve identified network connectivity issues between our control plane and build servers. We’re actively working to restore normal service.

  5. Identified

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  6. Identified

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  7. Identified

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  8. Identified

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  9. Identified

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

  10. Identified

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

  11. Identified

    We’re still working to resolve the network connectivity issues between our control plane and build servers. We’ll share another update as soon as we have more information.

  12. Identified

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

  13. Identified

    Our team is continuing to work on a fix for this issue.

  14. Identified

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

  15. Identified

    Our engineering team is actively working to resolve this issue.

  16. Monitoring

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

  17. Monitoring

    We are continuing to monitor for any further issues.

  18. Monitoring

    Our team is still monitoring the results.

  19. Resolved

    This incident has been resolved.

Keep exploring

More from Semaphore

Neighboring incidents on Semaphore's timeline and the rest of their record on OutageDeck.