Expensify Outage History

37 incidents recorded over the last 365 days, 37 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Expensify status100.00% uptime history

Every Recorded Expensify Incident

Expensify incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 8, 2026Expensify site is downThis incident has been resolved.6 minResolved
Sep 18, 2026Loading issue on Expenses pageThis incident has been resolved.1h 16mResolved
Aug 31, 2026Site SlowsThis incident has been resolved.1h 41mResolved
Aug 19, 2026Site IssueThis incident has been resolved.2h 44mResolved
Aug 9, 2026Expensify Site - Degraded PerformanceThis incident has been resolved.8h 44mResolved
Jul 15, 2026Problems uploading receiptsThis incident has been resolved.19 minResolved
Jul 9, 2026Site IssueThis incident has been resolved.4h 47mResolved
Jul 6, 2026Degraded performanceThis incident has been resolved.1h 18mResolved
Jun 29, 2026Degraded PerformanceThis incident has been resolved.5h 6mResolved
Jun 18, 2026Degraded PerformanceThis incident has been resolved.3 minResolved
Jun 14, 2026Degraded file export performanceThis issue has been fully resolved.14h 50mResolved
Jun 10, 2026Site IssueThe Expensify website is currently operational, and credit card connections are importing transactions.15h 49mResolved
Jun 10, 2026Site IssueThis incident has been resolved.1h 48mResolved
May 20, 2026Site IssueThis incident has been resolved.1h 9mResolved
May 19, 2026Site IssueThis incident has been resolved.1h 12mResolved
May 19, 2026Expensify AI auto-categorization temporarily disabledThis incident has been resolved.6h 13mResolved
May 19, 2026Degraded PerformanceThis incident has been resolved.10 minResolved
May 12, 2026Degraded PerformanceThis incident has been resolved.41 minResolved
May 7, 2026Site IssueThis incident has been resolved.7 minResolved
Apr 6, 2026Degraded PerformanceThis incident has been resolved.4h 28mResolved
Mar 20, 2026Expensify Magic Codes not workingThis incident has been resolved.86h 45mResolved
Mar 4, 2026Site IssueThis incident has been resolved.36 minResolved
Mar 3, 2026Expensify Billing – Duplicate or Missing Charges/CashbackThis incident has been resolved. Should you have any questions, feel free to reach out to us via Concierge or at concierge@expensify.com.142h 25mResolved
Mar 2, 2026Continuing to monitor site issuesThis incident has been resolved.12h 10mResolved
Mar 2, 2026Site IssuesThis incident has been resolved.1h 45mResolved
Mar 2, 2026Site DownThis incident has been resolved.16 minResolved
Mar 1, 2026Investigating Elevated Site LatencyThis incident has been resolved.35h 15mResolved
Feb 24, 2026Site DownThis incident has been resolved.39 minResolved
Feb 10, 2026Chase Cards impacted by Chase Import APIThis incident has been resolved.52 minResolved
Jan 22, 2026Expensify Cards impacted by ongoing partner outageOur Expensify Card issuing partner, Marqeta, has identified the root cause of the issue and deployed a fix. Services have recovered, and Expensify Card transactions and tokenization should now be functioning…1h 9mResolved
Jan 21, 2026Site outageThis incident has been resolved.5h 1mResolved
Jan 19, 2026Site outageWe have identified and resolved the issue, and the site is back up and running.11 minResolved
Jan 15, 2026Site outageWe identified the issue and pushed a fix. The site is back up.2 minResolved
Dec 22, 2025Card Data temporarily unavailableCredit Card updates are now back to normal.1h 32mResolved
Dec 17, 2025Degraded PerformanceThis incident has been resolved.56 minResolved
Dec 11, 2025Users logged in with SAML/SSO may be repeatedly logged outThis incident has been resolved. Please update to app version 9.2.76-0 or above.25h 52mResolved
Nov 26, 2025Site outageWe identified the issue and pushed a fix. The site is back up.8 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Expensify incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Expensify Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Expensify acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Expensify outage in this window ran 5d 22h, against a mean recovery of 10h 29m. If you depend on Expensify in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.