Is Codemagic Down?

No — Codemagic is up

Codemagic's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 549 ms

Right now

The verdict is the worse of these two. How we decide

Codemagic's status page

status.codemagic.io · read 4 minutes ago · checked every 3 minutes

Operational

Codemagic's components, as its status page reports them
Component	Status
macOS machines	Operational
Linux machines	Operational
Windows machines	Operational
App Preview	Operational
CodePush server	Operational
Website	Operational
Third Party: Bitbucket → API	Operational
Third Party: GitHub → API	Operational
Third Party: GitLab → API	Operational
Third Party: Google Cloud Platform	Operational

Open their status page

FlareWarden checks

codemagic.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 549 ms
Checked: 5 hours ago

By region

Ashburn reachable, 320 ms
Dallas reachable, 355 ms
Frankfurt reachable, 787 ms
Johannesburg reachable, 1389 ms
London reachable, 493 ms
Los Angeles reachable, 170 ms
Newark reachable, 308 ms
São Paulo reachable, 576 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	104 ms	1 ms	4 ms	320 ms
Dallas	148 ms	0 ms	4 ms	355 ms
Frankfurt	272 ms	1 ms	4 ms	779 ms
Johannesburg	119 ms	1 ms	6 ms	1389 ms
London	22 ms	3 ms	7 ms	493 ms
Los Angeles	110 ms	3 ms	7 ms	169 ms
Newark	144 ms	2 ms	4 ms	308 ms
São Paulo	37 ms	1 ms	4 ms	576 ms

We check that codemagic.io loads, not every feature behind it. Test it yourself

History

Incidents Codemagic reported

Since Oct 27, 10 days · from status.codemagic.io

Incidents: 1
Major or critical: 0
Median to resolve: 21m

Untitled incident
Unrated · Nov 4
lasted 21m

Codemagic website availability

Measured by FlareWarden · codemagic.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 483ms

Last 30 days

10-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of codemagic.io from multiple regions every 6 hours. Codemagic's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 10 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Codemagic does

Codemagic is a hosted CI/CD service for mobile apps from Nevercode. Teams connect a repository on GitHub, GitLab or Bitbucket, and Codemagic builds, tests and publishes Flutter, React Native, native iOS and Android, Ionic and Unity apps on its macOS, Linux and Windows build machines. It also hosts a CodePush service for over-the-air React Native updates, so an outage can hold up store releases and app updates alike.

What an outage looks like

Builds sit in the queue, fail with 'Something Went Wrong' errors when tools cannot be fetched from GitHub, commits stop triggering builds, or the web app fails to load apps and builds. Codemagic's status page reports macOS, Linux and Windows machines as separate rows, so one platform can queue while the others run, and tracks App Preview, the CodePush server, GitHub, GitLab, Bitbucket and Google Cloud separately.

What to do about it

Check status.codemagic.io and find the row for the machine type your build needs, since macOS queues are reported apart from Linux and Windows ones. In past queue incidents Codemagic reported the waiting builds starting once the fault was fixed. If builds fail while fetching dependencies, check GitHub's status too. Codemagic also posts disruptions in its GitHub Discussions; support is the in-app chat or support@codemagic.io.

Is it down for everyone, or just you?

If this page says Codemagic is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Codemagic outage FAQ

Why are my Codemagic builds stuck in the queue?

Usually because no machine of that type can start. On August 4, 2026 a resource shortage in Codemagic's Google Cloud region kept Linux and Windows builds queued for about 19 hours, and on April 18, 2026 resource exhaustion in GCP zone us-east1-d did the same until Codemagic switched zones. macOS queues have their own causes: on October 13, 2026 misuse of the service lengthened M2 queues for about seven hours.

Does a GitHub outage affect Codemagic builds?

Yes. Codemagic says its builds use tools and libraries installed from GitHub, so GitHub problems can stop builds from starting or produce 'Something Went Wrong' errors, as on August 12 and August 17, 2026, when Codemagic marked its GitHub API row degraded for several hours. GitHub, GitLab and Bitbucket APIs each have a row on Codemagic's status page, so check the one for your Git host as well.

Does a Google Cloud outage affect Codemagic?

It has. On June 12, 2025 Codemagic said a Google Cloud problem had taken down its infrastructure; services began returning about 80 minutes later with longer queues while the backlog cleared, and failing external APIs caused 'Something Went Wrong' build errors until about 10:51 PM UTC. Google Cloud Platform has its own row on Codemagic's status page, and GCP capacity shortages have since queued Linux and Windows builds.

Is CodePush affected when Codemagic builds are down?

Not necessarily. The CodePush server, Codemagic's hosted over-the-air update service for React Native, has its own row on the status page, apart from the build machines. On September 22, 2026 automated monitoring opened three CodePush availability incidents between 17:29 and 20:44 UTC, the longest about 70 minutes, and none listed a build machine. Check that row before retrying a release.

What does the check on this page measure?

It loads codemagic.io/login, the sign-in page of Codemagic's web app; the site's root redirects to a marketing page instead. It does not sign in, list apps, start a build, wait for a build machine, reach the CodePush server or call GitHub. A green result means the sign-in page answers, not that builds start; queues show on the machine rows of Codemagic's status page.

How we measure this

We request Codemagic's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Codemagic publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Codemagic itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Codemagic goes down

We check Codemagic every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required