Prisma

First posted only after it was over

4% 2 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Prisma: around the middle.

Time to resolve

2 h 15 min median; 9 in 10 within 9 h 40 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Prisma: around the middle.

Major or critical incidents

0.7 a month 8 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Prisma: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Prisma depends on

Runs in (named in its incidents): AWS eu-central-1 (10), AWS us-east-1 (9), AWS ap-northeast-2 (1), AWS ap-south-1 (1).

Outage events: Cloudflare, Dec 5, 2025, Cloudflare, Nov 18, 2025 (timing), AWS us-east-1, Oct 20, 2025, Google Cloud, Jun 12, 2025 (timing), AWS, Jun 13, 2023 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full Prisma change history

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Prisma incidents, last 90 daysJSONMarkdown