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

Errors increase for API in cluster us3

Reported by Pusher · Communication & Messaging · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Jan 29, 2026, 10:38 UTC
Vendor's clock
Resolved
Jan 29, 2026, 10:58 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
21 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

  • Pusher reports operational: "Errors increase for API in cluster us3".[E1, E2]
  • The vendor marked it resolved at 2026-01-29 10:58 UTC.[E3, E7]

Affected products and regions

  • Components: Channels REST API.[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-01-29 10:58 UTC · summary s1, evidence e3942f41933a5f90

Evidence (7)
  1. E1Pusher reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Errors increase for API in cluster us3". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-01-29 10:38 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Channels REST API. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-01-29 10:58 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Channels REST API

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

Pusher 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. Jan 29, 2026, 10:38 UTCVendor-reported startVendor time
  2. Jan 29, 2026, 10:58 UTCVendor-reported resolutionVendor time

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