Travis CI

Affected: Log Processing, Notifications, Linux and Windows Builds, IBM Z Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-25 14:12 UTC

   We are currently investigating reports of build jobs failing.

2. identified 2026-05-25 14:17 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-25 18:21 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-25 19:26 UTC

   The fix has been successful, and all systems are now operating normally. We will continue to monitor performance closely. Thank you for your patience and understanding as we addressed this issue. If you continue to experience any residual issues or have further questions, please...

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-20 18:44 UTC

   Trials are currently unavailable. The issue has been identified, and we are preparing a fix. In the meantime, please reach out to support@travis-ci.com if you have any questions.

2. resolved 2025-01-28 18:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-04 14:54 UTC

   We are investigating an issue that is preventing arm64 jobs from running correctly.

2. resolved 2024-09-04 19:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: A code release introduced the failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-08-29 14:07 UTC

   We have released DPLv2 as stable gem on Aug-28th into Travis gem collection. There's an issue for DPLv2 users and there's available workaround. The 'uri' gem updated 2 days ago caused DPLv2 2.0.5 not work correctly in Travis CI build environments due to dependency chain. This...

2. identified 2024-08-30 13:26 UTC

   We have reverted DPLv2 gem from being latest stable in gem repository, 1.10.16 is now latest stable. This doesn't affect TCI Hosted users. This should prevent TCI Enterprise server environments not updated to TCIE v3.1 suffer from necessity to update individual .travis.yml...

3. identified 2024-09-03 11:54 UTC

   Updating build environment images still in progress - additional dependencies were identified and are worked on. Until build environment updates are finished, DPLv1 works normally, DPLv2 users are recommended to continue using uri gem update workaround. TCI Enterprise server...

4. identified 2024-09-05 10:24 UTC

   TCI Enterprise server version 3.0.58 patch published and recommended to be used no later than by Sep-14th, 2024.

5. monitoring 2024-09-11 10:45 UTC

   Updates in DPLv2 and Travis CI build environments applied. We are monitoring. DPLv2 may be promoted to be default DPL function after Sep 14th.

6. resolved 2024-09-23 08:42 UTC

   Build images updates and DPLv2 updates will drop continuously. DPLv2 will be promoted as default DPL gem version at Sep-30th.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds, IBM Z Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-28 22:31 UTC

   We are currently investigating an issue that is preventing some builds from working properly.

2. resolved 2024-08-29 02:00 UTC

   This issue has been resolved and now builds are running as expected.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-23 13:58 UTC

   We have identified an issue that is preventing s390x and ppc64le jobs from running correctly. We’re actively working to address this problem.

2. identified 2024-08-24 00:42 UTC

   Bionic and Focal builds should work now, fix deployed.

3. resolved 2024-08-29 14:23 UTC

   This incident has been resolved for Bionic and Focal builds. We're working on Jammy builds that should be fixed soon, updates will be posted to our changelog page.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-17 08:07 UTC

   We have observed some issues with our Mac build process. Our team is investigating these issues and we will be providing further updates as more information becomes available

2. identified 2024-01-17 08:24 UTC

   The issue has been identified and a fix is being implemented

3. monitoring 2024-01-17 08:24 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-01-17 11:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: GitHub Issues, PRs, Dashboard, Projects

Failure mode: A configuration change caused the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2023-11-16 10:30 UTC

   Issues with branch/tag based builds reported since Nov-9 have been confirmed to be on Travis CI side. We have identified the reason and confirmed it's due to GitHub push event handling on Travis CI side. Working on the fix. Build infrastructure is fully operational

2. monitoring 2023-11-16 13:41 UTC

   A fix for handling GitHub push events was implemented and we are monitoring the system now.

3. resolved 2023-11-16 16:56 UTC

   Incident resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: User Sync

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2023-11-03 12:29 UTC

   We received information on issues with data synchronization with GitHub since Nov/1st. We have identified reason and are working on restoring system to normal operation.

2. monitoring 2023-11-03 15:10 UTC

   A fix is in place and we're monitoring.

3. resolved 2023-11-03 15:46 UTC

   Data synchronization issues with GitHub have been fully resolved and all systems are operational

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: API, Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2023-10-28 12:15 UTC

   Travis API errors discovered. Builds may be breaking.

2. monitoring 2023-10-28 13:00 UTC

   Issue found and fixed. Monitoring system.

3. resolved 2023-10-28 13:32 UTC

   Operation back to normal.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: GitHub, Linux and Windows Builds

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2023-03-24 10:12 UTC

   Users utilizing Custom SSH Key in Travis CI private repository settings may experience build errors or warnings on git checkout. This is due main SSH keys being updated by GitHub (see https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/ ). We are working on updating...

2. monitoring 2023-03-24 12:47 UTC

   We have deployed hotfix replacing main Github host RSA SSH keys and are monitoring the builds. Users with Custom SSH Key in Travis CI repository settings should be able to build correctly now.

3. resolved 2023-03-24 17:05 UTC

   The issue seems resolved. If you encounter further roadbloacks in repositories using Custom SSH Key in Travis CI, specifically on git repository cloning stage, please validate if a matching key pair is still available at GitHub. If not, removing old Custom SSH Key in Travis CI...

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: User Sync

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2022-12-20 11:30 UTC

   We are currently investigating the issue. The symptoms are that either adding new repository or installing Travis CI GitHub App from scratch results in repositories not being activated and builds cannot be triggered.

2. identified 2022-12-20 11:41 UTC

   The issue has been identified, fix is being implemented. Adding/activating new repos will not work for now.

3. monitoring 2022-12-20 12:11 UTC

   We're draining the pending messages to GitHub API queue. It may take some time before all affected accounts are enabled again.

4. monitoring 2022-12-20 14:13 UTC

   User synchronization operational. The queue drain was finished at GMT 13:00. We will be monitoring the situation over next hours, looking for any remaining issues caused by the incident. You may need to reinstall Travis CI GitHub App if you added a new repository or created a...

5. resolved 2022-12-20 15:44 UTC

   This incident has been resolved. You may need to reinstall Travis CI GitHub App if you added a new repository or created a new account between 19 December 2022 12:06:34 and 20 December 2022 GMT 13:00:00.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2022-05-17 03:00 UTC

   Some of the build requests they both triggered with API and Git push operations are not being processed. We are still investigating the root cause behind this issue.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2022-03-01 12:08 UTC

   We have identified the issue where some of the builds are not being triggered and got an undetailed error when they are triggered.

2. monitoring 2022-03-01 12:48 UTC

   We have implemented the fix and monitoring the issue.

3. resolved 2022-03-01 13:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2021-10-20 13:57 UTC

   The issue has been identified and a fix is being implemented.

2. identified 2021-10-20 16:46 UTC

   Summary: Users on Old Travis CI pricing model: We have identified that the Users/Orgs on old Travis CI pricing model are unable to trigger builds. Description: Users are not able to trigger builds on Travis CI Platform with a message "We are unable to start your build at this...

3. monitoring 2021-10-20 17:24 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2021-10-20 19:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2021-09-06 13:38 UTC

   The main page at https://travis-ci.com is down. Your builds are still executed. We're reviewing the main site case, it may remain inactive for a full day or so. The API and https://app.travis-ci.com can be still accessed directly and you can run, view, and manage your builds as...

2. resolved 2021-09-06 15:04 UTC

   The main site https://travis-ci.com/ is back on field.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: API, Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2021-08-11 13:33 UTC

   Sorry, some users are unable to trigger builds on GitHub commits. We are working on it and hope to restore the functionality shortly. Sorry for the inconvenience!

2. monitoring 2021-08-11 13:38 UTC

   Our Infra team has implemented a fix that should resolve this issue. Thank you for your patience and cooperation!

