Octopus Smart Signage Outage History

Started Sep 23, 2026, 06:44 AM UTC· resolved Sep 23, 2026, 06:48 AM UTC

1. identified Sep 23, 2026, 06:44 AM UTC

   Following a routine deployment at 06:40 UTC, the payment service failed to start within its start-up window and became unavailable. Payment requests made during this period will fail. Other services are unaffected. We have identified the cause and the service is being restarted.

2. resolved Sep 23, 2026, 06:48 AM UTC

   The payment service was restored at 06:48 UTC and is operating normally. Total impact was approximately eight minutes. Payments attempted during the outage were not processed and can be retried; no data was lost. We are extending the container start-up limit and reviewing our deployment process to prevent a recurrence.

Read the full incident report →

Started Aug 18, 2026, 01:19 PM UTC· resolved Aug 19, 2026, 07:36 AM UTC

1. investigating Aug 18, 2026, 01:19 PM UTC

   DEMO

Read the full incident report →

Started Jul 29, 2026, 05:44 AM UTC· resolved Aug 10, 2026, 06:33 AM UTC

1. investigating Jul 29, 2026, 05:44 AM UTC

   We are currently investigating an issue affecting our reporting service. All report types — including signage reports and video analytics reports — may fail to load or generate. Report data continues to be collected in the background and will be available once the issue is resolved. All other panel features are working normally, and content playback on screens is not affected. Our team is actively working on this. We will share an update as soon as we have more information. We apologize for any inconvenience.

Read the full incident report →

Started Jul 29, 2026, 05:43 AM UTC· resolved Aug 10, 2026, 06:33 AM UTC

1. investigating Jul 29, 2026, 05:43 AM UTC

   We are currently investigating an issue with how command results are displayed in the panel. Commands sent to devices remain in "In Progress" status and their final results are not shown, even though the commands are received and executed by the devices as expected. Sending commands to screens and accessing your devices are not affected, and content playback continues without interruption. Our team is actively working on this. We will share an update as soon as we have more information. We apologize for any inconvenience.

Read the full incident report →

Started Jul 28, 2026, 02:01 PM UTC· resolved Aug 10, 2026, 06:33 AM UTC

1. investigating Jul 28, 2026, 10:30 AM UTC

   We are currently investigating an issue with our email service. Outgoing emails — including notifications, ticket updates, and system alerts — may be delayed or not delivered. The panel and all other features are working normally, and content playback on screens is not affected. We will share an update as soon as we have more information. We apologize for any inconvenience.

2. identified Jul 28, 2026, 11:05 AM UTC

   We have identified the root cause of the issue affecting email delivery. The problem originates from our third-party email service provider, and outgoing emails — including notifications, ticket updates, password resets, and system alerts — are currently not being delivered. Our team is migrating email delivery to our own mail infrastructure to restore service as quickly as possible. Emails sent during this period may need to be re-triggered once the migration is complete. The panel and all other features are working normally, and content playback on screens is not affected. We will share an update as soon as the migration is complete. We apologize for any inconvenience.

3. monitoring Jul 28, 2026, 02:01 PM UTC

   Email delivery has been restored. Outgoing emails — including notifications, ticket updates, password resets, and system alerts — are now being sent through our own mail infrastructure and are being delivered as expected. If you were expecting an email during the outage and did not receive it, please re-trigger the action (for example, request a new password reset link). We are continuing to monitor the system to ensure everything remains stable. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jul 20, 2026, 01:47 PM UTC· resolved Jul 29, 2026, 11:26 AM UTC

1. investigating Jul 20, 2026, 01:47 PM UTC

   We are currently investigating a performance issue affecting plugin pages. Users may experience slow loading times when accessing these pages. Other panel features are not affected and can be used as usual. Content playback on screens is not impacted. We will share an update as soon as we have more information. We apologize for any inconvenience.

2. resolved Jul 29, 2026, 11:26 AM UTC

   This incident has been resolved. Plugin pages are now loading at normal speed, and all systems are operating as expected. Thank you for your patience, and we apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jul 20, 2026, 11:39 AM UTC· resolved Jul 20, 2026, 12:59 PM UTC

