Is Wave Down?

No — Wave is up

Wave's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 202 ms

Right now

The verdict is the worse of these two. How we decide

Wave's status page

status.waveapps.com · read just now · checked every 3 minutes

Operational

Wave's components, as its status page reports them
Component	Status
Web Application	Operational
Accounting	Operational
Invoicing	Operational
Payments	Operational
Payroll	Operational
Receipts Processing	Operational
Mobile Application	Operational

Open their status page

FlareWarden checks

waveapps.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 202 ms
Checked: 25 minutes ago

By region

Ashburn reachable, 155 ms
Chicago reachable, 115 ms
Johannesburg reachable, 113 ms
London reachable, 182 ms
Los Angeles reachable, 114 ms
Singapore reachable, 126 ms
São Paulo reachable, 623 ms
Tokyo reachable, 195 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	97 ms	1 ms	13 ms	149 ms
Chicago	71 ms	1 ms	6 ms	109 ms
Johannesburg	71 ms	0 ms	9 ms	110 ms
London	131 ms	2 ms	9 ms	175 ms
Los Angeles	68 ms	2 ms	9 ms	109 ms
Singapore	81 ms	1 ms	9 ms	122 ms
São Paulo	569 ms	2 ms	11 ms	617 ms
Tokyo	143 ms	1 ms	9 ms	192 ms

We check that waveapps.com loads, not every feature behind it. Test it yourself

History

Incidents Wave reported

Since Oct 22, 2 days · from status.waveapps.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Wave website availability

Measured by FlareWarden · waveapps.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 195ms

Last 30 days

75-day clean streak

Sep 24 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of waveapps.com from multiple regions every 6 hours. Wave's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 75 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Wave itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Wave goes down

We check Wave every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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