Squirrel Cloud Outage History

Squirrel Cloud is up right now

Squirrel Cloud had 2 outages in the last 2 years totaling 42h 25m of downtime, averaging 0.1 incidents per month.

There were 2 Squirrel Cloud outages since March 13, 2025 totaling 42h 25m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.squirrelcloud.com

Minor September 9, 2025

Outage in API service

Detected by Pingoru
Sep 09, 2025, 04:30 AM UTC
Resolved
Sep 10, 2025, 04:16 PM UTC
Duration
1d 11h
Affected: APIBoHFoH
Timeline · 4 updates
  1. identified Sep 09, 2025, 04:30 AM UTC

    Squirrel Cloud was unavailable for about 43 minutes starting 7:25 pm PST on 8th Sept 2025.

  2. identified Sep 09, 2025, 04:30 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Sep 09, 2025, 05:21 AM UTC

    The sites are operational now. We are working with Microsoft to identify the root cause.

  4. resolved Sep 10, 2025, 04:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 8, 2025

Service Disruption Due to Azure Maintenance – Central Canada Region

Detected by Pingoru
Jul 08, 2025, 02:18 PM UTC
Resolved
Jul 08, 2025, 08:56 PM UTC
Duration
6h 38m
Affected: APIBoHReportsFoH
Timeline · 3 updates
  1. identified Jul 08, 2025, 02:18 PM UTC

    We are currently experiencing intermittent service disruptions affecting our API due to unplanned critical infrastructure maintenance by Microsoft Azure in the Central Canada region. This is impacting service availability of our API, and our team is actively monitoring and restarting affected services as needed. During this time, please follow the procedures outlined in the Offline Mode option to continue operations to minimize disruption. If you encounter any additional challenges, please don't hesitate to contact our Support team for assistance. We apologize for the inconvenience and appreciate your understanding while Microsoft works to resolve the issue. We will continue to provide updates as more information becomes available.

  2. monitoring Jul 08, 2025, 06:30 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 08, 2025, 08:56 PM UTC

    This incident has been resolved.

Read the full incident report →