1. investigating Jul 20, 2026, 11:39 AM UTC

   We are currently investigating an issue affecting sub-account users under some customer accounts. Affected users may be unable to create new support tickets or view their existing tickets. Other panel features are not affected and can be used as usual. We will share an update as soon as we have more information. We apologize for any inconvenience.

2. identified Jul 20, 2026, 12:33 PM UTC

   We have identified the root cause of the issue preventing sub-account users under some customer accounts from creating or viewing support tickets. Our team has started working on a fix. Other panel features are not affected and can be used as usual. We will share an update once the fix is deployed. We apologize for any inconvenience.

3. resolved Jul 20, 2026, 12:59 PM UTC

   This incident has been resolved. Sub-account users can now create and view support tickets as expected. All systems are operating normally. Thank you for your patience, and we apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jul 20, 2026, 06:21 AM UTC· resolved Jul 20, 2026, 05:00 PM UTC

1. investigating Jul 20, 2026, 06:21 AM UTC

   We are currently investigating an issue affecting device commands sent through the CMS. Commands dispatched to screens remain in "In Progress" status and their results are not being returned, even though they may have been executed on the device. Our team has identified the issue and is actively working on a fix. Content playback on screens is not affected. We will share an update as soon as the issue is resolved. We apologize for any inconvenience.

2. identified Jul 20, 2026, 06:32 AM UTC

   We have identified the root cause of the issue affecting device commands and have started working on a fix. During this period, you will not be able to see the final status of commands sent to screens — they will remain in "In Progress" status. However, you can continue using the panel as usual, including sending content to your devices. Content playback on screens is not affected. We will share an update once the issue is resolved. We apologize for any inconvenience.

3. monitoring Jul 20, 2026, 06:58 AM UTC

   The issue affecting device commands has been resolved. Commands sent to screens are now being processed normally and their results are returned as expected. We are continuing to monitor the system to ensure everything remains stable. We apologize for any inconvenience this may have caused.

4. resolved Jul 20, 2026, 05:00 PM UTC

   This incident has been resolved. Device commands are now being processed normally and their results are returned as expected. All systems are operating normally. Thank you for your patience, and we apologize for any inconvenience this may have caused.

Read the full incident report →

Started May 23, 2026, 09:24 AM UTC· resolved Jun 23, 2026, 06:11 AM UTC

1. investigating May 23, 2026, 09:24 AM UTC

   We are currently investigating reports of the octoservice.net main API server being unresponsive or experiencing significantly elevated response times. Status: Investigating Impact: API requests may fail or time out. Services depending on octoservice.net may be affected. We will provide an update as soon as we have more information.

2. monitoring May 23, 2026, 09:29 AM UTC

   The issue affecting the octoservice.net main API server has been resolved. Services are back to normal operation. Status: Monitoring We are continuing to monitor the system closely to ensure stability and prevent recurrence. We will confirm full resolution once the monitoring period is complete.

3. resolved Jun 23, 2026, 06:11 AM UTC

   Following a period of monitoring, we have confirmed that system performance and stability have returned to normal. No further impact is expected. We appreciate your patience and understanding while we worked to resolve this issue.

Read the full incident report →

Started May 09, 2026, 07:19 AM UTC· resolved May 09, 2026, 07:42 AM UTC

1. identified May 09, 2026, 07:19 AM UTC

   "Summary: The analytics server is currently experiencing high load, resulting in degraded response times. The root cause has been identified and a fix is actively being applied. Impact: Analytics services are responding slowly or may be intermittently unavailable for end users. Current Status: Issue identified. Mitigation in progress. Next Update: Will be provided once the fix has been deployed and the service is confirmed stable. "

2. monitoring May 09, 2026, 07:33 AM UTC

   "Status: Resolved — Monitoring The issue affecting the analytics server has been resolved. The fix has been successfully applied and the service is back to normal operation. The team is actively monitoring to ensure stability is maintained. No further action is required at this time. This incident will be closed once the monitoring period is complete. "

3. resolved May 09, 2026, 07:42 AM UTC

   "Status: Resolved ✓ The analytics server high load incident has been fully resolved. The fix was applied successfully, the service operated normally during the monitoring period, and no further issues were detected. This incident is now closed. "

Read the full incident report →

Started Mar 30, 2026, 11:27 AM UTC· resolved Apr 20, 2026, 04:38 AM UTC

