Travis CI Outage History

Travis CI partial outage View live status →

Pingoru has recorded 57 incidents for Travis CI: 1 in the last 12 months and 0 in the last 90 days.

Source: traviscistatus.com

57incidents recorded
1last 12 months
0last 90 days
5 hourstypical duration
Incidents per month
012MayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%MayJunJulAugSepOct0%
Pingoru began tracking Travis CI in May 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
May 202615 of 744 (1%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Minor May 25, 2026 Build job(s) failures 5h 13m Log Processing, Notifications, Linux and Windows Builds, IBM Z Builds

Started May 25, 2026, 02:12 PM UTC· resolved May 25, 2026, 07:26 PM UTC

  1. investigating May 25, 2026, 02:12 PM UTC

    We are currently investigating reports of build jobs failing.

  2. identified May 25, 2026, 02:17 PM UTC

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

  3. monitoring May 25, 2026, 06:21 PM UTC

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

  4. resolved May 25, 2026, 07:26 PM 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 reach out to our team at [email protected]

Read the full incident report →

Notice December 20, 2024 Trials not working 39d

Started Dec 20, 2024, 06:44 PM UTC· resolved Jan 28, 2025, 06:45 PM UTC

  1. investigating Dec 20, 2024, 06:44 PM UTC

    Trials are currently unavailable. The issue has been identified, and we are preparing a fix. In the meantime, please reach out to [email protected] if you have any questions.

  2. resolved Jan 28, 2025, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →