Copyleaks's Services Outage History

8 incidents recorded over the last 365 days, 6 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 Copyleaks's Services status99.98% uptime history

Every Recorded Copyleaks's Services Incident

Copyleaks's Services incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 8, 2026Scheduled maintenance: Copyleaks US region – Sunday 8 November 2026Scheduled Maintenance2h 0mScheduled
Oct 26, 2026Scheduled maintenance: Copyleaks EU region – Monday 26 October 2026Scheduled Maintenance2h 0mScheduled
Oct 8, 2026Delayed scans in US datacenter2h 55mResolved
Sep 16, 2026Delayed scan processing in the US datacenter2h 5mResolved
Sep 1, 2026Delayed scan processing in the US datacenter1h 29mResolved
Aug 27, 2026Billing and subscription requests failing in US datacenter50 minResolved
Aug 26, 2026Delay on plagiarism scans2h 10mResolved
Aug 25, 2026Delays on some US plagiarism scans1h 55mResolved

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 Copyleaks's Services 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 Copyleaks's Services 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 Copyleaks's Services 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 Copyleaks's Services outage in this window ran 2h 55m, against a mean recovery of 1h 56m. If you depend on Copyleaks's Services 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.