- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 18of 100
What to do
Check whether your product depends on Infisical. 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-06 19:46 UTC and 2026-02-23 15:20 UTC may need a replay.Subscribe to Infisical's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=infisical works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Infisical 4
- investigating
We're investigating this issue. We'll provide an update shortly as we dig further into our metrics.
provider
- identified
We've identified the cause as a recent DB migration which has caused lock contention. Our team is working on a fix.
provider
- monitoring
A fix has been deployed and we're monitoring the results. Services should be returning to normal. We'll confirm full resolution shortly.
provider
- resolved
This incident has been resolved. All services are operating normally.
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-4b69d0d5d6
Is Infisical still down?
No, this incident was resolved 2026-02-23 15:20 UTC. For Infisical's live state, see https://down.guide/infisical.
How long did it last?
0m, from 2026-05-06 19:46 UTC to 2026-02-23 15:20 UTC, by the times Infisical posted.
What caused it?
Infisical hasn't published a root cause. If it does, it shows here.
Where does this come from?
Infisical's official status page, https://status.infisical.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.