GumGum had 12 outages in the last 2 years totaling 60h 30m of downtime — averaging 0.5 incidents per month.
There were 12 GumGum outages since June 1, 2024 totaling 60h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified an issue with the Contextual Platform that is causing delay in classification/segment data to clients.
The issue has been identified and a fixed has been implemented.
This incident has been resolved.
We are currently experiencing delays in classification processing on our platform. Our team is actively investigating the issue and working to identify the impacted pipelines. We will provide updates here, including details on the affected areas and timelines for resolution, as they become available. Thank you for your patience.
This issue has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing delays in classification processing on our platform. Our team is actively investigating the issue and working to identify the impacted pipelines. We will provide updates here, including details on the affected areas and timelines for resolution, as they become available. Thank you for your patience.
We see improvements in the video classification latency and are monitoring the applications.
We are now within normal latency limits for the video endpoint.
We're experiencing an elevated level of API errors and are currently looking into the issue.
This incident has been resolved.
We are currently experiencing delays in classification processing on our platform. Our team is actively investigating the issue and working to identify the impacted pipelines. We will provide updates here, including details on the affected areas and timelines for resolution, as they become available. Thank you for your patience.
We are facing increased classification latency due to an issue with one of our vendors. The issue has been identified and the cloud provider is working through a mitigation. For more information, please visit: https://health.aws.amazon.com/health/status.
We are still facing increased classification latencies as our cloud provider is working through a mitigation.
We are now within normal latency limits for the image endpoint and will keep monitoring the systems.
This incident has been resolved.
We are facing increased classification latency due to an issue with one of our vendors.
The issue has been identified and the cloud provider is working through a mitigation. For more information, please visit: https://health.aws.amazon.com/health/status.
We are still facing increased classification latencies as our cloud provider is working through a mitigation.
We are now within normal latency limits for the page endpoint.
We have identified an issue which is impacting the delivery of page, text and video data. This is impacting the page, text and video endpoints.
We have increased resources for our internal systems which require external network access. We are seeing a positive impact and we'll continue to monitor backlog processing. We still expect processing to be delayed for the next few hours.
This incident has been resolved.
We are currently monitoring the platform recovering from a networking outage. A fix has been deployed and we will update our status page once processing latencies are back to normal.
This incident has been resolved.
We have identified that one of our backend services is now currently experiencing delays in processing our backlog of messages. This is translating to high latency across Verity services, specifically for pages, text and video. We are increasing support to our affected system to help it recover and catch-up to our backlog.
We are continuing to investigate this issue.
We are seeing improvements to processing latency. We'll continue monitoring until we've seen consistent stability.
Processing latency is back to normal levels.
We are currently investigating this issue.
Our backend services have been manually scaled out to meet the extra demand to the platform. At the moment we're seeing improvements and we are catching up to our backlog of messages. You will still see some higher-than-normal-latency, but it will begin to get better soon.
We are continuing to monitor for any further issues.
No further issues are being observed and processing latencies are back to normal values.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and we are seeing improvement in the impacted service.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.