WarpBuild - Notice history

Experiencing partial outage

Dashboard - Operational

100% - uptime
Oct 2025
Nov 2025
Dec 2025

API - Major outage

100% - uptime
Oct 2025
Nov 2025
Dec 2025

GitHub Runners - Major outage

99% - uptime
Oct 2025
Nov 2025
Dec 2025

Docker Builders - Major outage

99% - uptime
Oct 2025
Nov 2025
Dec 2025
Operational

Third Party: Github → Actions - Operational

Third Party: Github → API Requests - Operational

Third Party: Github → Webhooks - Operational

Third Party: Github → Git Operations - Operational

Third Party: Github → Pull Requests - Operational

Notice history

Dec 2025

Upstream GitHub issue - API and actions degraded
  • Resolved
    Resolved

    The GitHub incident doesn't seem to have any real impact.

  • Identified
    Identified

    API Requests and Actions are experiencing degraded performance. https://www.githubstatus.com/incidents/xntfc1fz5rfb

Runners are not allocated or are failing to start
  • Resolved
    Resolved

    This incident has been resolved. A full post-incident report will be published shortly along with mitigation steps.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result. Runners are working as usual now.

  • Identified
    Identified

    We are working on a fix for this

  • Investigating
    Investigating

    Runners were either not starting or failing to start with a 503 after allocation.

WarpBuild Runners are not starting with a "failed to fetch" error
  • Postmortem
    Postmortem

    The issue was caused because of a faulty change to the auth service during a refactor. This was not expected to have an impact on the runner allocation flow. This was reverted to fix the error. We are also going to add tests to ensure issues of this nature do not creep through.

  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.

Nov 2025

Github reporting degradation for Actions
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    GitHub applied a mitigation. We are seeing recovery and monitoring the situation.

  • Identified
    Identified

    GitHub is investigating an actions related outage -

    https://www.githubstatus.com/incidents/zs5ccnvqv64m.

    This is leading to queued jobs not getting picked up.

GitHub reporting failures with Git operations
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    There is an increase in job failures because of an incident with Github https://www.githubstatus.com/incidents/5q7nmlxz30sk.

    We are monitoring the situation.

WarpBuild services are down because of cloudflare global outage
  • Resolved
    Resolved

    WarpBuild is seeing full recovery.

  • Investigating
    Investigating

    This issue is being added retroactively because the status page was also down.

    https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Oct 2025

Remote docker builders and arm64 runners are not functional because of the AWS outage
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We are seeing full recovery in the impacted services:

    • Docker builders

    • arm64 runners

    • custom runners

    • Snapshot runners

    • Windows runners

    x64 runners were not impacted and are continuing to work as usual.

  • Update
    Update

    Windows runners are also impacted because of the AWS outage.

  • Identified
    Identified

    Remote docker builders and arm64 runners are not functional because of the AWS outage

    There may be some delay in jobs getting picked up because of queueing and image related delays.

    Windows, custom runners, and snapshot runners are also affected.

Oct 2025 to Dec 2025

Next