3. resolved 2021-08-11 13:54 UTC

   This incident has been resolved. If you face any issues with builds on Travis Platform, you can reach our support staff at support@travis-ci.com

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds, GitHub API Requests, GitHub Issues, PRs, Dashboard, Projects

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2021-07-13 16:41 UTC

   Sorry, some users are unable to trigger builds on GitHub commits. We are working on it and hope to restore the functionality shortly. Sorry for the inconvenience!

2. monitoring 2021-07-13 17:01 UTC

   Our Infra team has implemented a fix that should resolve this issue. Thank you for your patience and cooperation!

3. resolved 2021-07-13 19:45 UTC

   This incident has been resolved. If you face any issues with builds on Travis Platform, you can reach our support staff at support@travis-ci.com

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-06-25 07:57 UTC

   Some build requests are being rejected and this causes builds to be triggered. We are currently investigating the issue.

2. investigating 2021-06-25 07:58 UTC

   We are continuing to investigate this issue.

3. identified 2021-06-25 08:25 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2021-06-25 08:32 UTC

   The fix has been implemented and build requests are being processed as usual. We are still monitoring the system

5. resolved 2021-06-25 08:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-06-21 15:05 UTC

   Some builds may have trouble on the queued stage. We are currently investigating the issue.

2. identified 2021-06-21 15:11 UTC

   We have identified the problem and a fix is in process.

3. identified 2021-06-21 16:24 UTC

   We are continuing to work on a fix for this issue.

4. identified 2021-06-21 18:26 UTC

   We are actively fixing this issue and will report back as soon this resolves. We are very sorry for the inconvenience in the meantime.

5. resolved 2021-06-22 08:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2021-06-11 14:53 UTC

   Some builds may have trouble on the queued stage, we are currently investigating the issue.

2. identified 2021-06-11 15:31 UTC

   We have identified the problem and queued jobs are already started processing.

3. resolved 2021-06-11 15:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2021-06-01 18:22 UTC

   We observed some ppc64 jobs are taking longer to start. In addition, we've noticed an increased error rate. We are working to resolve these and will provide updates shortly.

2. resolved 2021-06-01 21:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2021-03-30 17:34 UTC

   Builds are currently queued for longer than normal. We are investigating this issue and will provide an update shortly.

2. monitoring 2021-03-30 18:30 UTC

   Our queue is currently draining fast and processing of builds should be back to normal

3. resolved 2021-03-30 19:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds, Google Cloud Platform Google Compute Engine

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2021-03-17 17:45 UTC

   Due to the ongoing incident with Google's Compute Engine [1], some jobs may fail to run. We are monitoring the Google Status and will provide updates. Thank you [1] https://status.cloud.google.com/incident/cloud-networking/21006#21006002

2. resolved 2021-03-17 19:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2020-09-24 09:12 UTC

   We are investigating the root cause behind why builds are not triggered for travis-ci.com

2. identified 2020-09-24 09:41 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2020-09-24 09:41 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2020-09-24 10:14 UTC

   This incident has been resolved.

5. postmortem 2020-10-01 13:18 UTC

   We are extremely sorry about the outage on this incident and we would like to share some action that has been taken; * Issue reported date: The issue has been reported on 24.09.2020 09:12 UTC. * Issue: **Unstable VCS service, high memory usage** * Reason: Issue in Bitbucket...

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-08-12 19:25 UTC

   We are investigating reports of builds not being processed on .org.

2. monitoring 2020-08-12 19:40 UTC

   The issue has been resolved and we are monitoring the system.

3. resolved 2020-08-12 19:46 UTC

   Builds are being processed normally.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Notifications

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2020-04-29 20:56 UTC

   We have identified issues with infrastructure handling notifications, which leads to these not been fired. A fix is being worked on.

2. monitoring 2020-04-29 21:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2020-04-29 21:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2020-04-28 22:07 UTC

   We are currently investigating a large number of queued jobs on our .ORG infrastructure for MacOS builds

2. monitoring 2020-04-28 22:25 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2020-04-28 22:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-04-27 20:45 UTC

   We are currently investigating an uptick in queued jobs on our .COM platform

2. identified 2020-04-27 20:46 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2020-04-27 21:32 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2020-04-27 22:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2020-04-24 12:46 UTC

   We are investigating reports of intermittent failures on API.

2. identified 2020-04-24 13:12 UTC

   We have identified the cause and are working on a fix.

3. identified 2020-04-24 14:20 UTC

   We have deployed the fixes and monitoring their effectiveness.

4. monitoring 2020-04-24 14:39 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2020-04-24 15:07 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: GitHub, User Sync, Notifications, Linux and Windows Builds, GitHub API Requests, GitHub Issues, PRs, Dashboard, Projects

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2020-04-21 16:11 UTC

   Our services are degraded due to GitHub's ongoing issues.

2. resolved 2020-04-21 16:52 UTC

   The service are operating normally.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2020-04-14 07:10 UTC

   You may experience issues with macOS builds due to an issue with our infrastructure service provider. We are closely looking into this issue and more to come!

2. identified 2020-04-14 07:12 UTC

   Investigation underway we are in close contact with the service provider.

3. resolved 2020-04-14 09:45 UTC

   The issue related to macOS builds has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds, Google Cloud Platform Google Compute Engine

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2020-04-08 14:57 UTC

   Our service provider is experiencing issues, and at the moment we are unable to boot VMs to run the builds on Linux and Windows.

2. resolved 2020-04-08 15:32 UTC

   The service provider issue has been resolved. The builds should be processed normally.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2020-03-27 20:14 UTC

   We are investigating an outage on the .ORG API. We will provide updates based on our findings. Thank you

2. monitoring 2020-03-27 20:26 UTC

   We implemented a fix for the issue and are monitoring the results. Thank you

3. monitoring 2020-03-27 20:57 UTC

   We are continuing to monitor our infrastructure and one of our upstream providers, Google [1]. We will provide additional updates once these systems are fully functional. Thank you [1] https://status.cloud.google.com/incident/cloud-networking/20004

4. resolved 2020-03-27 21:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2020-03-25 19:21 UTC

   We are investigating the reports of GitHub commit status not being posted. The issue only affects those repositories using the legacy Services integration (i.e., all .org repositories and some .com ones), and only under some circumstances. You can migrate your repositories to...

2. identified 2020-03-26 13:32 UTC

   We have identified the source of these errors and are working on a fix.

3. monitoring 2020-03-26 16:38 UTC

   We've deployed additional measures to mitigate this issue and are monitoring the effects. We will roll out additional fixes as required. Thanks for your patience

4. resolved 2020-03-26 19:37 UTC

   The issue has been resolved. Please write to support@travis-ci.com if you encounter any similar problems. Thank you

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: API, GitHub, Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2020-03-24 13:41 UTC

   The issue related to queued builds and build statuses is still partially down. We have investigated the issue and currently working on the components to up again.

2. resolved 2020-03-24 15:00 UTC

   Thank you for your patience and understanding. This incident has been resolved by taking another look and tests about builds statuses and build trigger mechanism. The solution was deployed at 14:00 PM UTC.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2020-03-24 10:42 UTC

   We have observed the root cause of the problem with the builds isn't starting due to misusage. Currently, we are recovering the infrastructure.

2. resolved 2020-03-24 12:34 UTC

   Thank you for your patience. The incident has been resolved and builds should behave as normal.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2020-03-23 19:31 UTC

   We observed an issue with a small portion of macOS builds, jobs routed to a particular infrastructure unit took longer than expected to start or failed. The issue was resolved at 18h31 UTC

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2020-03-22 16:23 UTC

   We have identified an issue with a portion of Mac infrastructure which prevents builds from running correctly. We are working on mitigating the impact of this problem. Affected jobs would indicate "An error occurred while generating the build script." in the logs.

2. monitoring 2020-03-22 16:42 UTC

   We have removed the affected hardware out of the executor pool. Requests should work as expected at this time.

