Cloudimage by Scaleflex Outage History
Cloudimage by Scaleflex is up right nowPingoru has recorded 19 incidents for Cloudimage by Scaleflex: 8 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 6 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 517 (0%) |
Incidents, newest first
Minor September 22, 2026 HUB Service Degradation 7m Hub
Started Sep 22, 2026, 01:34 PM UTC· resolved Sep 22, 2026, 01:41 PM UTC
- investigating Sep 22, 2026, 01:34 PM UTC
Dear Customers, We have identified an issue currently affecting image delivery through the HUB. Our teams are actively investigating the situation and working to restore normal service as quickly as possible. Impact: Image delivery may be unavailable or degraded Expected resolution: Service should return to normal shortly We will provide further updates as soon as more information becomes available. Regards, Scaleflex Incident team
- resolved Sep 22, 2026, 01:41 PM UTC
The root cause has been identified and was related to today’s release, which unintentionally impacted a health check used for HUB asset delivery. The health check has been removed, and image delivery has been restored to normal. Our teams are now reviewing the appropriate long-term solution to prevent recurrence. We apologise for the disruption and thank you for your patience. Regards, Scaleflex Incident team
Minor April 28, 2026 MM NEW SERVER VALIDATION 20260428-221447 4s Hub
Started Apr 28, 2026, 10:14 PM UTC· resolved Apr 28, 2026, 10:14 PM UTC
- investigating Apr 28, 2026, 10:14 PM UTC
New server validation create
- resolved Apr 28, 2026, 10:14 PM UTC
New server validation resolved
Minor April 25, 2026 MM TAG DAM TEST 6s API infrastructure
Started Apr 25, 2026, 03:15 PM UTC· resolved Apr 25, 2026, 03:15 PM UTC
- investigating Apr 25, 2026, 03:15 PM UTC
Testing DAM tag
- resolved Apr 25, 2026, 03:15 PM UTC
DAM tag test resolved
Minor April 25, 2026 MM TAG DMO TEST 12s Media Delivery CDN
Started Apr 25, 2026, 03:15 PM UTC· resolved Apr 25, 2026, 03:15 PM UTC
- investigating Apr 25, 2026, 03:15 PM UTC
Testing DMO tag
- resolved Apr 25, 2026, 03:15 PM UTC
DMO tag test resolved
Minor April 25, 2026 MM LIVE VXP TEST 1m Hub
Started Apr 25, 2026, 02:55 PM UTC· resolved Apr 25, 2026, 02:56 PM UTC
- investigating Apr 25, 2026, 02:55 PM UTC
Mattermost live validation for VXP Hub
- resolved Apr 25, 2026, 02:56 PM UTC
Mattermost live validation completed for VXP Hub
Minor April 25, 2026 TEST MM PREFIX VALIDATION 20260425-145411 2s Hub
Started Apr 25, 2026, 02:54 PM UTC· resolved Apr 25, 2026, 02:54 PM UTC
- investigating Apr 25, 2026, 02:54 PM UTC
prefix parser validation
- resolved Apr 25, 2026, 02:54 PM UTC
prefix parser validation resolved
Minor April 25, 2026 TEST VXP DEPLOY VALIDATION 20260425-142932 4s Hub
Started Apr 25, 2026, 02:29 PM UTC· resolved Apr 25, 2026, 02:29 PM UTC
- investigating Apr 25, 2026, 02:29 PM UTC
deployment validation create
- resolved Apr 25, 2026, 02:29 PM UTC
deployment validation resolved
Major March 6, 2026 Investigating Traffic Delivery Slowdowns (Elevated HTTP 429/439 Responses) 2d 5h Image Transformation Infrastructure
Started Mar 06, 2026, 03:33 PM UTC· resolved Mar 08, 2026, 08:36 PM UTC
- investigating Mar 06, 2026, 03:33 PM UTC
Dear All, Please accept our apologies, as our notification process via the status page did not operate as expected. At approximately 10:20 AM (UTC) on 06 March 2026, we began observing degraded traffic delivery performance, reflected by an elevated number of HTTP 429 and 439 responses. Our engineering team is currently investigating the situation and working to identify the root cause. We will continue to monitor the platform closely and are taking the necessary actions to restore normal delivery levels as quickly as possible. We will provide further updates as soon as additional information becomes available. Thank you for your patience and understanding. Regards, Scaleflex Incident Management team
- identified Mar 06, 2026, 05:05 PM UTC
Dear All, We would like to provide an update regarding the ongoing incident. The root cause has been identified as an intermittent hardware issue on our cache server, which made diagnosing the issue more challenging and contributed to the extended investigation time. Our team is currently implementing a temporary mitigation to reduce the impact while awaiting the replacement of the affected disk. We do not yet have a confirmed replacement timeline, but we are in active communication with our hosting partner, OVH, to resolve this as quickly as possible. We will continue to provide updates as more information becomes available, and we appreciate your patience and understanding. Regards, Scaleflex Incident Management team
- monitoring Mar 06, 2026, 06:30 PM UTC
Dear All, We are pleased to inform you that the workaround has been successfully implemented and traffic delivery is now returning to normal. The affected disk on our cache server has not yet been replaced; however, we are monitoring the situation closely to ensure continued stability. We will provide updates promptly if there are any changes or further developments. Thank you for your patience and understanding. Regards, Scaleflex Incident Management team
- resolved Mar 08, 2026, 08:36 PM UTC
Dear All, We have received confirmation from our infrastructure partner that the defective hardware has now been successfully replaced. As communicated earlier, the service had already been restored following our prior mitigation actions, and we have been closely monitoring system performance to ensure stability. All infrastructure components are now operating normally, and performance metrics confirm that the platform is fully back to its expected state. As the situation has been fully resolved and the infrastructure is back to normal operation, we are therefore closing this incident. Thank you for your patience and understanding throughout this process. Thank you for your patience and understanding. Regards, Scaleflex Incident Management team