Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Some builds are not being triggerred

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

Official source (opens in a new tab)
Vendor start
Mar 1, 2022, 12:08 UTC
Vendor's clock
Resolved
Mar 1, 2022, 13:03 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 03:40 UTC
Statuswall's clock
Duration
55 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 partial outage: "Some builds are not being triggerred".[E1, E2]
  • The vendor marked it resolved at 2022-03-01 13:03 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 11f3daf13a0b52da

Evidence (8)
  1. E1Travis CI reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Some builds are not being triggerred". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2022-03-01 12:08 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: 2022-03-01 13:03 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. Mar 1, 2022, 12:08 UTCVendor-reported startVendor time
  2. Mar 1, 2022, 13:03 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 03:40 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall