Screenly Outage History

Screenly is up right now

Screenly had 8 outages in the last 2 years totaling 102h 12m of downtime — averaging 0.3 incidents per month.

There were 8 Screenly outages since July 17, 2024 totaling 102h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.screenly.io

Notice March 9, 2026

Investigating Service Disruptions (GCP)

Detected by Pingoru
Mar 09, 2026, 02:25 PM UTC
Resolved
Mar 09, 2026, 06:00 PM UTC
Duration
3h 34m
Timeline · 4 updates
  1. investigating Mar 09, 2026, 02:25 PM UTC

    Our Engineering team is currently investigating reports of connectivity issues and performance degradation resulting from our GCP cluster. We will provide another update as soon as more information is available.

  2. investigating Mar 09, 2026, 04:45 PM UTC

    Service Update: Investigation Ongoing and Partial Recovery. Our team is working closely with our cloud provider's support team to resolve the infrastructure issue. Impact: Logins & Updates: You may currently experience issues logging into the dashboard or pushing new content updates to your screens. Your Screens: Active players will continue to render content seamlessly and your current playlists will remain on-screen without interruption.

  3. monitoring Mar 09, 2026, 04:55 PM UTC

    Services are stabilizing. If you were previously unable to log in or update your content, please refresh your browser and try again.

  4. resolved Mar 09, 2026, 06:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Cloudflare Global Network Experiencing Issues

Detected by Pingoru
Nov 18, 2025, 12:03 PM UTC
Resolved
Nov 18, 2025, 04:48 PM UTC
Duration
4h 44m
Timeline · 2 updates
  1. investigating Nov 18, 2025, 12:03 PM UTC

    We are currently investigating reports of issues related to Cloudflare's global network. Cloudflare is a key service provider for many of our operations, and this degradation may intermittently affect the performance and availability of certain Screenly services. We are closely monitoring the situation and Cloudflare's own status updates. We will provide another update as soon as we have more information or the issue is resolved.

  2. resolved Nov 18, 2025, 04:48 PM UTC

    We will continue to monitor the situation closely. See www.cloudflarestatus.com for the latest updates directly from the Cloudflare.

Read the full incident report →

Major October 13, 2025

Screenly Player Max Players Not Displaying Content

Detected by Pingoru
Oct 13, 2025, 04:37 PM UTC
Resolved
Oct 14, 2025, 06:25 AM UTC
Duration
13h 47m
Timeline · 4 updates
  1. investigating Oct 13, 2025, 07:17 PM UTC

    We are currently investigating an issue that is preventing a portion of our Max Players from displaying content. This is currently being reported as either an all black screen or a black screen with error messages showing.

  2. identified Oct 13, 2025, 07:51 PM UTC

    Our team has identified the issue as being related to an upstream update sent out from our OS provider (Canonical). A fix is being tested for release to rollback the update.

  3. monitoring Oct 13, 2025, 07:56 PM UTC

    A fix has been released to rollback the update from our upstream provider (Canonical) and hold all updates. We are monitoring to confirm the changes.

  4. resolved Oct 14, 2025, 01:33 PM UTC

    The issue has been resolved. A fix was successfully released to roll back the update from our upstream provider (Canonical). We will continue monitoring to ensure stability.

Read the full incident report →

Major July 21, 2025

We’re currently investigating an issue causing blank pages in the Screenly interface for some users.

Detected by Pingoru
Jul 21, 2025, 04:00 PM UTC
Resolved
Jul 21, 2025, 06:13 PM UTC
Duration
2h 12m
Affected: Marketing Site
Timeline · 4 updates
  1. investigating Jul 21, 2025, 04:21 PM UTC

    We are currently investigating this issue.

  2. identified Jul 21, 2025, 06:05 PM UTC

    Our developers have identified an issue related to a deployment earlier today, and the process of rolling back the update is in-progress.

  3. monitoring Jul 21, 2025, 06:08 PM UTC

    The update has now been rolled back, and we are seeing the normal operation of the web console return by refreshing the browser session.

  4. resolved Jul 21, 2025, 06:13 PM UTC

    This incident has now been resolved.

Read the full incident report →

Major June 12, 2025

We're currently investigating issues with logging into the web console and registering devices.

