We continue to monitor our systems closely following the AWS thermal event. The situation appears to be stabilizing:
Pod restart frequency has decreased, and our systems are recovering as expected. BSN.cloud services remain fully operational with no impact to your workflows.
AWS Update: AWS has reported that the underlying thermal issue is beginning to resolve. We’re tracking their progress and will continue monitoring our infrastructure for any further activity.
We’ll maintain close observation over the next few hours and will provide another update if the situation changes. Thank you for your patience
Monitoring
We continue to monitor our systems closely following the AWS thermal event. The situation appears to be stabilizing:
Pod restart frequency has decreased, and our systems are recovering as expected. BSN.cloud services remain fully operational with no impact to your workflows.
AWS Update: AWS has reported that the underlying thermal issue is beginning to resolve. We’re tracking their progress and will continue monitoring our infrastructure for any further activity.
We’ll maintain close observation over the next few hours and will provide another update if the situation changes. Thank you for your patience
Investigating
We’re currently investigating an AWS thermal event affecting our infrastructure in USE-1. This is causing periodic pod restarts across our platform as AWS performs thermal management on the affected hardware.
Our Kubernetes cluster is actively managing these restarts, and BSN.cloud services remain operational. You may experience brief latency spikes or momentary connection resets as affected pods cycle, but core functionality is maintained.
What we’re doing:
• Actively monitoring pod restart patterns and cluster health
• Working with AWS on the underlying thermal issue
• Standing by to escalate or migrate workloads if operational impact increases
