Webdock - Notice history

Denmark: Storage Backend under maintenance

Denmark: Network Infrastructure - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 99.96%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Denmark: Storage Backend - Under maintenance

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Denmark: General Infrastructure - Operational

100% - uptime
Oct 2025 · 99.94%Nov · 99.98%Dec · 99.97%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Webdock Statistics Server - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Webdock Dashboard - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Webdock Website - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Webdock Image Server - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Webdock REST API - Operational

100% - uptime
Oct 2025 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2025
Nov 2025
Dec 2025

Notice history

Dec 2025

Flaky network for some /24 in DK DC1
  • Resolved
    UTC
    Resolved

    For the past two hours or so, no issues whatsoever. We are still investigating what happened exactly, and it's looking like some misconfiguration happened on our side. We will reopen this if we see further problems.

  • Investigating
    UTC
    Investigating

    We are seeing intermittent packet loss on certain prefixes (IP ranges) in DK DC-1. This may be another small scale DOS which is not being properly mitigated. We are currently investigating this incident.

Network issue in DK DC
  • Resolved
    UTC
    Resolved

    This incident has been resolved. We apologize for the inconvenience this evening.!

  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified

    NOC team is still working on this. We are unsure on this side why the fix is taking so long, especially given our pretty good DOS protection - this may be some sort of novel/interesting attack we haven't seen before. We will update once our NOC gives us information.

  • Monitoring
    UTC
    Monitoring

    Still seeing up to 90% packet loss from some regions, depending on the route the traffic takes to reach us. It's a single 10Gbit line which is currently overloaded. Our NOC team is looking at blocking the source of the DOS (which should be automatic, not sure why that is not happening) or shifting the traffic to our healthy 100Gbit lines. We will hopefully have this resolved soon.

  • Identified
    UTC
    Identified

    This is looking like a DOS event. We are investigating why auto-mitigation failed us.

  • Investigating
    UTC
    Investigating

    Something is happening with our network at this time. We are currently investigating this incident.

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

    The host needs a reboot, there will be 5-10 minutes of downtime. Sorry for the inconvenience.

Another LXD-based host needs a reboot as the system became unresponsive
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Identified
    UTC
    Identified

    The host will be rebooted now. There will be 5-10 minutes of downtime.

An lxd-based host needs a reboot
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Identified
    UTC
    Identified

    The host needs a reboot. Server will see a 5-10 minutes of downtime. Apologies for the inconvenience.

Nov 2025

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

    One of our lxd-based host needs a reboot as it has become unresponsive.

A single host needs a reboot (legacy lxd-based host)
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Identified
    UTC
    Identified

    The host needs reboot. The container VPSes will see a 5-10 minutes of downtime.

One of our EPYC system is down
  • Resolved
    UTC
    Resolved

    This incident has been resolved. Sorry for the inconvenience.

  • Identified
    UTC
    Identified

    One of our EPYC system is down and hence VPSes will be unreachable. We are investigating this.

Oct 2025

Issue with lxd-based Host
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Identified
    UTC
    Identified

    The server needs a reboot. Expect 5-10 minutes of downtime. Apologies for the inconvenience.

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

    The host needs a reboot. There will be 5-10 minutes fo downtime. Sorry for any inconvenience caused

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

    One of our legacy container-based host needs a reboot (system is frozen) for proper functioning. There will be dowtime for few minutes.

    Apologies for the inconvenience.

Fiber optics and cable replacement
  • Completed
    October 11, 2025 at 5:22 PMUTC
    Completed
    October 11, 2025 at 5:22 PMUTC

    Maintenance has completed successfully. No impact to customer workloads was seen.

  • In progress
    October 11, 2025 at 5:15 PMUTC
    In progress
    October 11, 2025 at 5:15 PMUTC
    Maintenance is now in progress
  • Planned
    October 11, 2025 at 5:15 PMUTC
    Planned
    October 11, 2025 at 5:15 PMUTC

    Our NOC team has identified and issue with a flapping link and high CRC errors rate for the past 2 days. We will attempt to fix the issue by changing optics.

Issue with lxd-based Host
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Identified
    UTC
    Identified

    The server needs a reboot. Expect 5-10 minutes of downtime. Apologies for the inconvenience.

Oct 2025 to Dec 2025

Next