Skip to content

Outage tracker / Copper / In the US

Is Copper down in the US?

Vendor reports no incidentWhat Copper reports

Copper reports no incident on its status page.

As of the last successful poll, 2026-11-07 17:44 UTC.

Copper's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Copper at Nov 7, 2026, 6:13 PM UTC.

Over the last 24 hours we completed 263 checks from Ashburn and San Jose and 263 answered cleanly, 100.00% availability.

Of the 2 other regions we check Copper from, all 2 read checks passing right now.

Email me when Copper reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Copper's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing141 checks in 24h, 100.00%
San JoseChecks passing122 checks in 24h, 100.00%

Last checked Nov 7, 2026, 6:13 PM UTC.

Copper from Ashburn and San Jose over the last 30 days

Over the last 30 days, Copper answered our Ashburn probe in 1,428 ms on average, and 1 check in 20 took longer than 2,261 ms.

Over the last 30 days, Copper answered our San Jose probe in 1,562 ms on average, and 1 check in 20 took longer than 2,269 ms.

Ranked by average response time across the 4 cities we check Copper from, Ashburn 2nd, San Jose 3rd; Frankfurt was fastest at 979 ms and Tokyo slowest at 2,233 ms.

From Ashburn and San Jose we ran 1,295 checks of Copper in 6 days, and 1,295 answered cleanly: 100.00% availability.

Every one of those days was clean: not one failed check.

In Ashburn local time (EST), Copper was slowest around 4 PM, at 1,720 ms on average over the last 14 days, and quickest around 10 AM, at 1,080 ms.

Day (UTC)ChecksAvailabilityAverage response
Sat, Nov 7197100.00%1,237 ms
Fri, Nov 6250100.00%1,609 ms
Thu, Nov 5250100.00%1,607 ms
Wed, Nov 4250100.00%1,270 ms
Tue, Nov 3245100.00%1,510 ms
Mon, Nov 2103100.00%1,853 ms

Copper outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Copper outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Copper from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 116 checks
TokyoChecks passing100.00% of 67 checks

Other countries we check Copper from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Copper's public endpoints. They are not user reports, and they are not Copper's own status page.

See Copper's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Copper has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter