outages.live
Live
PrismaIncident · 2026-08-03 10:01 UTC

Accelerate is slow to provision new query engines in eu-west-3

ResolvedOfficial update

This incident has been resolved.

The latest update from Prisma.

State

Resolved

Started

90 d ago

2026-08-03 10:01 UTC

Lasted

47 min

until 2026-08-03 10:47 UTC

Worst impact

Degraded

Timeline

2 updates
10:0110:1210:2410:3610:47
DegradedUpdate postedTimes in UTC

Monitoring

47 min 100%

Updates

Times in UTC

As posted by Prisma

Resolved2026-08-03 10:47 UTC

This incident has been resolved.

Monitoring2026-08-03 10:01 UTC

We have identified an upstream infrastructure provider issue affecting the eu-west-3 region. Accelerate is experiencing issues provisioning resources for new query engine instances. Affected users: Users provisioning new Accelerate query engines in the eu-west-3 region. Root cause: AWS EC2 instance capacity saturation Workarounds: None identified

Affected components

1
Prisma Accelerate

Prisma in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

3

Median duration

1 h 45 min

This incident

55% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 54 min
median 1 h 45 min
90 days agoToday

Other Prisma incidents

All incidents

Prisma·Intermittent Connection Errors on Prisma Postgres

We are continuing to observe healthy traffic to Prisma Postgres across all regions. This incident has been resolved.

Resolvedresolved 16 d ago

Prisma·Degraded performance on Prisma Postgres for some users in US East.

This incident has been resolved.

Resolvedresolved 40 d ago

Prisma·Accelerate is unable to provision new query engines in eu-west-3

This incident has been resolved.

Resolvedresolved 61 d ago

Follow Prisma

Your coding agent knows when Prisma is down, and tells you when a failure is theirs, not yours. You can also get Prisma incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "prisma" and tell me if Prisma has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=prisma
Slack
/feed subscribe https://outages.cc/feed.xml?providers=prisma

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane