Skip to main content
Expensify logo

Is Expensify Down?

No — Expensify is up

Reachable from all 8 checked regions

Average response time: 338ms

Last checked · checks run every 6 hours

Official status page: https://status.expensify.com

Expensify uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
347ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 23 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

23-day clean streak
Sep 10: no data
Sep 11: no data
Sep 12: no data
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: 100.00% uptime, 16 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 40 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 32 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 24 checks
Sep 10 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn
332ms
DNS 85ms TCP 1ms TLS 13ms TTFB 326ms
cdg
521ms
DNS 115ms TCP 2ms TLS 14ms TTFB 377ms
dfw
198ms
DNS 81ms TCP 2ms TLS 9ms TTFB 194ms
ewr
221ms
DNS 62ms TCP 2ms TLS 9ms TTFB 215ms
fra
311ms
DNS 28ms TCP 2ms TLS 15ms TTFB 299ms
gru
463ms
DNS 183ms TCP 2ms TLS 12ms TTFB 453ms
iad
247ms
DNS 21ms TCP 3ms TLS 10ms TTFB 194ms
jnb
411ms
DNS 14ms TCP 1ms TLS 13ms TTFB 404ms

What Expensify does

Expensify is spend management software for receipts and expense reports. Employees photograph receipts with SmartScan, reports are built and routed for approval automatically, and finance teams sync the results into their accounting system. It also runs the Expensify Card and imports company card feeds from banks, so it sits between spending and the ledger.

What an outage looks like

The website and mobile app fail to load or will not sign in. SmartScan leaves receipts stuck on scanning instead of reading the merchant and amount. Report PDFs will not generate. Card transactions stop appearing because a bank feed is delayed. Accounting exports fail through the integration APIs, and notification emails and text messages do not arrive.

What to do about it

Read status.expensify.com row by row. Expensify separates the Website And Mobile App, SmartScan, Report PDFs, Integration APIs, outgoing email and SMS, and lists each company card feed on its own, including American Express, Bank of America, Chase, Citi, Capital One and Wells Fargo. A missing card transaction usually traces to one bank feed, not to Expensify as a whole.

Is it down for everyone, or just you?

If this page says Expensify is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Expensify outage FAQ

Why are my receipts stuck on scanning?
SmartScan is its own component on status.expensify.com, so it can be degraded while the app works normally. If it shows an incident, keep the receipts where they are rather than uploading them again, since duplicates then need deleting by hand. If SmartScan is operational, check the image itself: a blurry or cropped photo takes longer and may need manual entry.
My company card transactions are missing. Is Expensify down?
Probably not all of it. Expensify lists commercial card feeds per bank, including American Express, Bank of America, Brex, Capital One, Chase, Citi and Wells Fargo, as separate components. Find your bank's row. If that feed is delayed, the transactions normally arrive once it recovers, so wait rather than adding them manually and creating duplicates.
Why did my accounting export fail?
Check Integration APIs on the status page. Exports to accounting systems go through that component, so they can fail while reports, approvals and SmartScan all work. If it is degraded, leave approved reports in place and export again after recovery, then confirm in the accounting system that nothing was posted twice.
Is the Expensify Card affected when the app is down?
Expensify reports the Expensify Card as a separate component from the Website And Mobile App, so an app outage does not by itself mean the card is failing. Check the card's own row. If a purchase is declined and that row shows a problem, use another payment method and file the expense afterwards.
Is Expensify down for everyone or just me?
Compare status.expensify.com with this page's regional measurements. If both look healthy, the problem is likely local: an outdated mobile app, a network that blocks uploads, or single sign-on through your company's identity provider. If the site fails from several regions at once, it is Expensify rather than you.

How we measure this

  • We request Expensify's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Expensify publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Expensify goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required