Major outage
ResolvedOfficial update
0
The Helicone EU API had a major outage. Helicone reports that the incident is resolved. The outage lasted 3 minutes.
State
Resolved
Started
Lasted
3 min
Worst impact
Major outage
Timeline
2 updates09:0909:0909:1009:1109:12
Major outageUpdate postedTimes in UTC
Components degraded
3 min 100%
Updates
Times in UTCAs posted by Helicone
Resolved
Components degraded
Affected components
1EU API
Helicone in the last 90 days
Full history90 days agoToday
Incidents in 90 days
1
Days with an incident
1
Median duration
3 min
This incident
About the median
Follow Helicone
Your coding agent knows when Helicone is down, and tells you when a failure is theirs, not yours. You can also get Helicone 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 "helicone" and tell me if Helicone 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=heliconeSlack
/feed subscribe https://outages.cc/feed.xml?providers=heliconeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane