depthfirst Outage History

16 incidents recorded over the last 365 days, 16 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 depthfirst status99.91% uptime history

Every Recorded depthfirst Incident

depthfirst incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 30, 2026Webapp Experiencing 503 ErrorsNo errors in the last hour. Resolved.1h 2mResolved
Oct 13, 2026Secrets page returning 400 errorsIssue resolved57 minResolved
Sep 29, 2026depthfirst Platform UnavailableIssue was identified as a problematic release impacting database queries. Change was rolled back and impacted components are recovered.9 minResolved
Sep 28, 2026Security Reviewer Reviews DegradedJob success rate and latency normalized.1h 4mResolved
Sep 20, 2026Degraded Security Reviewer ReviewsWarm pool scaled up1h 18mResolved
Sep 3, 2026AWS STS Outage Impacting Platform OperationsNo issues observed.1h 46mResolved
May 20, 2026Code Scanning DegradationDeployment configuration mismatch resolved. Confirming new Security Reviewer reviews and Code scans are completing as expected.38 minResolved
May 1, 2026Elevated Rate of Security Reviewer ErrorsSecurity Reviewer error rates recovered. Originally caused by database availability issues that are since resolved.21 minResolved
Apr 13, 2026Partial Errors for Security Reviewer and Code ScansCode Scan error rates normalized56 minResolved
Mar 10, 2026Code Deep Scan DegradationCode Deep Scan Error Rate Recovered. Only select customers affected. Comms sent to any parties affected.2h 26mResolved
Mar 10, 2026Elevated Rate of Security Reviewer ErrorsError Rates subsided. Security Reviewer fully operational.46 minResolved
Feb 9, 2026High Error Rate For Security ReviewerWe observed full recovery on recent PR Reviews. We will continue to closely monitor40 minResolved
Jan 21, 2026Security Reviewer partial outageFully mitigated32 minResolved
Jan 16, 2026Security Reviewer Elevated Error RateSecurity Reviewer Error Rates Recovered57 minResolved
Jan 6, 2026Security Reviewer DegradationThe issue has been identified as a misconfiguration in a regular config rollout. The misconfiguration was quickly detected by our monitoring systems and has been resolved. Security Reviewer is fully operational.13 minResolved
Dec 10, 2025Elevated Rate of Security Reviewer FailuresAll affected components operational at this time.5 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 depthfirst 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 depthfirst 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 depthfirst 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 depthfirst outage in this window ran 2h 26m, against a mean recovery of 52 min. If you depend on depthfirst 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.