Webdock - Notice history

All systems operational

Denmark: Network Infrastructure - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Denmark: Storage Backend - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Denmark: General Infrastructure - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Webdock Statistics Server - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Webdock Dashboard - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Webdock Website - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Webdock Image Server - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Webdock REST API - Operational

100% - uptime
Jan 1781 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 1781
Feb 1781
Mar 1781

Notice history

Sep 2025

Another LXD-based host needs a reboot
  • Resolved
    Resolved

    This incident has been resolved. Sorry for the inconvenience.

  • Identified
    Identified

    Host reboot is required to fix the frozen system. 5-10 of downtime is to be expected.

An lxd-based container host requires a reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    The containers there refuse to start. A reboot is required, hence there will be downtime for 5-10 minutes.

A single host needs a reboot
  • Resolved
    Resolved

    This incident has been resolved. Sorry for inconvenience caused.

  • Identified
    Identified

    A host needs a reboot. There will be 5-10 minutes of downtime.

A Ryzen host is unreachable/offline
  • Resolved
    Resolved

    This incident has been resolved. Sorry for the inconvenience.

  • Identified
    Identified

    Or NOC guys are working on this one. Will update the page soon.

Issue with a single host
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.

Aug 2025

Single host down in DK DC1
  • Resolved
    Resolved

    The host is back up and all customer instances are running. We apologize for any inconvenience caused.

  • Identified
    Identified

    We have a Xeon host down in DK DC1 - NOC team is working on bringing the system back up. We hope to have customer instances up and running in about 10-15 minutes.

Issue with a single Ryzen host
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The host needs a reboot. There will be 15 to 20 minutes of downtime.

Yet another LXD host needs a reboot
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The system is a bit frozen. The snapshot and start operations seem to hang. A reboot is required, hence a 5-10 minutes of downtime

Issue with an another LXD-based host
  • Resolved
    Resolved

    This incident has been resolved. Sorry for the inconvenience.

  • Investigating
    Investigating

    The host needs a reboot and will be up in 5-10 minutes.

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

    The host needs a reboot for proper functioning. Instances will see 5-10 minutes of downtime.

Jul 2025

Small outage in DK DC1
  • Resolved
    Resolved

    We had a small outage again affecting Ryzen and Epyc workloads as well as our dashboard and related services. The event lasted about 10 minutes. All customers should be operational again. We apologize for the inconvenience.

Partial outage in DK DC affecting Webdock dashboard and Epyc/Ryzen instances
  • Resolved
    Resolved

    This incident has been resolved and all customers and services are back up. We sincerely apologize for the inconvenience caused here tonight. The incident was indeed a power event, and our electrician will be investigating the root cause further in the morning and hopefully we can find the cause and prevent anything similar happening again in the future.

  • Identified
    Identified

    The incident unfortunately seems to be a complete power outage in the rack. A DC tech is en-route to the location to inspect the situation and hopefully power the rack back on. If this is a simple power event, we should be back up in about 45-60 minutes.

  • Investigating
    Investigating

    We are currently investigating this incident. A network-level event seems to have affected a single rack in our DC, taking down our dashboard and some related services, as well as a number of our Epyc/Ryzen customer instances.

Issue with a single host
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    One of our container-based hosts needs a reboot. There will be downtime for few minutes

Frozen lxd-based Host
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    The host needs a reboot. Few minutes of downtime is to be expected.

Issue again with a single host (container-based based)
  • Resolved
    Resolved

    This incident has been resolved. Sorry for the inconvenience caused.

  • Identified
    Identified

    The host requires a reboot. There will be few minutes of downtime.

Jul 2025 to Sep 2025

Next