Webador Outage History

14 incidents recorded over the last 365 days, 14 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 Webador status99.99% uptime history

Every Recorded Webador Incident

Webador incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 21, 2026System temporarily offline3h 50mResolved
Oct 5, 2026Downtime738h 4mResolved
Sep 18, 2026Search for similar images is currently offline1149h 40mResolved
Sep 15, 2026Temporary Domain Operations Downtime on Sept 154h 0mResolved
Aug 21, 2026New Mollie connection will fail1714h 57mResolved
Aug 15, 2026Automated Email Delivery Issues1858h 57mResolved
Jul 24, 2026Brief periods of downtime due to high request rate1643h 57mResolved
Jul 21, 2026Emails with invalid links were generated1712h 38mResolved
Jul 7, 2026Email degraded2056h 15mResolved
Jun 29, 2026Website Editor is currently unavailable. 1528h 26mResolved
Jun 29, 2026DDoS attack1531h 40mResolved
Jun 17, 2026Automated Email Delivery Issues1815h 37mResolved
Jun 15, 2026Performance degradation due to elevated network traffic1852h 9mResolved
Jun 9, 2026High error rate during AI onboarding flow2001h 8mResolved

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 Webador 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 Webador 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 Webador 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 Webador outage in this window ran 85d 16h, against a mean recovery of 58d 8h. If you depend on Webador 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.