3. resolved 2020-03-22 17:12 UTC

   The Mac build capacity has been brought back to normal.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2020-03-19 19:41 UTC

   We have observed issues with Mac OSX builds that are failing on both .com and .org due to a major outage at our upstream provider. We are looking into this and will provide additional updates.

2. resolved 2020-03-19 21:59 UTC

   Thank you for your patience. Our upstream provider has reported that a fix has been implemented [1]. We have also seen improvements on our end and so we are marking this issue resolved. Thank you [1] https://status.macstadium.com/incidents/l464rrkdg4yn

3. postmortem 2020-03-23 16:26 UTC

   Please see the MacStadium Post-Mortem \[1\] for details about this incident. Thank you! \[1\] [https://status.macstadium.com/incidents/l464rrkdg4yn](https://status.macstadium.com/incidents/l464rrkdg4yn)

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2020-02-04 20:07 UTC

   We have confirmed that a portion of jobs requested today were not processed correctly. These jobs are stuck in the "queued" state. We confirmed that restarting affected jobs solves the issue.

2. monitoring 2020-02-04 20:11 UTC

   We are restarting the jobs stuck in "queued" state at this time. Affected users may restart them themselves. If you continue to see problems, please contact us at support@travis-ci.com.

3. monitoring 2020-02-04 21:57 UTC

   We are planning on restarting stuck jobs between 20:40 and 21:40 UTC and monitor the queue following the restart.

4. resolved 2020-02-04 22:36 UTC

   Jobs have been processed. If you see problems, please contact us at support@travis-ci.com.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2020-01-30 14:46 UTC

   We are investigating reports of Linux jobs not being processed for .com (both private and public).

2. identified 2020-01-30 15:25 UTC

   We have confirmed that a portion of jobs requested starting around 07:00 UTC today were not processed correctly. These jobs are stuck in the "queued" state. We confirmed that restarting affected jobs solves the issue.

3. monitoring 2020-01-30 15:48 UTC

   We are restarting the jobs stuck in "queued" state at this time. Affected users may restart them themselves. If you continue to see problems, please contact us at support@travis-ci.com.

4. resolved 2020-01-30 16:34 UTC

   Jobs have been processed. If you see problems, please contact us at support@travis-ci.com.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2019-11-19 08:13 UTC

   We are investigating an issue with IBM Z builds.

2. monitoring 2019-11-19 14:50 UTC

   We are seeing builds on IBM Z starting normally. A fix for both .com and .org has been implemented and we are monitoring the results.

3. resolved 2019-11-19 19:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2019-08-08 07:29 UTC

   We have received several reports of builds failing due to an unsuccessful TLS handshake to *whereami.travis-ci.com:443* on one of our production servers. We are opening this incident to acknowledge the issue and also keep you posted on our work to solve it. Thank you for your...

2. investigating 2019-08-08 07:41 UTC

   We are continuing to investigate this issue.

3. identified 2019-08-08 07:50 UTC

   We have identified the production systems affected by this issue and have removed these from the pool. No new builds will be affected by this, existing builds in the pool will be allowed to finish but might have network connectivity issues. Please expect additional updates...

4. monitoring 2019-08-08 10:52 UTC

   Builds that were running on the affected pool have now finished and all builds are back to normal. We're monitoring closely and will post again once we're in the clear.

5. monitoring 2019-08-08 13:45 UTC

   Builds are back to running normally. We will continue to monitor the situation for a short while before closing the incident.

6. resolved 2019-08-08 14:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2019-08-06 17:55 UTC

   We are receiving reports of Linux and Windows builds where network connectivity is unreliable, intermittently working or slow. We are opening this incident to acknowledge the issue and also keep you posted on our work to solve it. Thank you for your patience.

2. investigating 2019-08-06 17:55 UTC

   We are continuing to investigate this issue.

3. identified 2019-08-07 07:54 UTC

   We've identified an issue with the latest changes to update the NAT gateways. While this change was meant to improve maintainability, we are rolling it back due to the degraded network performance. We're expecting this provides network speed improvements within the next hour. We...

4. identified 2019-08-07 10:37 UTC

   At this point, we've reverted half of the NAT gateway updates and a 50% of the Linux and Windows jobs currently processed have better network performance already. We'll provide another update as soon as this process is complete. Thanks for your patience.

5. monitoring 2019-08-07 12:38 UTC

   The NAT gateway changes have been fully reverted. Network performance and reliability in your builds should be back to normal. We’ll be monitoring for a short while before closing this incident.

6. resolved 2019-08-07 14:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2019-07-25 13:07 UTC

   We are seeing a backlog of Linux and Windows builds on both travis-ci.org and travis-ci.com. We are adding capacity as we speak and we’ll keep you posted on the results. Thank you for your patience.

2. resolved 2019-07-25 13:34 UTC

   Backlogs have cleared on both sites hence we are resolving this incident.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2019-07-24 15:33 UTC

   We are seeing a backlog of - macOS builds on travis-ci.com - Linux and Windows builds on travis-ci.org We are looking into adding back capacity to process them.

2. investigating 2019-07-24 15:48 UTC

   macOS builds backlog on travis-ci.com has cleared. We are almost done processing the Linux and Windows backlog on travis-ci.org. Thank you for your patience!

3. resolved 2019-07-24 15:59 UTC

   All backlogs have cleared now. Sorry again for the inconvenience and happy building!

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. identified 2019-07-08 21:26 UTC

   We have received reports of delayed posting of Github Statuses. We are working to clear the backlog of such that should have been sent out.

2. identified 2019-07-08 21:44 UTC

   We have cleared the back logs, and most status have now been posted. If your GitHub Apps is not posting statuses, please try disabling and re-enabling the repository, and restarting (parts of) the affected builds.

3. monitoring 2019-07-08 21:49 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2019-07-08 22:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2019-07-03 14:15 UTC

   We are seeing backlogs of jobs growing on both travis-ci.org and travis-ci.com stemming from yesterday’s incident. We’ve been able to add more resources but not to the extent to be able to handle all build requests we receive during peak hours. Hence, your builds might be...

2. monitoring 2019-07-03 18:26 UTC

   We’ve added more capacity and have been able to process the accumulated backlogs on both .com and .org. We will monitor the situation for a short while to ensure everything is stable.

3. resolved 2019-07-03 20:02 UTC

   Builds are running smoothly and we have significant remaining headroom. Please send your commits our way! We are closing this incident for now and are thanking you again for you enduring patience.

Excerpts are shortened. Read the full incident on Travis CI's status page.

Affected: Linux and Windows Builds

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2019-07-02 15:16 UTC

   We are receiving reports of slow booting Linux builds. We are currently looking into it.

2. investigating 2019-07-02 16:25 UTC

   We are currently hitting the API rate-limit when using our Cloud Provider’s API that is preventing us from creating/deleting VMs. We are looking into getting the system back under the API rate-limit threshold. Thank you for your patience.

3. identified 2019-07-02 17:22 UTC

   We’ve made progress in being able to stay under the API rate-limit and things are looking better on travis-ci.com. A higher backlog of jobs remains on travis-ci.org. We’ll keep you posted on the status of each backlog on a timely basis.

4. identified 2019-07-02 21:07 UTC

   Sorry for the lack of updates. It's been challenging to remain below the API rate-limit and the backlogs haven't been decreasing at a steady pace as previously mentioned. We now confirm that the backlog on .com is decreasing at a comfortable pace while the backlog on .org is...

5. monitoring 2019-07-02 22:21 UTC

   Backlog on travis-ci.com has cleared around 21:55 UTC. We are monitoring travis-ci.org's backlog closely.

6. resolved 2019-07-03 02:45 UTC

   Backlog on travis-ci.org has cleared has of 2019-07-03 2:14 UTC. Thanks again for your continued patience during this incident.

Excerpts are shortened. Read the full incident on Travis CI's status page.