Travis CI Outage History
3 incidents recorded over the last 365 days, 1 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Travis CI Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 25, 2026 | Build job(s) failuresThe 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… | 5h 13m | Resolved |
| Apr 11, 2026 | Database maintenanceSystem maintenance has been successfully completed. All systems are working as expected. We appreciate your patience during this process. | 2h 0m | Scheduled |
| Feb 28, 2026 | Database maintenanceSystem maintenance has been successfully completed. All systems are working as expected. We appreciate your patience during this process. | 3h 0m | Scheduled |
How to Read This Travis CI Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Travis CI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Travis CI outage in this window ran 5h 13m, against a mean recovery of 3h 24m. If you depend on Travis CI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.