Zerops Outage History

Zerops is up right now

Zerops had 7 outages in the last 2 years — averaging 0.3 incidents per month.

There were 7 Zerops outages since January 12, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.zerops.io

Minor July 20, 2026

Control plane has degraded ...

Detected by Pingoru
Jul 20, 2026, 06:00 AM UTC
Resolved
Jul 20, 2026, 06:00 AM UTC
Duration
Affected: Current status by service (API & Dashboard)
Timeline · 1 update
  1. investigating Jul 20, 2026, 06:00 AM UTC

    One of our physical server nodes had a corrupted motherboard, which resulted in a cascade of stuck processes in the process manager. We are working on a fix (the motherboard is being replaced, and we are implementing changes to make sure processes won't get stuck next time). User applications and services in HA shouldn't be affected. The ability to run actions/deploys will be resumed soon.

Read the full incident report →

Minor June 20, 2026

Sites using Zerops' shared ...

Detected by Pingoru
Jun 20, 2026, 06:16 AM UTC
Resolved
Jun 20, 2026, 06:16 AM UTC
Duration
Affected: Object Storage (EU Central (prg1))
Timeline · 1 update
  1. resolved Jun 20, 2026, 06:16 AM UTC

    An issue during a re-configuration of our proxy service after a certificate renewal caused sites using our shared IPv4 and our preview sub-domains (*.{prg1|sea1|ny1}.zerops.app) to stop routing. Sites with a dedicated IPv4 or using only IPv6 (either directly or behind an e.g. Cloud Flare proxy), were unaffected. Incident started at 07:58 AM CEST and was resolved at 08:16 AM CEST.

Read the full incident report →

Major January 14, 2025

API & Dashboard functionali...

Detected by Pingoru
Jan 14, 2025, 07:42 PM UTC
Resolved
Jan 14, 2025, 07:42 PM UTC
Duration
Affected: Homepage (Zerops.io homepage)Current status by service (API & Dashboard)
Timeline · 1 update
  1. resolved Jan 14, 2025, 07:42 PM UTC

    As part of ongoing effort to repair our billing database cluster, which caused the previous accident ealier this week a critical internal component was restarted which caused a cascade of fails which shortly affected user applications. We are working on restoring the system to full health. Update: user apps back up and dashboard / API access restored

Read the full incident report →