- Detected by Pingoru
- Aug 28, 2026, 06:52 AM UTC
- Resolved
- Aug 28, 2026, 07:09 AM UTC
- Duration
- 16m
Affected: Device Management UI (EU)
Timeline · 2 updates
-
monitoring Aug 28, 2026, 06:52 AM UTC
We observed service degradation in the EU region from approximately 05:35 (UTC) to 05:55 (UTC) on August 28, 2026. Service functionality has since recovered, and we have not observed any further occurrences at this time. Our investigation indicates the issue may have been related to an underlying platform or database service degradation. We are continuing to monitor the environment to ensure service stability. At this time, services are operating normally. We will provide additional updates if the situation changes.
-
resolved Aug 28, 2026, 07:09 AM UTC
The service degradation affecting the EU region has been resolved. Services are operating normally, and no further issues have been observed. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 02:50 PM UTC
- Resolved
- Jul 13, 2026, 02:50 PM UTC
- Duration
- –
Affected: Device Management UI (CA)
Timeline · 1 update
-
resolved Jul 13, 2026, 02:50 PM UTC
We had received alerts indicating the possible failure on our device management cloud environment. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 07:35 AM UTC
- Resolved
- Jun 10, 2026, 01:05 AM UTC
- Duration
- 17h 29m
Affected: Device Management UI (CA)
Timeline · 2 updates
-
monitoring Jun 09, 2026, 07:35 AM UTC
An issue occurred for approximately 10 minutes during which the DeviceManagement top page was inaccessible. The cause has been identified, and we are currently working on a permanent fix. The issue has now been resolved, and we will continue to monitor the situation. Thank you for your understanding.
-
resolved Jun 10, 2026, 01:05 AM UTC
The root cause of this issue has been identified; however, a permanent fix is still in progress. No recurrence or significant impact has been observed to date, and given the sustained stability over a certain period, this incident will now be closed. We will continue working toward a permanent resolution. Thank you for your understanding and cooperation.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 06:49 AM UTC
- Resolved
- Jun 01, 2026, 08:36 AM UTC
- Duration
- 1h 47m
Affected: Device Management UI (AP)
Timeline · 2 updates
-
investigating Jun 01, 2026, 06:49 AM UTC
We are receiving a high number of alerts. The Device Management UI might be inaccessible. We are investigating the issue with the highest priority.
-
resolved Jun 01, 2026, 08:36 AM UTC
Following our investigation, we confirmed that this incident was a false positive and that there was no actual impact on service functionality. We are implementing measures to prevent recurrence and are reviewing our monitoring.
Read the full incident report →
- Detected by Pingoru
- May 31, 2026, 11:22 AM UTC
- Resolved
- Jun 16, 2026, 06:35 AM UTC
- Duration
- 15d 19h
Affected: Device Management UI (EU)
Timeline · 5 updates
-
investigating May 31, 2026, 11:22 AM UTC
We're experiencing an elevated level of timeout errors and are currently looking into the issue. Updates will follow on this channel.
-
identified Jun 01, 2026, 02:58 AM UTC
We have identified the cause of this issue. We are currently working on mitigation and recovery.
-
identified Jun 01, 2026, 08:01 AM UTC
The impact has been mitigated through a workaround. We will continue to monitor the situation while working on a permanent fix.
-
monitoring Jun 02, 2026, 02:09 PM UTC
While the root cause of the issue has not yet been fully determined, a workaround has been implemented, and the issue has not been observed since its application. As the system has remained stable with no impact observed, the status has been moved to Monitoring. We will continue to closely monitor the system and conduct further investigation, including detailed analysis of the underlying cause to prevent recurrence. Further updates will be provided as necessary. Thank you for your understanding.
-
resolved Jun 16, 2026, 06:35 AM UTC
The impact of this issue is no longer being observed, and service has remained stable for a sustained period. This incident is considered resolved and is now closed. Permanent corrective actions are still in progress. We will continue working to prevent recurrence.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2026, 05:00 PM UTC
- Resolved
- Apr 01, 2026, 05:10 AM UTC
- Duration
- 7d 12h
Affected: Device Management UI (EU)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 01:50 PM UTC
- Resolved
- Mar 04, 2026, 01:50 PM UTC
- Duration
- –
Affected: Device Management UI (NA)
Timeline · 2 updates
-
resolved Mar 04, 2026, 01:50 PM UTC
We had received alerts indicating the inaccessibility of the Device Management UI. The issue has already been restored. We will continue to investigate the root cause in the coming days.
-
postmortem Mar 18, 2026, 06:12 AM UTC
Incident Summary : A temporary instability occurred in part of the infrastructure responsible for traffic routing. This caused some internal monitoring checks to fail and triggered alerts. Customer-facing services continued to operate normally, as requests were automatically retried and routed to healthy components. As a result, end users may have experienced a slight, temporary increase in response time, but there was no service outage or functional impact. Root Cause : An unexpected autoscaling behavior caused some routing components to repeatedly restart, which intermittently affected internal health check responses. Resolution : As a mitigation measure, autoscaling for the affected components was adjusted on March 11. In addition, we are improving the monitoring configuration to better tolerate transient conditions and prevent unnecessary alerts in the future.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 12:43 AM UTC
- Resolved
- Jun 09, 2026, 09:12 AM UTC
- Duration
- 97d 8h
Affected: Device Management UI (EU)Device Management UI (AP)Device Management UI (NA)Device Management UI (CA)
Timeline · 3 updates
-
identified Mar 04, 2026, 12:43 AM UTC
Incident Summary In some environments, devices may appear as “No response” in CloudStream DM even though they are powered on. When this occurs, configuration tasks may not run or may be delayed. This issue happens when the device operation panel enters sleep mode. Root Cause This issue is caused by a sleep mode handling defect in specific versions of the CloudStream DM Agent, which prevents proper communication between the device and CloudStream. Resolution • Affected versions: CloudStream DM Agent v1.8.0 and v1.8.2 • Fix: The issue will be resolved in CloudStream DM Agent v1.8.3 Updates will be provided on this status page as they become available.
-
monitoring Mar 24, 2026, 12:07 PM UTC
Service Status The fix for the issue where devices could appear as “No response” has been completed. This issue is resolved in CloudStream DM Agent v1.8.3.
-
resolved Jun 09, 2026, 09:12 AM UTC
The issue has been resolved with the deployment of CloudStream DM Agent v1.8.3. No recurrence of the “No response” issue has been observed, and all services are operating normally. Monitoring is complete, and the incident has been closed.
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 10:33 AM UTC
- Resolved
- Mar 02, 2026, 10:33 AM UTC
- Duration
- –
Affected: Device Management UI (NA)
Timeline · 2 updates
-
resolved Mar 02, 2026, 10:33 AM UTC
We had received alerts indicating the possible failure on our device management cloud environment. The issue has already been restored. We will continue to investigate the root cause in the coming days.
-
postmortem Mar 18, 2026, 06:23 AM UTC
Please see the [link](https://cloudstream.status.ricoh.com/incidents/tzkbzfx64jst)[ ](https://cloudstream.status.ricoh.com/incidents/vwy37c4gtzrc)for Incident Summary, Root Cause, and Resolution.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 02:57 AM UTC
- Resolved
- Feb 02, 2026, 02:57 AM UTC
- Duration
- –
Affected: Device Management UI (EU)
Timeline · 1 update
-
resolved Feb 02, 2026, 02:57 AM UTC
We had received alerts indicating the possible failure on our device management cloud environment. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
- Detected by Pingoru
- Oct 31, 2025, 07:04 AM UTC
- Resolved
- Nov 07, 2025, 03:00 AM UTC
- Duration
- 6d 19h
Affected: Device Management UI (EU)
Timeline · 3 updates
-
investigating Oct 31, 2025, 07:04 AM UTC
We're experiencing an elevated level of timeout errors and are currently looking into the issue. Updates will follow on this channel. Incident Summary: We have identified an issue that is causing communication with the application to become unstable. As a result, some users may experience delays or failures when trying to connect or use certain features. Root Cause: The issue has been traced to a temporary overload in the system’s communication capacity. This overload is making it difficult to establish or maintain stable connections. Resolution: We are currently working to reduce communication load and improve system stability.
-
investigating Nov 04, 2025, 08:52 AM UTC
Planned Action: We will make urgent changes to internal system communication only in the EU environment to resolve the communication capacity issue. Please note that this urgent maintenance may cause a service outage lasting up to 1 hour, scheduled between 1:00 AM and 3:00 AM UTC on November 7. This outage will affect EU environments only. We apologize for the short notice, as this is an unplanned maintenance activity. Thank you for your understanding and cooperation.
-
resolved Nov 07, 2025, 03:00 AM UTC
The issue has been resolved. The services in the EU environment are operating normally.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 06:00 PM UTC
- Resolved
- Oct 21, 2025, 06:00 PM UTC
- Duration
- –
Affected: Device Management UI (EU)
Timeline · 1 update
-
resolved Oct 21, 2025, 06:00 PM UTC
We had received alerts indicating the inaccessibility of the Device Management UI. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 06:18 PM UTC
- Resolved
- Oct 02, 2025, 06:18 PM UTC
- Duration
- –
Affected: Device Management UI (NA)
Timeline · 1 update
-
resolved Oct 02, 2025, 06:18 PM UTC
We had received alerts indicating the possible failure on our device management cloud environment. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
Notice September 17, 2025 - Detected by Pingoru
- Sep 17, 2025, 12:13 AM UTC
- Resolved
- Sep 17, 2025, 12:13 AM UTC
- Duration
- –
Affected: Device Management UI (EU)
Timeline · 1 update
-
resolved Sep 17, 2025, 12:13 AM UTC
We had received alerts indicating the possible failure on our device management cloud environment. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
- Detected by Pingoru
- Aug 06, 2025, 03:35 PM UTC
- Resolved
- Aug 06, 2025, 03:35 PM UTC
- Duration
- –
Affected: Device Management UI (AP)
Timeline · 1 update
-
resolved Aug 06, 2025, 03:35 PM UTC
We had received alerts indicating the inaccessibility of the Device Management UI. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2025, 09:11 AM UTC
- Resolved
- Apr 24, 2026, 06:24 AM UTC
- Duration
- 273d 21h
Affected: Device Management UI (EU)
Timeline · 12 updates
Read the full incident report →
- Detected by Pingoru
- Nov 11, 2024, 05:16 PM UTC
- Resolved
- Nov 11, 2024, 05:16 PM UTC
- Duration
- –
Affected: Device Management UI (CA)
Timeline · 1 update
-
resolved Nov 11, 2024, 05:16 PM UTC
We had received alerts indicating the inaccessibility of the Device Management UI. The issue has already been restored. We will continue to investigate the root cause in the coming days.
Read the full incident report →
