Percy: Percy builds were degraded for ~50 mins due to an existing Google Cloud Provider incident [7.30 AM PDT to 8.20 AM PDT on 13th July]

What to do

Check whether your product depends on Percy. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-07-13 16:20 UTC and 2026-07-13 02:00 UTC may need a replay.
Subscribe to Percy's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=percy works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedJul 13, 2026, 2:00 AM UTC
Percy builds were degraded for ~50 mins [7.30 AM PDT to 8.20 AM PDT on 13th July] due to an existing Google Cloud Provider incident We have moved our infrastructure from the impacted GCP node pool and are back to normal processing GCP incident details - https://console.cloud.google.com/servicehealth/incidentDetails/projects%2Fpercy-prod%2Flocations%2Fglobal%2Fevents%2FZBYNZVS?project=percy-prod&tab=full-history
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Percy still down?

No, this incident was resolved 2026-07-13 02:00 UTC. For Percy's live state, see https://down.guide/percy.

How long did it last?

0m, from 2026-07-13 16:20 UTC to 2026-07-13 02:00 UTC, by the times Percy posted.

What caused it?

Percy hasn't published a root cause. If it does, it shows here.

Where does this come from?

Percy's official status page, https://status.percy.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.