NoVPS - Notice history

All systems operational

Website - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

App - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Workers - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Public clusters - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 99.93%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Private clusters - Operational

100% - uptime
Mar 2026 · 100.0%Apr · 99.60%May · 100.0%

Previous page

Next page

Mar 2026
Apr 2026
May 2026

Notice history

May 2026

No notices reported this month

Apr 2026

Issues with cross-node networking
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    We were able to localize the problem. The affected node has been removed from the cluster, and all applications running on it have been redistributed among the other nodes.

  • Identified
    UTC
    Identified
    We are continuing to work on a fix for this incident.
Errors in cross-node communication in private clusters
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Update
    UTC
    Update

    The public cluster has recovered, though we are still seeing an elevated number of errors in some public clusters.

  • Monitoring
    UTC
    Monitoring

    We implemented a fix and are currently monitoring the result.

    A network configuration error on our provider's end caused a VLAN overlap.

    We have reconfigured the cluster subnets to prevent similar issues in the future.

  • Identified
    UTC
    Identified
    We are continuing to work on a fix for this incident.
  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

Mar 2026

No notices reported this month

Mar 2026 to May 2026

Next