Optimization Agent shows elevated error rate
Contentful reports that the Optimization Agent showed an elevated error rate. Contentful says the incident is resolved and the service runs normally again. The incident lasted 12 minutes.
State
Resolved
Started
1 h ago
2026-11-02 15:18 UTC
Lasted
12 min
until 2026-11-02 15:31 UTC
Worst impact
Notice
Timeline
2 updatesInvestigating
12 min 100%
Updates
Times in UTCAs posted by Contentful
A recent change led to a degraded Optimization Agent experience, this is now resolved and everything is running normally again.
Our monitoring systems have detected an outage of [COMPONENT] we're investigating the nature and the cause of the outage and we'll update this incident as we have more details
Follow Contentful
Your coding agent knows when Contentful is down, and tells you when a failure is theirs, not yours. You can also get Contentful 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 "contentful" and tell me if Contentful 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=contentful/feed subscribe https://outages.cc/feed.xml?providers=contentfulFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane