Bluesky vs Prisma: reliability
In the last 60 days, Bluesky had 13 incidents (median fix 45 min) and Prisma had 9 incidents. Prisma broke less often.
Side by side, last 60 days
Bluesky's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Bluesky: waxcap PDS maintenance | high | 2 h | first | |
| Bluesky: Site Instability | high | 8 h | first | |
| Tangled.org AT Protocol Outage | high | ongoing | not yet | |
| Bluesky: WAXCAP PDS | medium | 28 min | first | |
| Bluesky: Partial outage for some users | medium | 12 min | first |
Prisma's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Prisma v8.0.0-rc.18: Breaking Changes in Raw SQL and PSL | high | ongoing | ||
| Prisma v8.0.0-rc.24 MongoDB Date Storage Breaking Change Cause: MongoDB Date storage logic was updated to store Date as a BSON date at midnight instead of a calendar date. | medium | ongoing | ||
| Prisma Dev WAL Polling Enters Aborted Socket Transactions and Breaks Shutdown Cause: Internal WAL/Streams work queries the same PGlite instance while a client transaction is still in an aborted state following an expected SQL error, triggering error code 25P02. | medium | ongoing | ||
| Prisma 6.19.3 Rust-Free adapter-pg Exceeds MaxWait Under Pool Contention | medium | ongoing | ||
| Prisma v8.0.0-rc.23 Released with Breaking Changes for Apps and MongoDB Indexes | medium | ongoing |