Dock Outage History

Dock is up right now

Dock had 2 outages in the last 2 years totaling 5h 38m of downtime — averaging 0.1 incidents per month.

There were 2 Dock outages since October 20, 2025 totaling 5h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dock.us

Minor February 24, 2026

Dock application experiencing issues

Detected by Pingoru
Feb 24, 2026, 03:55 PM UTC
Resolved
Feb 24, 2026, 04:15 PM UTC
Duration
20m
Affected: Web Application
Timeline · 3 updates
  1. investigating Feb 24, 2026, 03:55 PM UTC

    Dock's engineering team is currently investigating the issue

  2. identified Feb 24, 2026, 04:03 PM UTC

    The issue has been identified and the engineering team is working to fix. Customers should start to see improved performance.

  3. resolved Feb 24, 2026, 04:15 PM UTC

    The incident has been resolved

Read the full incident report →

Major October 20, 2025

AWS Outage

Detected by Pingoru
Oct 20, 2025, 03:50 PM UTC
Resolved
Oct 20, 2025, 09:09 PM UTC
Duration
5h 18m
Affected: Web Application
Timeline · 4 updates
  1. investigating Oct 20, 2025, 03:50 PM UTC

    Dock is impacted by the widespread AWS outage. We are actively monitoring.

  2. monitoring Oct 20, 2025, 08:18 PM UTC

    We are continuing to monitor the ongoing AWS incident, which remains in a degraded state. At this time, our services are operating normally and we are not observing customer impact. We will remain vigilant and continue to monitor the situation closely until AWS confirms full resolution. If conditions change, we will provide further updates.

  3. monitoring Oct 20, 2025, 08:30 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 20, 2025, 09:09 PM UTC

    We have been closely monitoring the AWS incident and allowed for an observation period to ensure stability. During this time, we have not experienced any degraded performance. Based on these results, we are now moving this incident to Resolved. Thank you for your patience while we monitored this issue.

Read the full incident report →