CoderPad Outage History

18 incidents recorded over the last 365 days, 18 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live CoderPad status100.00% uptime history

Every Recorded CoderPad Incident

CoderPad incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 27, 2026Degraded database performanceAn issue with an upstream cloud provider led to degraded systems performance of our APIs and interview rooms. Nominal performance was restored at 7:00 PM PDT.0 minResolved
Oct 21, 2026Degraded database performanceThis incident has been resolved.22h 23mResolved
Sep 1, 2026Screen Projects service interruptionEverything is confirmed to be operational45 minResolved
Aug 11, 2026Failure to load InterviewThis incident has been resolved.28 minResolved
Jul 31, 2026Pad Creation and Execution OutageWe are currently investigating issues with creating and editing pads and sandboxes.0 minResolved
Jul 29, 2026Code Execution OutageThis incident has been resolved.0 minResolved
Jul 21, 2026Code Execution OutageThis incident has been resolved.2h 36mResolved
Jul 3, 2026Interview pad execution failuresThe Interview execution service is now operational57 minResolved
Apr 27, 2026Code Execution OutageThis incident has been resolved.1h 47mResolved
Mar 12, 2026Anthropic Models Unavailable in AI AssistantThis incident has been resolved.5h 55mResolved
Feb 18, 2026Partial Interview app outageThis incident has been resolved.1h 45mResolved
Feb 18, 2026Transcription currently unavailable in InterviewThis incident has been resolved.2h 1mResolved
Feb 12, 2026Screen Projects service interruptionThis incident has been resolved.0 minResolved
Jan 26, 2026Screen Projects service interruptionThis incident has been resolved.1h 52mResolved
Jan 7, 2026Issues loading Screen Projects questionsThis incident has been resolved.12h 25mResolved
Nov 18, 2025Web requests failingOur upstream provider has resolved their incident and we have re-enabled affected services.5h 46mResolved
Nov 13, 2025Screen - Increased latency and timeoutsWe 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…-1040 minResolved
Nov 12, 2025Screen - Increased latency and timeoutsBetween 3:00 AM and 4:00 AM UTC, we observed an unusual increase in database latency, which led to higher CPU usage across multiple servers. This issue affected the Screen product only. The issue resolved itself…-855 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next CoderPad incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This CoderPad Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before CoderPad acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single CoderPad outage in this window ran 22h 23m, against a mean recovery of 3h 40m. If you depend on CoderPad in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.