Accelerate is unable to provision new query engines in eu-west-3
This incident has been resolved.
The latest update from Prisma.
State
Resolved
Started
61 d ago
2026-09-01 06:52 UTC
Lasted
2 h 24 min
until 2026-09-01 09:16 UTC
Worst impact
Partial outage
Timeline
5 updatesIdentified
1 h 48 min 75%
Monitoring
36 min 25%
Updates
Times in UTCAs posted by Prisma
This incident has been resolved.
The capacity problems have subsided. We are monitoring the situation.
Description: We have identified an upstream infrastructure provider capacity issue affecting the eu-west-3 region. Accelerate is experiencing intermittent issues provisioning resources for new query engine instances in this region. No other regions are impacted. Affected users: Users provisioning new Accelerate query engines in the eu-west-3 region. Root cause: Upstream infrastructure provider capacity Workarounds: None identified
The capacity problems have subsided. We are monitoring the situation.
Description: We have identified an upstream infrastructure provider capacity issue affecting the eu-west-3 region. Accelerate is experiencing intermittent issues provisioning resources for new query engine instances in this region. No other regions are impacted. Affected users: Users provisioning new Accelerate query engines in the eu-west-3 region. Root cause: Upstream infrastructure provider capacity Workarounds: None identified
Affected components
1Prisma in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
2 h 24 min
This incident
About the median
Other Prisma incidents
All incidentsPrisma·Intermittent Connection Errors on Prisma Postgres
We are continuing to observe healthy traffic to Prisma Postgres across all regions. This incident has been resolved.
Prisma·Degraded performance on Prisma Postgres for some users in US East.
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=prisma/feed subscribe https://outages.cc/feed.xml?providers=prismaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane