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

[us-west-2] Increased failure rate on public API

Reported by Front · Communication & Messaging · source last read just now

Vendor start
Nov 18, 2024, 20:03 UTC
Vendor's clock
Resolved
Nov 18, 2024, 22:18 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 16 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

  • Front reports partial outage: "[us-west-2] Increased failure rate on public API".[E1, E2]
  • The vendor marked it resolved at 2024-11-18 22:18 UTC.[E3, E7]

Affected products and regions

  • Regions: us-west-2 (read from the title, so inferred).[E5]
  • Components: API and integrations.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2024-11-18 22:18 UTC · summary s1, evidence 79e47b473261965b

Evidence (7)
  1. E1Front reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "[us-west-2] Increased failure rate on public API". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-11-18 20:03 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-west-2. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: API and integrations. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-11-18 22:18 UTC. (vendor) source (opens in a new tab)

Affected scope

us-west-2

Components: API and integrations

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

Front 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. Nov 18, 2024, 20:03 UTCVendor-reported startVendor time
  2. Nov 18, 2024, 22:18 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.