User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 758 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 378 ms | 0 |
| Tue 01 | 0 | 0.0 | 427 ms | 0 |
| Tue 03 | 0 | 0.0 | 402 ms | 0 |
| Tue 05 | 0 | 0.0 | 381 ms | 0 |
| Tue 07 | 0 | 0.0 | 264 ms | 0 |
| Tue 09 | 0 | 0.0 | 405 ms | 0 |
| Tue 12 | 0 | 0.0 | 764 ms | 0 |
| Tue 14 | 0 | 0.0 | 444 ms | 0 |
| Tue 16 | 0 | 0.0 | 748 ms | 0 |
| Tue 18 | 0 | 0.0 | 586 ms | 0 |
| Tue 20 | 0 | 0.0 | 438 ms | 0 |
| Tue 23 | 0 | 0.0 | 355 ms | 0 |
| Wed 01 | 0 | 0.0 | 292 ms | 0 |
| Wed 03 | 0 | 0.0 | 268 ms | 0 |
| Wed 05 | 0 | 0.0 | 529 ms | 0 |
| Wed 08 | 0 | 0.0 | 815 ms | 0 |
| Wed 10 | 0 | 0.0 | 720 ms | 0 |
| Wed 12 | 0 | 0.0 | 446 ms | 0 |
| Wed 14 | 0 | 0.0 | 1421 ms | 0 |
| Wed 16 | 0 | 0.0 | 578 ms | 0 |
| Wed 18 | 0 | 0.0 | 1067 ms | 0 |
| Wed 21 | 0 | 0.0 | 432 ms | 0 |
| Wed 23 | 0 | 0.0 | 751 ms | 0 |
| Thu 01 | 0 | 0.0 | 694 ms | 0 |
| Thu 03 | 0 | 0.0 | 401 ms | 0 |
| Thu 05 | 0 | 0.0 | 736 ms | 0 |
| Thu 07 | 0 | 0.0 | 486 ms | 0 |
| Thu 09 | 0 | 0.0 | 584 ms | 0 |
| Thu 11 | 0 | 0.0 | 416 ms | 0 |
| Thu 13 | 0 | 0.0 | 291 ms | 0 |
| Thu 15 | 0 | 0.0 | 436 ms | 0 |
| Thu 17 | 0 | 0.0 | 318 ms | 0 |
| Thu 20 | 0 | 0.0 | 508 ms | 0 |
| Thu 22 | 0 | 0.0 | 280 ms | 0 |
| Thu 23 | 0 | 0.0 | 781 ms | 0 |
| Fri 01 | 0 | 0.0 | 418 ms | 0 |
| Fri 03 | 0 | 0.0 | 304 ms | 0 |
| Fri 05 | 0 | 0.0 | 768 ms | 0 |
| Fri 08 | 0 | 0.0 | 164 ms | 0 |
| Fri 10 | 0 | 0.0 | 814 ms | 0 |
| Fri 11 | 0 | 0.0 | 375 ms | 0 |
| Fri 13 | 0 | 0.0 | 430 ms | 0 |
| Fri 15 | 0 | 0.0 | 415 ms | 0 |
| Fri 17 | 0 | 0.0 | 420 ms | 0 |
| Fri 19 | 0 | 0.0 | 409 ms | 0 |
| Fri 20 | 0 | 0.0 | 425 ms | 0 |
| Fri 21 | 0 | 0.0 | 400 ms | 0 |
| Fri 22 | 0 | 0.0 | 758 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Expensya yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Expensya goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Expensya alerts to Slack, Discord or a webhook — free.
We track Expensya (expensya.com) as part of the Productivity group. Remplacez le stress et les frictions liés à la gestion des dépenses et des notes de frais des employés par la clarté et la simplicité : voici Expensya, le logiciel intelligent de gestion des dépenses pour les équipes financières modernes.
Expensya publishes an official status page at status.expensya.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 459 ms average, 164–814 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Expensya incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
459 ms on average over the last 24 hours (164–814 ms).
Yes, at https://status.expensya.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Expensya here at once, the problem is on Expensya's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Expensya. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.