- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us, us-east-1
- Down Index
- 26of 100
What to do
Check whether you use Percy in us, us-east-1. 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 2025-10-20 13:30 UTC and 2025-10-20 13: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
We are currently observing degraded performance from 6.30 AM - 7.45 AM PDT in Percy, primarily affecting build processing times and dashboard responsiveness. Our investigation indicates that this is due to an ongoing AWS US-East-1 regional outage impacting one of our critical third-party services - LaunchDarkly - which we use for configuration management and feature flag delivery. We are actively monitoring the situation and working with teams to mitigate impact. Builds may take longer to start or complete until the upstream issue is resolved.
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-b0d6e0b5e5
Is Percy still down?
No, this incident was resolved 2025-10-20 13:30 UTC. For Percy's live state, see https://down.guide/percy.
How long did it last?
0m, from 2025-10-20 13:30 UTC to 2025-10-20 13:30 UTC, by the times Percy posted.
What was affected?
Percy named in us, us-east-1.
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.