Partially Degraded Service
ResolvedOfficial update
0
Travis CI had a partially degraded service that affected the GitHub component. Travis CI reports that the incident is resolved. The outage lasted 99 minutes.
State
Resolved
Started
Lasted
1 h 39 min
Worst impact
Degraded
Timeline
2 updates21:0021:2421:4922:1422:39
DegradedUpdate postedTimes in UTC
Components degraded
1 h 39 min 100%
Updates
Times in UTCAs posted by Travis CI
Resolved
Components degraded
Affected components
1GitHub
Travis CI in the last 90 days
Full history90 days agoToday
Incidents in 90 days
1
Days with an incident
1
Median duration
1 h 39 min
This incident
About the median
Follow Travis CI
Your coding agent knows when Travis CI is down, and tells you when a failure is theirs, not yours. You can also get Travis CI 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 "travisci" and tell me if Travis CI 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=travisciSlack
/feed subscribe https://outages.cc/feed.xml?providers=travisciFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane