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

Expensify Cards impacted by ongoing partner outage

Reported by Expensify · HR, Finance & Ops · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Jan 22, 2026, 19:36 UTC
Vendor's clock
Resolved
Jan 22, 2026, 20:45 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 9 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

  • Expensify reports partial outage: "Expensify Cards impacted by ongoing partner outage".[E1, E2]
  • The vendor marked it resolved at 2026-01-22 20:45 UTC.[E3, E7]

Affected products and regions

  • Components: Expensify Card.[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-22 20:45 UTC · summary s1, evidence 8e819a357dc30477

Evidence (7)
  1. E1Expensify reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Expensify Cards impacted by ongoing partner outage". (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-22 19:36 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Expensify Card. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-01-22 20:45 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Expensify Card

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

Expensify 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 22, 2026, 19:36 UTCVendor-reported startVendor time
  2. Jan 22, 2026, 20:45 UTCVendor-reported resolutionVendor time

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