Is Wave Down?

No — Wave is up

Reachable from all 8 checked regions

Average response time: 197ms

Last checked 14 minutes ago · checks run every 6 hours

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

Wave uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

179ms

Avg response, 30 days

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

30-day history

63-day clean streak

Sep 12 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.

ams

149ms

DNS 109ms TCP 2ms TLS 9ms TTFB 144ms

arn

85ms

DNS 50ms TCP 1ms TLS 7ms TTFB 82ms

nrt

229ms

DNS 186ms TCP 1ms TLS 19ms TTFB 226ms

ord

209ms

DNS 154ms TCP 2ms TLS 8ms TTFB 203ms

sin

302ms

DNS 266ms TCP 1ms TLS 7ms TTFB 298ms

sjc

153ms

DNS 102ms TCP 2ms TLS 10ms TTFB 148ms

syd

330ms

DNS 294ms TCP 1ms TLS 9ms TTFB 327ms

yyz

121ms

DNS 71ms TCP 1ms TLS 13ms TTFB 116ms

What Wave does

Wave is accounting and invoicing software aimed at small businesses and sole traders. It covers bookkeeping, invoice sending, receipt capture, payments and payroll, with the core accounting free and payments and payroll charged. Owners run their billing through it, so an outage stops invoices going out and stops customer card payments being taken.

What an outage looks like

Wave reports the web app, accounting, invoicing, payments, payroll, receipts and the mobile app as separate components. Invoices fail at the send step or save without being delivered, card payments are declined or left pending, receipt uploads never finish processing, and the dashboard loads with stale or missing balances while sign-in itself still works normally.

What to do about it

Check status.waveapps.com, which separates payments and payroll from the core accounting app, so a billing problem can be narrowed to one of them quickly. If a payroll run is due, confirm afterwards that it actually submitted rather than assuming it did. Avoid resending an invoice that may already have queued, since the send step can succeed after the interface reports a failure.

Is it down for everyone, or just you?

If this page says Wave 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

Wave outage FAQ

Did my invoice send if Wave errored?

Check the invoice status and the sent log before resending, because invoicing and delivery are tracked separately from the web app and a send can complete after the interface times out. Resending creates a duplicate your customer sees, which is worse than a short delay. If the invoicing component is listed as affected, wait for it to clear and then confirm the state.

Are card payments lost during a Wave outage?

Payments is its own component and payments left pending during an incident normally resolve one way or the other once it clears, rather than disappearing. The thing to avoid is asking a customer to pay again while the first attempt is still pending, which can take the money twice. Check the payment record after the incident and reconcile before requesting anything further.

Does a Wave outage affect payroll deadlines?

An outage does not move a payroll deadline, so a run due during an incident needs following up rather than assuming. Payroll is listed as its own component on the status page, which means it can be affected while invoicing and accounting are fine. After service returns, confirm the run submitted and check the pay date rather than relying on the last screen you saw.

Wave loads but my balances look wrong. Is that an outage?

It can be. Accounting and the web app are separate components, so the interface can load while the data behind it is degraded or stale. Balances that look wrong during a reported incident are usually a display or sync problem rather than lost transactions. Avoid making correcting entries based on figures seen during an incident, since that creates real errors to unpick later.

How we measure this

We request Wave'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 Wave 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 Wave 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