Skip to content
PulseWatchOUTAGE.INTEL
Expensify logo

Productivity

Is Expensify down right now?

NormalOfficial status last polled Oct 1, 2026 12:28 UTCexpensify.comOfficial status page

Are you on the Expensify team and see something inaccurate? Report it to us. We respond within one business day.

Is Expensify down right now?

No. Expensify has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 1, 2026 13:30 UTC

Normal

Expensify is operating normally

As of Oct 1, 2026 13:30 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 18, 2026 20:29 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Expensify.

1

Incident days

29

No recorded incident

2h 10m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Expensify. Hover a day for detail.

Sep 2Sep 7Sep 12Sep 17Sep 22Sep 2701234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

1

Days with incidents

1 incident

Busiest day

2h 10m

Recorded duration

Report volume

0 reports in last 24H

01:30 PM05:00 PM08:30 PM12:00 AM03:30 AM07:00 AM10:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Expensify outage on September 18 2h 9m disruption

Sep 18, 06:19 PM → Sep 18, 08:29 PM · 2h 9m · high

On September 18, 2026, Expensify experienced a major-impact incident. The vendor reported the issue on its status page, and it was resolved after 2 hours and 9 minutes.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
2h 9m
until recovery

Impact

This incident affected Expensify for a duration of 2 hours and 9 minutes, with a high severity. During this period, the vendor reported a major-impact incident on its status page. No user-reported data was collected for this incident, and therefore no specific user-visible features, regions, or issue types can be identified from user reports.

Outage timeline

  1. Sep 18, 06:19 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 18, 06:19 PM

    Status updated: possible issue

  3. Sep 18, 08:29 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 18, 06:19 PM

    Expensify status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

99.70%

90-day uptime

99.83%

Calculated from Expensify's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Expensify: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Expensify or have an alert rule on it can be alerted, labelled vendor-reported.

9/18/2026, 6:19:45 PM · 2h 9m

06:19 PM08:29 PM
Detection9/18/2026, 6:19:45 PM · 12d ago

Detected — high severity

Expensify: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Expensify or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Expensify incident correlated across 1 signal group: official/vendor.

8/31/2026, 5:08:36 PM · 1h 36m

05:08 PM06:45 PM
Detection8/31/2026, 5:08:36 PM · 1mo ago

Detected — medium severity

Expensify incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Expensify enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

expensify.com