Travis CI
All Systems Operational
API Operational
90 days ago
100.0 % uptime
Today
Web App Operational
90 days ago
100.0 % uptime
Today
Builds Processing Operational
90 days ago
99.8 % uptime
Today
Mac Builds ? Operational
90 days ago
100.0 % uptime
Today
Linux and Windows Builds ? Operational
90 days ago
99.61 % uptime
Today
Background Processing Operational
90 days ago
100.0 % uptime
Today
Log Processing Operational
90 days ago
100.0 % uptime
Today
User Sync ? Operational
90 days ago
100.0 % uptime
Today
Notifications ? Operational
90 days ago
100.0 % uptime
Today
Third Party Services Operational
GitHub Operational
DNSimple Name Servers Operational
Heroku Operational
Pusher Pusher REST API Operational
Pusher WebSocket client API Operational
Pusher Presence channels Operational
Pusher Webhooks Operational
AWS ec2-us-east-1 Operational
PagerDuty Notification Delivery Operational
npm, Inc. Registry Reads ? Operational
Zendesk ? Operational
Google Cloud Platform Google Compute Engine Operational
GitHub API Requests Operational
GitHub Issues, PRs, Dashboard, Projects Operational
GitHub Notifications Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
API Uptime (api.travis-ci.org)
Fetching
API Uptime (api.travis-ci.com)
Fetching
Active Linux Builds for Open Source projects
Fetching
Backlog Linux Builds for Open Source projects
Fetching
Active macOS Builds for Open Source Projects
Fetching
Backlog macOS Builds for Open Source Projects
Fetching
Past Incidents
May 21, 2019

No incidents reported today.

May 20, 2019

No incidents reported.

May 19, 2019

No incidents reported.

May 18, 2019

No incidents reported.

May 17, 2019

No incidents reported.

May 16, 2019

No incidents reported.

May 15, 2019

No incidents reported.

May 14, 2019
Resolved - We have proceeded with releasing a fix earlier today and affected customers confirmed it was effective for them. We are again grateful for your understanding and please reach out to support@travis-ci.com if you run into anything else. Happy building!
May 14, 18:55 UTC
Identified - We have continued to investigate this issue. We have a fix that we are sending to affected customers to have a wider validation before deploying it to all customers. Thanks again for your patience.
May 9, 15:05 UTC
Investigating - We have received reports today about network connectivity issues when running builds from within a Docker container. We are opening this incident to give visibility about this issue and also post updates on our investigation. Thank you for your patience.
May 8, 14:59 UTC
May 13, 2019

No incidents reported.

May 12, 2019

No incidents reported.

May 11, 2019

No incidents reported.

May 10, 2019

No incidents reported.

May 7, 2019
Resolved - This incident has been resolved. We are thanking you all for hanging in there with us. Happy building!
May 7, 19:28 UTC
Monitoring - A fix has been implemented and deployed to production. We are monitoring the results.
May 7, 16:32 UTC
Identified - The issue has been identified and a fix is being implemented.
May 7, 15:17 UTC
Update - We are continuing to investigate this issue.
May 7, 14:55 UTC
Investigating - Our test cases have been failing again so we are retracting what we said in the previous update. Sorry for the inconvenience.
May 7, 03:12 UTC
Monitoring - We have proceeded with replacing affected NAT instances with new ones in production and network operations from within Docker containers seem to be back to normal. We'll be monitoring things to ensure everything is stable. We are again thanking your for your enduring patience.
May 7, 02:45 UTC
Identified - We’ve been able to reproduce and then fix this issue on our staging environment by re-creating some misbehaving NAT instances. We are devising a way to apply the same to our production environment without disruption.
May 6, 20:10 UTC
Update - Adding `--network=host` to your `docker` commands should help you get past the current issue e.g.

docker build --network=host [...]

or

docker run --network=host [...]

We are still looking at fixing the problem at the product level.

Thank you for your continued patience.
May 6, 18:01 UTC
Update - In the meantime, a workaround that's worth trying to stabilize your builds and prevent the need to restart them manually, is to add `travis_retry` to your failing commands e.g.

travis_retry docker build [...]

This will effectively re-run your command up to 3 times if it fails.
May 6, 15:19 UTC
Investigating - We have received reports since last Friday about slow or stalling downloads when done from within a Docker container. We are opening this incident to give visibility about this issue and also post updates on our investigation. Thank you for your patience.
May 6, 14:28 UTC