2Captcha Outage History
10 incidents recorded over the last 365 days, 10 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.
Every Recorded 2Captcha Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 28, 2026 | Heavy DDoSEverything is up and running | 3 min | Resolved |
| Apr 22, 2026 | API outageThe incident has been fixed | -10 min | Resolved |
| Feb 25, 2026 | Major fault on datacenterThe issue has been fixed. | -13 min | Resolved |
| Feb 2, 2026 | Proxy service outageThe issue has been fixed | -1364 min | Resolved |
| Jan 30, 2026 | Proxy service outageAll endpoints has been restored and are operational. | -1498 min | Resolved |
| Jan 24, 2026 | Proxy service issueThere was an issue preventing new proxy service user generation. It has been fixed | -28 min | Resolved |
| Jan 22, 2026 | DB maintenance followupThe maintenance is finally over | -191 min | Resolved |
| Jan 22, 2026 | DB maintenanceThe incident has been resolved within 70 minutes | -369 min | Resolved |
| Dec 8, 2025 | Proxy server changeThe server has been successfully changed within 100 minutes | 0 min | Resolved |
| Nov 20, 2025 | Backend urgent maintenanceResolved | -201 min | Resolved |
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 2Captcha 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 2Captcha 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 2Captcha 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 2Captcha outage in this window ran 3 min, against a mean recovery of 2 min. If you depend on 2Captcha 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.