Workspot Outage History

Workspot is up right now

Workspot had 11 outages in the last 2 years totaling 1084h 52m of downtime — averaging 0.5 incidents per month.

There were 11 Workspot outages since May 29, 2025 totaling 1084h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.workspot.com

Notice May 5, 2026

Intermittent Restarts of Control Dynos

Detected by Pingoru
May 05, 2026, 12:08 PM UTC
Resolved
May 06, 2026, 04:32 AM UTC
Duration
16h 24m
Affected: Workspot Control
Timeline · 8 updates
  1. investigating May 05, 2026, 12:08 PM UTC

    We are observing intermittent dynos restarts reported by our platform provider, Heroku. At this time, we have not observed any application downtime. This activity is not related to any security incident. Our engineering team is actively investigating the issue. We will continue to provide updates as we learn more.

  2. investigating May 05, 2026, 12:35 PM UTC

    We have not observed any dyno restarts in the last 30 minutes. The engineering team is closely monitoring the environment and continues to investigate the underlying cause of the earlier dyno restarts. We will provide further updates as more information becomes available.

  3. investigating May 05, 2026, 01:06 PM UTC

    We have not observed any dyno restarts since the incident was reported, nor any application downtime. The engineering team continues to monitor the environment closely and is investigating the underlying cause of the earlier dyno restarts. We will provide further updates as more information becomes available.

  4. investigating May 05, 2026, 01:37 PM UTC

    No new issues have been observed. As a mitigation measure, the engineering team has implemented changes to improve platform stability. The team is closely monitoring the environment and continues to investigate the underlying cause of the earlier instability. The next update will be shared in one hour. We will provide further updates sooner if there are any changes.

  5. investigating May 05, 2026, 02:33 PM UTC

    There are no new updates at this time. The platform remains stable, and the engineering team continues to monitor the environment. If there are no changes, the next update will be shared in the next 2 hours. We will provide further updates sooner if needed.

  6. investigating May 05, 2026, 04:33 PM UTC

    No new update at this time. The platform remains stable, and the engineering team continues to actively monitor the environment. If there are no changes, the next update will be shared in the next two hours. We will provide an update sooner if there is any change in status.

  7. investigating May 05, 2026, 07:01 PM UTC

    There are no new updates at this time. The platform remains stable, and the engineering team continues to monitor the environment. If there are no changes, the next update will be shared in the next 2 hours. We will provide further updates sooner if needed.

  8. resolved May 06, 2026, 04:32 AM UTC

    Workspot investigated the restart of the Control Dynos reported by our platform provider. The system is stable and we are closing the incident on status, but continuing to actively monitor and investigate the root cause. We will share the RCA and updates as soon as they become available. Thank you.

Read the full incident report →

Notice March 20, 2026

Workspot Control Reported Five Minutes Downtime

Detected by Pingoru
Mar 20, 2026, 06:09 PM UTC
Resolved
Mar 24, 2026, 05:17 AM UTC
Duration
3d 11h
Affected: Workspot Control
Timeline · 2 updates
  1. investigating Mar 20, 2026, 06:09 PM UTC

    Pingdom reported production was down for Five minutes(4:08 PM UTC - 4:13 PM UTC). There was a 5 minute intermittent service outage by a subservice provider resetting their system. The service automatically recovered. We will share the RCA once we receive from the subservice provider.

  2. resolved Mar 24, 2026, 05:17 AM UTC

    The system has been stable and functioning normally for the past 48 hours. Our internal investigation found no application-level anomalies. We are closing this incident while the root cause analysis (RCA) from our infrastructure provider is still ongoing. We will share updates as soon as they become available. Thank you for your patience.

Read the full incident report →

Major November 14, 2025

Workspot Control Login Instability

Detected by Pingoru
Nov 14, 2025, 03:57 PM UTC
Resolved
Nov 14, 2025, 06:30 PM UTC
Duration
2h 33m
Affected: Workspot Control
Timeline · 3 updates
  1. investigating Nov 14, 2025, 03:57 PM UTC

    We are currently experiencing intermittent issues with Workspot Control logins and non-persistent VM logins. Our team is actively investigating the issue and has escalated the matter by raising a priority ticket with the platform vendor. We are working closely with them to resolve this as quickly as possible. Further updates will be shared as soon as more information becomes available.

  2. monitoring Nov 14, 2025, 05:20 PM UTC

    Update: We are seeing improvement in both Workspot Control logins and non-persistent VM logins. At this time, we are closely monitoring the situation to ensure stability. Our investigation is ongoing, and we will share additional details as they become available.

  3. resolved Nov 14, 2025, 06:30 PM UTC

    This issue has been resolved, and customers can now log in to Workspot Control and access non-persistent VMs without any issues. The platform is stable, and normal operations have resumed. We will continue to monitor the environment to ensure stability. We will share a post-incident summary once our investigation ends and relevant details are available.

Read the full incident report →

Notice June 12, 2025

GCP Service Alert

Detected by Pingoru
Jun 12, 2025, 07:10 PM UTC
Resolved
Jun 12, 2025, 09:03 PM UTC
Duration
1h 52m
Timeline · 6 updates
  1. identified Jun 12, 2025, 07:10 PM UTC

    GCP is reporting 11:46 PDT "Multiple GCP products are experiencing impact due to Identity and Access Management Service Issue". https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  2. monitoring Jun 12, 2025, 07:15 PM UTC

    GCP update 12:09 PDT "Our engineers are continuing to mitigate the issue and we have confirmation that the issue is recovered in some locations."

  3. monitoring Jun 12, 2025, 07:32 PM UTC

    GCP: 12:30 PDT All locations except us-central1 have fully recovered. us-central1 is mostly recovered. We do not have an ETA for full recovery in us-central1.

  4. monitoring Jun 12, 2025, 07:44 PM UTC

    GCP 1241 PDT: "Our engineers have identified the root cause and have applied appropriate mitigations. While our engineers have confirmed that the underlying dependency is recovered in all locations except us-central1, we are aware that customers are still experiencing varying degrees of impact on individual google cloud products. All the respective engineering teams are actively engaged and working on service recovery. We do not have an ETA for full service recovery."

  5. monitoring Jun 12, 2025, 08:19 PM UTC

    GCP 13:16 PDT We have identified the root cause and applied appropriate mitigations. Our infrastructure has recovered in all regions except us-central1.

  6. resolved Jun 12, 2025, 09:03 PM UTC

    GCP 14:00 PDT We have implemented mitigation for the issue in us-central1 and multi-region/us and we are seeing signs of recovery. Please see GCP's status page for more details. https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

Read the full incident report →