Changes / Travis CI / Builds not starting/queuing or stucks on .COM

Travis CI: Major incident: Builds not starting/queuing or stucks on .COM

Summary

Travis CI reported a major .COM outage with builds not starting, queuing or getting stuck, from 2020-03-24 10:42 UTC to 2020-03-24 12:34 UTC, lasting 1 h 51 min. The vendor attributed the problem to “misusage,” reported recovering infrastructure, and confirmed builds should behave normally after resolution.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 92%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Builds not starting/queuing or stucks on .COM
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2020-03-24 10:42 UTC
AddedResolved time#5
Before: not present
After: 2020-03-24 12:34 UTC
AddedUpdatemonitoring#6
Before: not present
After: We have observed the root cause of the problem with the builds isn't starting due to misusage. Currently, we are recovering the infrastructure.
AddedUpdateresolved#7
Before: not present
After: Thank you for your patience. The incident has been resolved and builds should behave as normal.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Builds not starting/queuing or stucks on .COM (this change)
Travis CI reported a major .COM outage with builds not starting, queuing or getting stuck, from 2020-03-24 10:42 UTC to 2020-03-24 12:34 UTC, lasting 1 h 51 min. The vendor attributed the problem to “misusage,” reported recovering infrastructure, and confirmed builds should behave normally after resolution.
Major incident

All Travis CI changes → · Travis CI profile · Markdown · JSON