Mittwald Outage History

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

Every Recorded Mittwald Incident

Mittwald incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Einschränkung festgestellt—Investigating
Nov 4, 2026Einschränkung festgestellt5h 35mResolved
Nov 3, 2026Störung1h 3mResolved
Nov 2, 2026Geplante Wartungsarbeiten47 minResolved
Oct 28, 2026Geplante Wartungsarbeiten38 minResolved
Oct 27, 2026Einschränkung AI-Hosting festgestellt19 minResolved
Oct 26, 2026Geplante Wartungsarbeiten1h 14mResolved
Oct 22, 2026Sicherheitslücke in Node.js5h 8mResolved
Oct 21, 2026Geplante Wartungsarbeiten1h 44mResolved
Oct 21, 2026Vorsorgliche Einschränkungen aufgrund der aktuellen PHP-Sicherheitslücke10h 12mResolved
Oct 20, 2026Geplante Wartungsarbeiten5h 2mResolved
Oct 19, 2026Geplante Wartungsarbeiten3h 1mResolved
Oct 19, 2026Geplante Wartungsarbeiten6h 0mResolved
Oct 17, 2026Einschränkung festgestellt2h 27mResolved
Oct 15, 2026Einschränkung festgestellt1h 8mResolved
Oct 13, 2026Geplante Wartungsarbeiten22 minResolved
Oct 8, 2026Geplante Wartungsarbeiten2h 0mResolved
Oct 8, 2026Einschränkung festgestellt30 minResolved
Oct 1, 2026Einschränkung festgestellt15 minResolved
Sep 29, 2026Einschränkung festgestellt31 minResolved
Sep 17, 2026Einschränkung festgestellt27 minResolved
Sep 14, 2026Geplante Wartungsarbeiten2h 4mResolved
Sep 9, 2026Geplante Wartungsarbeiten2h 51mResolved
Sep 9, 2026Geplante Wartungsarbeiten3h 1mResolved
Sep 9, 2026Einschränkung festgestellt42 minResolved
Sep 7, 2026Einschränkung festgestellt im Cluster Altgemeinde51 minResolved
Sep 3, 2026Einschränkung festgestellt36 minResolved
Sep 2, 2026Geplante Wartungsarbeiten3h 2mResolved
Aug 28, 2026Einschränkung festgestellt3h 26mResolved
Aug 27, 2026Einschränkung festgestellt38 minResolved

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 Mittwald 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 Mittwald 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 Mittwald 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 Mittwald outage in this window ran 10h 12m, against a mean recovery of 2h 16m. If you depend on Mittwald 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.