Copper Outage History

11 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.

Every Recorded Copper Incident

Copper incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 24, 2026Copper Scheduled Maintenance - October 24, 2026Scheduled maintenance is still in progress. We will provide updates as necessary.8h 0mScheduled
Jun 27, 2026Copper Scheduled Maintenance - June 27, 2026The scheduled maintenance has been completed.8h 0mScheduled
Jun 9, 2026We are investigating an issue with the Google Sheets Add-on resulting in difficulty Importing DataAll issues are now resolved and all components are operational. If you still experience an issue after removing and re-installing the Chrome Extension or Google Sheets Add-on, please contact the Copper Support Team.148h 26mResolved
May 23, 2026Copper Scheduled Maintenance - May 23, 2026The scheduled maintenance has been completed.48h 0mScheduled
Feb 25, 2026Form Builder, Linked Pages, and some Integrations failing to operate as expected.This incident has been resolved.1h 40mResolved
Feb 19, 2026Custom Report data is delayedThis incident has been resolved.14h 25mResolved
Feb 18, 2026Custom Report data is delayedThis incident has been resolved.9h 26mResolved
Feb 9, 2026Custom Report data is delayedThis incident has been resolved.3h 50mResolved
Feb 3, 2026Some users are experiencing issues loading the appThis incident has been resolved.24 minResolved
Jan 10, 2026Copper Scheduled Maintenance - January 10, 2026The scheduled maintenance has been completed.8h 0mScheduled
Dec 6, 2025Copper Scheduled Maintenance - December 6, 2025The scheduled maintenance has been completed.8h 0mScheduled

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 Copper 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 Copper 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 Copper 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 Copper outage in this window ran 6d 4h, against a mean recovery of 23h 28m. If you depend on Copper 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.