GitHub incident is causing elevated error rate for environments
We're no longer seeing degradation when interacting with GitHub.
The latest update from Ona.
State
Resolved
Started
Lasted
2 h 46 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
1 h 36%
Monitoring
1 h 45 min 64%
Updates
Times in UTCAs posted by Ona
We're no longer seeing degradation when interacting with GitHub.
GitHub has indicated the issue has been resolved, we're seeing improvements to the error rate and continue to observe.
GitHub continues to be affected with many of their services degraded - [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx "https://www.githubstatus.com/incidents/zkxwbgr0cnmx"). Ona environments and agent sessions using GitHub are impacted.
GitHub originated incident is resulting in environments being unable to checkout content, webhooks for automations are not being delivered.
Ona in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
2 h 46 min
This incident
About the median
Follow Ona
Your coding agent knows when Ona is down, and tells you when a failure is theirs, not yours. You can also get Ona 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 "ona" and tell me if Ona 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=ona/feed subscribe https://outages.live/feed.xml?providers=onaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane