Codemagic Outage History

Codemagic is up right now

Codemagic had 6 outages in the last 2 years totaling 35h 15m of downtime — averaging 0.2 incidents per month.

There were 6 Codemagic outages since April 28, 2026 totaling 35h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.codemagic.io

Minor August 17, 2026

Intermittent issues with GitHub API

Detected by Pingoru
Aug 17, 2026, 02:35 PM UTC
Resolved
Aug 17, 2026, 07:00 PM UTC
Duration
4h 25m
Affected: Third Party: GitHub → API
Timeline · 2 updates
  1. identified Aug 17, 2026, 02:35 PM UTC

    GitHub status page is reporting issues that may affect downloading tools and dependencies from GitHub, potentially causing issues with builds.

  2. resolved Aug 17, 2026, 07:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2026

GitHub has intermittent issues which leads to SWW errors in builds

Detected by Pingoru
Aug 12, 2026, 04:45 PM UTC
Resolved
Aug 12, 2026, 11:00 PM UTC
Duration
6h 15m
Affected: Third Party: GitHub → API
Timeline · 2 updates
  1. identified Aug 12, 2026, 04:45 PM UTC

    According to GitHub status page, there are issues that GitHub is currently investigating. Builds use tools and libraries that are installed from GitHub therefore sometimes fail to start, however our monitoring systems show that the failure rate is quite low. We will post an update as soon as the issue is resolved.

  2. resolved Aug 12, 2026, 11:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 4, 2026

Linux and Windows builds remain queued due to external outage

Detected by Pingoru
Aug 04, 2026, 05:30 PM UTC
Resolved
Aug 05, 2026, 12:48 PM UTC
Duration
19h 18m
Affected: Linux machinesWindows machines
Timeline · 3 updates
  1. identified Aug 04, 2026, 05:30 PM UTC

    We are experiencing a resource shortage in our GCP region. Therefore, there's a lack of VMs starting for Linux and Windows builds, which remain queued. We will do our best to mitigate this as soon as possible.

  2. monitoring Aug 04, 2026, 10:30 PM UTC

    We implemented a fix and are currently monitoring the result. We had to temporarily alter the config of our VMs but we expect this not to affect the build performance significantly. We will continue to monitor the situation and revert the change as soon as we see it fixed on the provider's side.

  3. resolved Aug 05, 2026, 12:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 27, 2026

macOS and Linux X2 builds remain queued

Detected by Pingoru
May 27, 2026, 10:32 AM UTC
Resolved
May 27, 2026, 11:14 AM UTC
Duration
42m
Affected: macOS machinesLinux machines
Timeline · 2 updates
  1. investigating May 27, 2026, 10:32 AM UTC

    We are currently investigating this incident.

  2. resolved May 27, 2026, 11:14 AM UTC

    This incident was caused by an internal configuration issue that has now been resolved. All queued builds are now starting as expected.

Read the full incident report →

Minor May 19, 2026

macOS Builds Queued

Detected by Pingoru
May 19, 2026, 09:41 PM UTC
Resolved
May 20, 2026, 12:10 AM UTC
Duration
2h 29m
Affected: macOS machines
Timeline · 2 updates
  1. investigating May 19, 2026, 09:41 PM UTC

    We are experiencing an infrastructure issue that is causing some macOS builds to remain queued.

  2. resolved May 20, 2026, 12:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 28, 2026

Delays in Automatic Build Triggering

Detected by Pingoru
Apr 28, 2026, 07:55 AM UTC
Resolved
Apr 28, 2026, 10:00 AM UTC
Duration
2h 5m
Affected: macOS machinesLinux machinesWindows machines
Timeline · 2 updates
  1. monitoring Apr 28, 2026, 07:55 AM UTC

    We experienced an issue with webhook processing that caused delays in build triggering for some users.

  2. resolved Apr 28, 2026, 10:00 AM UTC

    The issue has now been resolved, and systems are operating normally. We apologize for any inconvenience caused and appreciate your patience.

Read the full incident report →