- 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-02-16 15:49 UTC and 2026-02-07 21: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.
Updates from Percy 1
- resolved
- Between February 8, 2026 (10:30 AM – 2:30 PM UTC) and February 9, 2026 (12:00 PM – 1:30 PM UTC) some customers may have noticed incorrect visual diffs on Percy (Safari on iPhone) - The issue occurred due to an incorrect screenshot capture where a “connection not private” error page was rendered instead of the expected page - The impact was limited, affecting a very small percentage of builds across a small number of organisations - Our engineering team has identified and addressed the underlying issue - All Percy services are now operating normally We sincerely apologise for any confusion or inconvenience this may have caused
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-370491e71e
Is Percy still down?
No, this incident was resolved 2026-02-07 21:00 UTC. For Percy's live state, see https://down.guide/percy.
How long did it last?
0m, from 2026-02-16 15:49 UTC to 2026-02-07 21: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.