Vendor reports: degradedResolved · vendor status “resolved”Official status API

Linux builds not being processed for .com

Reported by Travis CI · Developer Tools & CI/CD · source last read 3 min ago

Vendor start
Feb 4, 2020, 20:07 UTC
Vendor's clock
Resolved
Feb 4, 2020, 22:36 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 03:40 UTC
Statuswall's clock
Duration
2 h 29 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Travis CI reports degraded: "Linux builds not being processed for .com".[E1, E2]
  • The vendor marked it resolved at 2020-02-04 22:36 UTC.[E3, E7]

Affected products and regions

  • Components: Linux and Windows Builds.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 03:40 UTC · summary s1, evidence 5ea0fc33a3e9fb64

Evidence (8)
  1. E1Travis CI reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Linux builds not being processed for .com". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2020-02-04 20:07 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Linux and Windows Builds. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2020-02-04 22:36 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 03:40 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: Linux and Windows Builds

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Travis CI is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Feb 4, 2020, 20:07 UTCVendor-reported startVendor time
  2. Feb 4, 2020, 22:36 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 03:40 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall
Travis CI: Linux builds not being processed for .com — statuswall