Live / Wave / Incident
Wave: Error page when trying to access Wave
Wave · waveapps.comCritical outageResolved2026-10-05 17:15 UTC
Public — what happened
Summary
Wave reported a critical incident on October 5, 2026, in which people trying to reach Wave were shown an error page instead. The company began looking into the problem at 16:13 UTC and said at 16:56 UTC that it had found the issue, though it did not describe the cause publicly. Wave said a fix was in place by 17:10 UTC, and it marked the incident resolved at 17:15.
Affected
Web Application, Accounting, Invoicing, Payments, Payroll, Receipts Processing, Mobile Application
Timeline
- Started — 2026-10-05 16:13 UTC
- Investigating — 2026-10-05 16:13 UTC (2 updates)
- Identified — 2026-10-05 16:56 UTC
- Monitoring — 2026-10-05 17:10 UTC
- Resolved — 2026-10-05 17:15 UTC · 1h 02m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Wave against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Wave: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Wave report →
More from Wave
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.