JouwWeb internal 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 JouwWeb internal status100.00% uptime history

Every Recorded JouwWeb internal Incident

JouwWeb internal incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 2, 2026Blog is down1h 29mResolved
Sep 1, 2026Zendesk and Blog are down27h 52mResolved
Aug 31, 2026Landing and Website rendering are down42h 6mResolved
Aug 29, 2026Zendesk and Blog are down107h 34mResolved
Aug 27, 2026Blog is down146h 29mResolved
Aug 25, 2026Webmail is down192h 56mResolved
Aug 22, 2026Zendesk is down266h 21mResolved
Aug 20, 2026Blog was unavailable315h 23mResolved
Aug 17, 2026Test downtime192h 12mResolved
Aug 14, 2026Blog is being updated457h 33mResolved
Jul 24, 2026Short and brief periods of downtime due to high request rate765h 37mResolved
Jul 7, 2026Email degraded1177h 55mResolved
Jun 29, 2026DDoS attack1373h 40mResolved
Jun 15, 2026Scanning attack on multiple websites1694h 9mResolved

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 JouwWeb internal 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 JouwWeb internal 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 JouwWeb internal 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 JouwWeb internal outage in this window ran 70d 14h, against a mean recovery of 20d 2h. If you depend on JouwWeb internal 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.