Webdock - Notice history

All systems operational

Denmark: Network Infrastructure - Operational

100% - uptime
Feb 2026 · 100.0%Mar · 99.99%Apr · 100.0%

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Denmark: Storage Backend - Operational

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

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Denmark: General Infrastructure - Operational

100% - uptime
Feb 2026 · 99.96%Mar · 99.92%Apr · 100.0%

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Webdock Statistics Server - Operational

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

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Webdock Dashboard - Operational

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

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Webdock Website - Operational

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

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Webdock Image Server - Operational

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

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Webdock REST API - Operational

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

Previous page

Next page

Feb 2026
Mar 2026
Apr 2026

Notice history

Apr 2026

No notices reported this month

Mar 2026

Single Host Reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
Single Host Reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
Storage Backend in DK-DC1 under maintenance.
  • Completed
    March 12, 2026 at 8:23 PM
    Completed
    March 12, 2026 at 8:23 PM

    Maintenance has completed successfully. All snapshots operations once again available.

  • In progress
    March 12, 2026 at 7:00 PM
    In progress
    March 12, 2026 at 7:00 PM

    We are performing some needed maintenance in storage cluster DK DC1 now and for up to 2 hours. In this period, snapshot functionality will not be available.

A single host needs a reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot.

A single host needs a reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    One of the hosts (lxd based legacy host) seems unresponsive or crashed. This one needs a reboot.

Feb 2026

Problems communicating with Epyc Host
  • Resolved
    Resolved

    Fortunately the issue was not as critical as feared and all services came up after a reboot. We saw at most 5 minutes of downtime here today. Thank you for your patience.

  • Update
    Update

    We have to now escalate this to a downtime scenario as we are completely unable to reach the control plane of this host. The host will need a reboot and some maintenance. This means all customers on this host will now go down for anything up to 2 hours unfortunately, depending on the severity of the issue. We will update once we know more.

  • Identified
    Identified

    We are having issues communicating with one of our Epyc hosts - all customers there are running fine, we just have problems interacting with and sending commands to the host system.

Issue with a single host (lxd-based)
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The host needs a reboot for proper functioning. Sorry for the inconvenience

Issue with lxd host
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
Issue with a single host (lxd-based)
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The host requires a reboot. Instances will face downtime for 2-5 minutes.

    Sorry for the inconvenience.

Feb 2026 to Apr 2026

Next