1. investigating Mar 30, 2026, 11:27 AM UTC

   "Summary: A critical issue has been identified where users are being unexpectedly logged out of the CMS immediately upon uploading content to a folder. The session is being invalidated during the upload process, completely disrupting user operations. Current Status: The issue is currently under active investigation. The engineering team is analyzing the root cause, focusing on the relationship between the folder content upload mechanism and the CMS session management layer. Impact: All users attempting to upload content to folders via the CMS are experiencing forced session termination. This prevents any content upload operations from being completed and requires users to repeatedly re-authenticate, causing significant workflow disruption. Suspected Area: The session logout behavior appears to be triggered during or immediately after a folder content upload action. Root cause has not yet been confirmed. Next Steps: • Investigate session handling and token validation logic during file upload requests • Analyze server logs around the time of upload to identify session invalidation triggers • Check for potential CSRF token mismatches, auth middleware interference, or timeout misconfiguration • Reproduce the issue in a staging environment for controlled diagnosis ⚠️ This incident is actively being investigated. Further updates will follow as findings become available. "

2. resolved Apr 20, 2026, 04:38 AM UTC

   The issue causing users to be unexpectedly logged out of the CMS during folder content uploads has been resolved. Root Cause The session invalidation was triggered during the folder content upload process due to an interference in the auth middleware / CSRF token validation logic during file upload requests. Resolution The relevant session handling and token validation logic has been reviewed and corrected. The fix has been deployed and verified in the production environment. Verification Folder content uploads can now be completed successfully without session termination. Users no longer need to re-authenticate mid-operation. Impact Summary All users attempting to upload content to folders via the CMS were affected. Normal operations have been fully restored.

Read the full incident report →

Started Feb 24, 2026, 01:45 PM UTC· resolved Feb 24, 2026, 02:53 PM UTC

1. investigating Feb 24, 2026, 01:45 PM UTC

   We are currently experiencing an issue affecting device status monitoring within the CMS. At this time, screen connectivity statuses (online/offline) cannot be accurately tracked or displayed in the CMS dashboard. Our technical team is actively investigating the root cause of the issue. There is no confirmed impact on content playback at this stage; the issue is limited to status visibility within the CMS. We will provide further updates as soon as more information becomes available.

2. resolved Feb 24, 2026, 02:53 PM UTC

   The issue affecting device status monitoring in the CMS has been resolved. Screen connectivity statuses (online/offline) are now being reported and displayed correctly in the CMS dashboard. Our technical team has implemented the necessary fixes to restore normal monitoring functionality. We will continue to monitor the system to ensure stability. Thank you for your patience and understanding.

Read the full incident report →

Started Feb 09, 2026, 08:23 AM UTC· resolved Feb 24, 2026, 01:43 PM UTC

1. identified Feb 09, 2026, 08:23 AM UTC

   LG display devices running Octopus software version 5.x do not send heartbeat data correctly to the CMS. Because of this issue, the CMS cannot reliably determine the actual connectivity status of these devices. As a result, affected LG displays may be shown as offline while they are actually online, or online while they are offline, which leads to inaccurate online/offline device counts in the CMS dashboard. This issue is specific to LG devices using Octopus software version 5.x and does not affect devices running other Octopus versions or different hardware brands.

2. resolved Feb 24, 2026, 01:43 PM UTC

   The issue affecting LG display devices running Octopus software version 5.x has been resolved. Previously, these devices were not sending heartbeat data correctly to the CMS, which caused inaccurate device connectivity status reporting. As a result, some LG displays were incorrectly shown as online or offline in the CMS dashboard. The heartbeat communication mechanism has been corrected, and device status reporting is now functioning as expected. This issue was limited to LG devices using Octopus software version 5.x. Devices running other Octopus versions or different hardware brands were not affected. We appreciate your patience during this process.

Read the full incident report →

Started Dec 22, 2025, 11:13 AM UTC· resolved Dec 22, 2025, 04:51 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 20, 2025, 08:53 PM UTC· resolved Dec 22, 2025, 04:51 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 15, 2025, 05:43 PM UTC· resolved Dec 16, 2025, 08:09 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 14, 2025, 08:25 AM UTC· resolved Nov 14, 2025, 09:05 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →