We started checking Wave on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Wave reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Wave's own status page declared. Below it, any public chatter we saw about Wave and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Wave's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Wave in the last 24 hours, which is not evidence that nothing is wrong.
Wave's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Wave's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Wave next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts4 in the last hour (prior day averaged 7.1/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
425
US-West
99.68%
313
Europe
100.00%
288
Asia-Pacific
100.00%
172
Their declared record
Wave's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Wave Support Impacted by 3rd party incidentAll systems operational
Nov 4, 2026, 8:23 PM UTC to Nov 5, 2026, 3:36 AM UTC (7h 14m)resolved
their latest update (Nov 5, 2026, 3:36 AM UTC): Our 3rd party partner has resolved this incident, and the in-app help function is working once again.
Incorrect Payout Date DisplayMinor incident
Oct 13, 2026, 3:27 PM UTC to Oct 13, 2026, 5:14 PM UTC (1h 48m)resolved
their latest update (Oct 13, 2026, 5:14 PM UTC): We've identified an in-app error on the Sales & Payments > Payments page for some Wave Payments users. Users may see an incorrect estimated deposit date of Monday October 12th. This date did not properly factor in the bank holiday that took place yesterday.
Payouts are processi…
Error page when trying to access WaveAll systems operational
Oct 5, 2026, 4:13 PM UTC to Oct 5, 2026, 5:15 PM UTC (1h 2m)resolved
their latest update (Oct 5, 2026, 5:15 PM UTC): This incident has been resolved.
Latency across WaveAll systems operational
Oct 1, 2026, 3:28 PM UTC to Oct 1, 2026, 3:53 PM UTC (24 min)resolved
their latest update (Oct 1, 2026, 3:53 PM UTC): This incident has been resolved.
Investigating reports of login errorsMajor outage
Sep 22, 2026, 6:49 AM UTC to Sep 22, 2026, 7:30 AM UTC (41 min)resolved
their latest update (Sep 22, 2026, 7:30 AM UTC): This incident has been resolved.
Investigating reports of delayed or failed receipt scan uploadsMinor incident
Aug 8, 2026, 1:35 AM UTC to Aug 8, 2026, 4:09 AM UTC (2h 35m)resolved
their latest update (Aug 8, 2026, 4:09 AM UTC): This incident has been resolved. Receipts may take a few minutes to fully upload. If you attempted a receipt upload between 7:13 PM and 11:08 PM on Friday, August 7, 2026, please re-upload your receipt.
Investigating reports of business logos not appearing on invoice or estimate emails and exported PDF'sMinor incident
Jul 29, 2026, 7:43 PM UTC to Jul 29, 2026, 8:20 PM UTC (37 min)resolved
their latest update (Jul 29, 2026, 8:20 PM UTC): This incident has been resolved.
Timesheet Saving Errors - PayrollPartial outage
Jun 23, 2026, 4:57 PM UTC to Jun 23, 2026, 7:20 PM UTC (2h 23m)resolved
their latest update (Jun 23, 2026, 7:20 PM UTC): The issue has been resolved. We apologize for the interruption.
Wave Payroll Impacted by 3rd party incidentMinor incident
Jun 18, 2026, 3:17 PM UTC to Jun 19, 2026, 1:05 AM UTC (9h 47m)resolved
their latest update (Jun 19, 2026, 1:05 AM UTC): As it turns out, some impacted payroll deposits will be delayed past June 18th. We have reached out to those impacted employers directly. Beyond those impacted, the incident has been resolved between our 3rd party partner and their banking partner.
Investigating reports of login errorsMinor incident
Jun 1, 2026, 10:46 PM UTC to Jun 1, 2026, 11:31 PM UTC (45 min)resolved
their latest update (Jun 1, 2026, 11:31 PM UTC): We have resolved the issues that were affecting the sign in page.
Showing the 10 most recent of 51 incidents Wave has declared in the history we hold.
These entries are Wave's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Wave's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.