- Level
- confirmed
- Worst impact
- Degraded
- Components
- Prisma Postgres
- Regions
- eu, eu-central-1, us, us-east-1
- Down Index
- 35of 100
What to do
Check whether you use Prisma Data Platform Prisma Postgres in eu, eu-central-1, 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 2h 5m it lasted.
Anything that failed between 2026-01-27 18:56 UTC and 2026-01-27 21:01 UTC may need a replay.Subscribe to Prisma Data Platform's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=prisma works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Prisma Data Platform 3
- investigating
Prisma Postgres Direct TCP is experiencing degraded service in our US East (Newark) and EU Central (Frankfurt) regions. We have identified the cause and are investigating a fix.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been 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-18959a1862
Is Prisma Data Platform still down?
No, this incident was resolved 2026-01-27 21:01 UTC. For Prisma Data Platform's live state, see https://down.guide/prisma.
How long did it last?
2h 5m, from 2026-01-27 18:56 UTC to 2026-01-27 21:01 UTC, by the times Prisma Data Platform posted.
What was affected?
Prisma Data Platform named Prisma Postgres in eu, eu-central-1, us, us-east-1.
What caused it?
Prisma Data Platform hasn't published a root cause. If it does, it shows here.
Where does this come from?
Prisma Data Platform's official status page, https://www.prisma-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.