outages.live
Live

Travis CI

Travis CI is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

22

Background Processing

Log Processing Operational
90 days agoNo incidentsToday
User Sync Operational
90 days agoNo incidentsToday
Notifications Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Web App Operational
90 days agoNo incidentsToday
Google Cloud Platform Google Compute Engine Operational
90 days agoNo incidentsToday
GitHub API Requests Operational
90 days agoNo incidentsToday
GitHub Issues, PRs, Dashboard, Projects Operational
90 days agoNo incidentsToday
Assembla API and Merge Requests Operational
90 days agoNo incidentsToday
GitLab API and Pull Requests Operational
90 days agoNo incidentsToday

Third Party Services

GitHub Operational
90 days agoNo incidentsToday
DNSimple Name Servers Operational
90 days agoNo incidentsToday
Pusher Pusher REST API Operational
90 days agoNo incidentsToday
Pusher WebSocket client API Operational
90 days agoNo incidentsToday
Pusher Presence channels Operational
90 days agoNo incidentsToday
Pusher Webhooks Operational
90 days agoNo incidentsToday
AWS ec2-us-east-1 Operational
90 days agoNo incidentsToday
PagerDuty Notification Delivery Operational
90 days agoNo incidentsToday
npm, Inc. Registry Reads Operational
90 days agoNo incidentsToday
Assembla Operational
90 days agoNo incidentsToday

Builds Processing

Linux and Windows Builds Operational
90 days agoNo incidentsToday
IBM Z Builds Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

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=travisci
Slack
/feed subscribe https://outages.cc/feed.xml?providers=travisci

Go from tracking outages to fixing production issues with Polylane.

Try Polylane