Detected by Pingoru
Jun 12, 2025, 06:13 PM UTC
Resolved
Jun 12, 2025, 10:29 PM UTC
Duration
4h 16m
Affected: Login PageDevice RegistrationAuthAPI v3
Timeline · 6 updates
  1. investigating Jun 12, 2025, 06:39 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 12, 2025, 07:14 PM UTC

    One of our cloud service providers, Google Cloud (GCP), has identified a major service outage affecting multiple GCP products and customers. This is currently being investigated by the Google Engineering team. Google's status page for the incident can be followed here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  3. identified Jun 12, 2025, 08:25 PM UTC

    Google's Engineering team has identified the root cause and began implementing mitigation and recovery processes. They have confirmed that the underlying dependency is recovered in all locations except us-central1, but noted that "many customers are still experiencing varying degrees of impact on individual google cloud products." The Google engineering teams are continuing to work on restoring service, and there is no ETA at this time. For the complete update, Google's status page for the incident can be followed here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  4. monitoring Jun 12, 2025, 09:15 PM UTC

    All Screenly production systems appear to be fully operational, however, we are monitoring to ensure there is no degradation of service. Google Engineers have also mitigated the issues within the us-central1 region, and expect full recovery within the next hour. For the latest update, Google's status page for the incident can be followed here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  5. monitoring Jun 12, 2025, 09:21 PM UTC

    All Screenly production systems appear to be fully operational, however, we are monitoring to ensure there is no degradation of service. Google Engineers have also mitigated the issues within the us-central1 region, and expect full recovery within the next hour. For the latest update, Google's status page for the incident can be followed here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

  6. resolved Jun 12, 2025, 10:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 17, 2024

Screens Showing QR and PIN Codes

Detected by Pingoru
Sep 17, 2024, 02:14 PM UTC
Resolved
Sep 19, 2024, 02:02 PM UTC
Duration
1d 23h
Timeline · 4 updates
  1. identified Sep 18, 2024, 05:19 PM UTC

    Over the past year, we’ve been focused on enhancing the security of our digital signage players to meet the highest compliance standards, including Zero Trust principles. While the transition has been smooth for the vast majority of our users, a small number of older devices encountered issues during the migration and did not fully integrate with our new implementation. This was identified early during our canary deployment this week. Upon discovering the problem, we immediately paused the rollout to limit its impact and reverted the release. We are committed to resolving this issue promptly and will be working directly with affected customers to ensure a swift resolution.

  2. identified Sep 18, 2024, 05:29 PM UTC

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

  3. identified Sep 18, 2024, 11:39 PM UTC

    We are continuing to work on a fix for this issue. For any affected customers, please reference our Help Center guide here.

  4. resolved Sep 19, 2024, 02:02 PM UTC

    All affected users have been contacted with detailed instructions on how to restore their screens. Please reference our Help Center guide here.

Read the full incident report →

Major August 5, 2024

Issues Logging In With Username/Password

Detected by Pingoru
Aug 05, 2024, 05:42 PM UTC
Resolved
Aug 05, 2024, 07:17 PM UTC
Duration
1h 34m
Affected: Login Page
Timeline · 4 updates
  1. investigating Aug 05, 2024, 05:53 PM UTC

    We are currently investigating reports of being unable to login using username and password. SSO logins (Sign in with Google/GitHub/Microsoft/SAML) appear to be unaffected at this time.

  2. identified Aug 05, 2024, 06:32 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 05, 2024, 06:38 PM UTC

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

  4. resolved Aug 05, 2024, 07:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 17, 2024

Multiple API Endpoints Issue

Detected by Pingoru
Jul 17, 2024, 03:23 PM UTC
Resolved
Jul 18, 2024, 03:37 PM UTC
Duration
1d
Timeline · 3 updates
  1. investigating Jul 17, 2024, 03:23 PM UTC

    Our team is currently investigating an issue affecting multiple API endpoints. Users may experience intermittent connectivity problems or errors when accessing our services. We are working diligently to identify the root cause and implement a solution quickly. This issue may affect all users trying to connect to our API services.

  2. investigating Jul 18, 2024, 03:36 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jul 18, 2024, 03:37 PM UTC

    This incident has been resolved.

Read the full incident report →