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

Degraded file export performance

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

Official source (opens in a new tab)
Vendor start
Jun 14, 2026, 23:05 UTC
Vendor's clock
Resolved
Jun 15, 2026, 13:55 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
14 h 50 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 degraded: "Degraded file export performance".[E1, E2]
  • The vendor marked it resolved at 2026-06-15 13:55 UTC.[E3, E7]

Affected products and regions

  • Components: Expensify Website And Mobile App, Integration APIs.[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-06-15 13:55 UTC · summary s1, evidence eab47b051c3f5a13

Evidence (7)
  1. E1Expensify reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Degraded file export performance". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-06-14 23:05 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 Website And Mobile App, Integration APIs. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-06-15 13:55 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Expensify Website And Mobile App, Integration APIs

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

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. Jun 14, 2026, 23:05 UTCVendor-reported startVendor time
  2. Jun 15, 2026, 13:55 UTCVendor-reported resolutionVendor time

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