- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
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-05-12 08:56 UTC and 2026-05-11 11:30 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.
Updates from Percy 1
- resolved
Between 4:30 AM and 9:30 AM PDT on May 11, 2026, some Percy builds took longer than usual to complete due to increased database contention. Builds were not lost - only delayed. The issue has been mitigated and processing times are back to normal. We're investigating the root cause to prevent recurrence in future.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-dca1f15ddc
Is Percy still down?
No, this incident was resolved 2026-05-11 11:30 UTC. For Percy's live state, see https://down.guide/percy.
How long did it last?
0m, from 2026-05-12 08:56 UTC to 2026-05-11 11:30 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.