Canary Outage History

Canary is up right now

Canary had 1 outage in the last 2 years totaling 3h 1m of downtime — averaging 0 incidents per month.

There was 1 Canary outage since October 20, 2025 totaling 3h 1m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.canary.is

Minor October 20, 2025

Amazon Web Services Outage

Detected by Pingoru
Oct 20, 2025, 07:08 PM UTC
Resolved
Oct 20, 2025, 10:10 PM UTC
Duration
3h 1m
Affected: Canary ServiceCanary App
Timeline · 4 updates
  1. investigating Oct 20, 2025, 07:08 PM UTC

    Canary services are currently impacted by the ongoing Amazon Web Services outage affecting businesses worldwide. This has unfortunately caused some Canary devices to fall offline or not function as intended. We are actively working to address these issues as quickly as possible. We will continue to post updates here as progress is made.

  2. identified Oct 20, 2025, 07:16 PM UTC

    Canary services are currently impacted by the ongoing Amazon Web Services outage affecting businesses worldwide. This has unfortunately caused some Canary devices to fall offline or not function as intended. We are actively working to address these issues as quickly as possible. We will continue to post updates here as progress is made.

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

    We are continuing to monitor the status of the Amazon Web Services incident, which is impacting a subset of Canary devices. We have started to see an improvement to our impacted services. We will continue to monitor, and will post further updates here as we receive them. We sincerely appreciate your patience and understanding as we continue to work through this to return service to all Canary devices.

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

    All Canary services that were being impacted by the Amazon Web Services incident have now been restored. If you are continuing to experience any issues, please contact our support team via [email protected]

Read the full incident report →