Code Execution Outage
Timeline · 1 update
- resolved Jul 29, 2026, 09:43 AM UTC
This incident has been resolved.
CoderPad had 11 outages in the last 2 years totaling 56h 3m of downtime — averaging 0.5 incidents per month.
There were 11 CoderPad outages since September 2, 2025 totaling 56h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.
This incident has been resolved.
We are currently investigating a outage with the Interview code execution service.
We have identified the issue with the Interview code execution service and have implemented a fix. We are currently monitoring the service's health.
The Interview execution service is now operational
We are currently experiencing issues accessing AI models provided by Anthropic in our AI Assistant. Our team is actively investigating the issue and monitoring the situation. We will provide updates as soon as more information becomes available. Other AI providers and services remain unaffected.
This incident has been resolved.
We are currently investigating an issue that is preventing the CoderPad Interview application from loading.
After a brief issue with an upstream provider, the Interview application is functional. We are now monitoring the application's performance and availability.
This incident has been resolved.
The in-pad audio transcription is currently unavailable, due to upstream issues with a service provider. We're monitoring and will update once it's available again.
An update from the upstream service provider has restored transcription functionality. We are monitoring this fix and will update again once it has been fully resolved.
This incident has been resolved.
This incident has been resolved.
We are actively investigating issues with loading Screen Projects questions. Non-projects Screen tests are working as normal.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We continue to be impacted by an extended outage at one of our upstream providers. We are investigating further steps for mitigation.
We have taken steps to mitigate the upstream provider issue but are still identifying areas that are impacted. Mitigation steps are continuing.
We are seeing services start to recover and are continuing to monitor its progress.
We are seeing reduced error rates but continue to monitor the situation with our upstream provider.
Our upstream provider has resolved their incident and we have re-enabled affected services.
We observed an unusual increase in database latency, which led to higher CPU usage across multiple servers. This issue affected the Screen product only. We believe that we have identified the root cause and a patch will be deployed.
We have identified an issue with an upstream provider causing issues with transcription generation in Interview pads.
We are continuing to monitor the status of our upstream provider's fix for the issue.
We're experiencing some issues related to the global AWS service disruption (https://health.aws.amazon.com/health/status). Our team is closely monitoring AWS recovery effort to restore full functionality as soon as possible. CoderPad systems that may be impacted: - Interview transcription - Screen webcam proctoring - Platform login: login can be impacted by the AWS outage, please go to https://app.coderpad.io/login?skip_hydra=true to login
We still experiencing partial service disruptions due to ongoing issues with some of our upstream providers. While some providers are beginning to recover, full functionality has not yet been restored. We are closely monitoring the situation and will provide updates as our providers continue to recover.
This incident has been resolved.
We are currently experiencing delays in email delivery due to a temporary service disruption with our email infrastructure provider. This affects candidate invitations, user invitations, and report emails. Our team is actively working with our upstream provider to resolve the underlying issue. All queued emails will be automatically delivered once service is restored.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.