User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
copper.com · Productivity
Is Copper down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → copper.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 133 ms · 5 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 07:00 | 0 | 0.0 | 73 ms | 0 |
| 07:15 | 0 | 0.0 | 72 ms | 0 |
| 07:30 | 0 | 0.0 | 181 ms | 0 |
| 07:45 | 0 | 0.0 | 97 ms | 0 |
| 08:00 | 0 | 0.0 | 155 ms | 0 |
| 08:15 | 0 | 0.0 | 226 ms | 0 |
| 08:30 | 0 | 0.0 | 115 ms | 0 |
| 08:45 | 0 | 0.0 | 130 ms | 0 |
| 09:00 | 0 | 0.0 | 141 ms | 0 |
| 09:15 | 0 | 0.0 | 129 ms | 0 |
| 09:30 | 0 | 0.0 | 111 ms | 0 |
| 09:45 | 0 | 0.0 | 118 ms | 0 |
| 10:00 | 0 | 0.0 | 83 ms | 0 |
| 10:15 | 0 | 0.0 | 86 ms | 0 |
| 10:30 | 0 | 0.0 | 115 ms | 0 |
| 10:45 | 0 | 0.0 | 145 ms | 0 |
| 11:00 | 0 | 0.0 | 223 ms | 0 |
| 11:15 | 0 | 0.0 | 88 ms | 0 |
| 11:30 | 0 | 0.0 | 119 ms | 0 |
| 11:45 | 0 | 0.0 | 89 ms | 0 |
| 12:00 | 0 | 0.0 | 142 ms | 0 |
| 12:15 | 0 | 0.0 | 103 ms | 0 |
| 12:30 | 0 | 0.0 | 274 ms | 0 |
| 12:45 | 0 | 0.0 | 96 ms | 0 |
| 13:00 | 0 | 0.0 | 103 ms | 0 |
| 13:15 | 0 | 0.0 | 102 ms | 0 |
| 13:30 | 0 | 0.0 | 244 ms | 0 |
| 13:45 | 0 | 0.0 | 98 ms | 0 |
| 14:00 | 0 | 0.0 | 238 ms | 0 |
| 14:15 | 0 | 0.0 | 95 ms | 0 |
| 14:30 | 0 | 0.0 | 128 ms | 0 |
| 14:45 | 0 | 0.0 | 99 ms | 0 |
| 15:00 | 0 | 0.0 | 195 ms | 0 |
| 15:15 | 0 | 0.0 | 140 ms | 0 |
| 15:30 | 0 | 0.0 | 101 ms | 0 |
| 15:45 | 0 | 0.0 | 97 ms | 0 |
| 16:00 | 0 | 0.0 | 187 ms | 0 |
| 16:15 | 0 | 0.0 | 77 ms | 0 |
| 16:30 | 0 | 0.0 | 103 ms | 0 |
| 16:45 | 0 | 0.0 | 182 ms | 0 |
| 17:00 | 0 | 0.0 | 245 ms | 0 |
| 17:15 | 0 | 0.0 | 92 ms | 0 |
| 17:30 | 0 | 0.0 | 84 ms | 0 |
| 17:45 | 0 | 0.0 | 167 ms | 0 |
| 18:00 | 0 | 0.0 | 194 ms | 0 |
| 18:15 | 0 | 0.0 | 122 ms | 0 |
| 18:30 | 0 | 0.0 | 95 ms | 0 |
| 18:45 | 0 | 0.0 | 112 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Copper status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Copper yet. Outages of 10 minutes or more get their own page here.
Having trouble with Copper?
One report per service every 10 minutes from this network. No account.
Follow Copper
Get an email when Copper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Copper alerts to Slack, Discord or a webhook — free.
Questions
Is Copper down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Copper not working for me but the status is fine. What now?
If Copper is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Copper's side.
How does Damn is it down decide Copper's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Copper checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.