WaveSpeedAI Outage History

5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live WaveSpeedAI status99.88% uptime history

Every Recorded WaveSpeedAI Incident

WaveSpeedAI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 8, 2026API model health, Frontend model health, and 1 other service are down1380h 50mResolved
Aug 20, 2026API model health is down1741h 18mResolved
Jul 30, 2026API model health, Frontend model health, and 1 other service are down1489h 45mResolved
Jul 29, 2026API model health, Frontend model health, and 1 other service are down1519h 40mResolved
Jul 20, 2026API model health and Frontend model health are down1747h 7mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next WaveSpeedAI incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This WaveSpeedAI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before WaveSpeedAI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single WaveSpeedAI outage in this window ran 72d 19h, against a mean recovery of 65d 15h. If you depend on WaveSpeedAI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.