Resolved after 2 hours 44 minutes, on April 28, 2025.
The system is back to normal. ### Initial Technical Analysis * A sudden increase in ingress traffic caused one of the OLAP DB to throttle new write and read requests * That caused an accumulation of backlog tasks - an autoscaling kicked off but couldn't cope with the backlog * Increasing the infrastructure capacity resolved the issue. ### Impact The issue affected test results reported between April 25 \~4:30pm-7:30pm GMT * runs could be marked as timed out * test results reporting is missing or delayed for affected runs * CI jobs displaying warnings and connectivity error.
Update timeline
- investigating Apr 28, 2025, 05:11 PM UTC
We are currently investigating this incident..
- identified Apr 28, 2025, 06:46 PM UTC
The issue is caused by an increased memory pressure on an infrastructure component. We are performing an adjustment to it capacity and taking care of the pending tasks..
- resolved Apr 28, 2025, 07:56 PM UTC
The system is back to normal. ### Initial Technical Analysis * A sudden increase in ingress traffic caused one of the OLAP DB to throttle new write and read requests * That caused an accumulation of backlog tasks - an autoscaling kicked off but couldn't cope with the backlog * Increasing the infrastructure capacity resolved the issue. ### Impact The issue affected test results reported between April 25 \~4:30pm-7:30pm GMT * runs could be marked as timed out * test results reporting is missing or delayed for affected runs * CI jobs displaying warnings and connectivity error.
Your product runs on more than Currents
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services