Travis CI
All Systems Operational
API Operational
Web App Operational
Builds Processing Operational
Mac Builds ? Operational
Linux Builds (container-based) ? Operational
Linux Builds (Trusty and Precise on GCE) ? Operational
Background Processing Operational
Log Processing Operational
User Sync ? Operational
Notifications ? Operational
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
Help Scout Email Processing Operational
Help Scout Web App Operational
PagerDuty Notification Delivery Operational
Google Cloud Platform Google Compute Engine Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
API Uptime (api.travis-ci.org)
Fetching
API Uptime (api.travis-ci.com)
Fetching
Active Linux Builds for Open Source projects (container-based)
Fetching
Backlog Linux Builds for Open Source projects (container-based)
Fetching
Active Linux Builds for Open Source projects
Fetching
Backlog Linux Builds for Open Source projects
Fetching
Active OS X Builds for Open Source Projects
Fetching
Backlog OS X Builds for Open Source Projects
Fetching
Past Incidents
May 22, 2017

No incidents reported today.

May 21, 2017
Completed - The network maintenance is complete. Thank you for your patience, and happy building!
May 21, 20:51 UTC
Verifying - The infrastructure provider has installed the HA pair, and we are checking to make sure that everything is still working as intended.
May 21, 20:37 UTC
In progress - macOS builds have been halted in preparation for network maintenance. We are now waiting on our infrastructure provider to install the HA router pair.
May 21, 20:12 UTC
Update - macOS builds will be halted shortly in preparation for the network maintenance on the macOS build infrastructure.
May 21, 20:03 UTC
Scheduled - Job processing on the macOS will be stopped for a time in order for us to install a high-availability router pair in place of our single router. This will allow us to provide more stability going forward.
May 16, 01:32 UTC
May 20, 2017

No incidents reported.

May 19, 2017

No incidents reported.

May 18, 2017
Resolved - Jobs and logs are processing normally.
May 18, 20:55 UTC
Monitoring - We are happy to report that there's no backlog on our sudo-enabled infrastructure (i.e. GCE) at this time. There are still backlogs on our container-based and Mac infrastructures.
May 18, 20:17 UTC
Update - We are restarting to process builds and are seeing the backlog going down. We are monitoring to see that everything is back to normal. Thank you!
May 18, 20:04 UTC
Identified - We've identified that a network issue of some kind interrupted connections to our RabbitMQ cluster and we're in the process of restarting backend services that have been left in an error state due to the interruption. We'll provide another update as we confirm we're processing builds properly again.
May 18, 19:45 UTC
Investigating - We are seeing reports of builds not starting for private repositories. We are currently looking into it. Thank you for your patience!
May 18, 19:11 UTC
May 17, 2017

No incidents reported.

May 16, 2017

No incidents reported.

May 15, 2017

No incidents reported.

May 14, 2017

No incidents reported.

May 13, 2017

No incidents reported.

May 12, 2017

No incidents reported.

May 11, 2017

No incidents reported.

May 10, 2017

No incidents reported.

May 9, 2017

No incidents reported.

May 8, 2017
Resolved - This incident has been resolved.
May 8, 22:24 UTC
Update - Backlogs are clear on all Linux queues. We are still working through a backlog for Mac jobs.
May 8, 21:17 UTC
Update - Backlogs are clear on all container-based Linux queues. We have brought additional capacity online for sudo-enabled Linux. Backlogs remain on:

- Mac
- sudo-enabled Precise and Trusty
May 8, 20:40 UTC
Monitoring - All infrastructure are now processing builds. The container-based infrastructure running Precise doesn't have a backlog right now. A backlog remains, however, for the following infrastructures:

- Mac
- container-based infrastructure (Trusty)
- sudo-enabled Precise and Trusty

We will give another update on the state of the backlog for these infrastructures soon.
May 8, 19:59 UTC
Update - Our RabbitMQ cluster has been restored. We are now restarting our workers to start processing builds again.
May 8, 19:36 UTC
Update - We are currently working with our RabbitMQ provider to help us get our cluster back up. We are sorry for the continued troubles.
May 8, 19:14 UTC
Update - We are still having issues with the connectivity between our components. We need to proceed to an emergency maintenance of our RabbitMQ cluster to be able to fix this issue. We thank you again for your patience.
May 8, 18:33 UTC
Update - We are still working on bringing back our build infrastructures and build logs are still unavailable. We have proceeded to restart one of our components and are currently assessing the resulting situation. We are sorry for the continued troubles.
May 8, 17:44 UTC
Update - Full build processing capacity has been restored on our Mac infrastructure. Other infrastructures should be back on their feet shortly. Thanks for hanging in there.
May 8, 16:34 UTC
Investigating - We are currently seeing at backlog of private builds on travis-ci.com. Hence, you might see delays before your builds start. Our Engineering Team is currently looking into it. We'll update this incident when we know more. Thank you for your enduring patience.
May 8, 16:19 UTC
Resolved - Logs should now be displaying properly. Please reach out at support [at] travis-ci [dot] com if it's not the case. Thank you! 💛
May 8, 16:17 UTC
Monitoring - We've been able to put back the display of build logs back on its feet. We are monitoring things to see if everything is working correctly now.
May 8, 16:05 UTC
Investigating - We are currently seeing reports of build logs being unavailable for private builds on travis-ci.com. Our Engineering Team is currently looking into it. We will update this incident as soon as we know more. Thank you for your patience!
May 8, 15:37 UTC