Elevated rate of 5XX errors
Koyeb reports a high rate of 5XX errors in Frankfurt, Washington D.C., Tokyo, Singapore, San Francisco, and Paris. Koyeb now monitors the fix. The incident started 10 minutes ago.
State
Monitoring
Started
Ongoing for
27 min
Worst impact
Partial outage
Timeline
2 updatesIdentified
10 min 38%
Monitoring
17 min 62%
Updates
Times in UTCAs posted by Koyeb
Affected components
6Koyeb in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
6
Median duration
36 min
This incident
26% shorter than the median
Other Koyeb incidents
All incidentsKoyeb·Degraded performance
Koyeb reports degraded performance for the Third Party: Github to Webhooks component. Koyeb resolved the incident after 30 minutes.
Koyeb·Elevated rate of 500 errors in WAS
Koyeb reported an elevated rate of 500 errors in the Washington, D.C. (WAS) region. Koyeb reports that this incident is resolved. The incident lasted 80 minutes.
Koyeb·Degraded performance
Koyeb reported degraded performance for GitHub webhooks, a third-party component. Koyeb resolved the incident after 3 minutes.
Koyeb·Degraded performance
Koyeb reports degraded performance for the third party component GitHub Webhooks. Koyeb reports that the incident is resolved. The incident lasted 6 minutes.
Koyeb·Deployments failing for services using secrets with uppercase names
Deployments fail for services that use secrets with uppercase names. The API and the Build / Provisioning components are affected. Koyeb reports that this incident is resolved. The incident lasted 4 hours and 44 minutes.
Follow Koyeb
Your coding agent knows when Koyeb is down, and tells you when a failure is theirs, not yours. You can also get Koyeb 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.live/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 "koyeb" and tell me if Koyeb 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.live/feed.xml?providers=koyeb/feed subscribe https://outages.live/feed.xml?providers=koyebFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane