User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
carbon3d.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 165 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 202 ms | 0 |
| Mon 22 | 0 | 0.0 | 37 ms | 0 |
| Tue 01 | 0 | 0.0 | 153 ms | 0 |
| Tue 03 | 0 | 0.0 | 131 ms | 0 |
| Tue 05 | 0 | 0.0 | 117 ms | 0 |
| Tue 07 | 0 | 0.0 | 59 ms | 0 |
| Tue 09 | 0 | 0.0 | 52 ms | 0 |
| Tue 11 | 0 | 0.0 | 162 ms | 0 |
| Tue 13 | 0 | 0.0 | 99 ms | 0 |
| Tue 16 | 0 | 0.0 | 131 ms | 0 |
| Tue 18 | 0 | 0.0 | 167 ms | 0 |
| Tue 20 | 0 | 0.0 | 234 ms | 0 |
| Tue 22 | 0 | 0.0 | 151 ms | 0 |
| Wed 00 | 0 | 0.0 | 148 ms | 0 |
| Wed 03 | 0 | 0.0 | 214 ms | 0 |
| Wed 05 | 0 | 0.0 | 75 ms | 0 |
| Wed 07 | 0 | 0.0 | 119 ms | 0 |
| Wed 09 | 0 | 0.0 | 169 ms | 0 |
| Wed 12 | 0 | 0.0 | 50 ms | 0 |
| Wed 14 | 0 | 0.0 | 123 ms | 0 |
| Wed 16 | 0 | 0.0 | 196 ms | 0 |
| Wed 18 | 0 | 0.0 | 97 ms | 0 |
| Wed 20 | 0 | 0.0 | 103 ms | 0 |
| Wed 22 | 0 | 0.0 | 130 ms | 0 |
| Thu 01 | 0 | 0.0 | 78 ms | 0 |
| Thu 03 | 0 | 0.0 | 187 ms | 0 |
| Thu 05 | 0 | 0.0 | 178 ms | 0 |
| Thu 07 | 0 | 0.0 | 159 ms | 0 |
| Thu 09 | 0 | 0.0 | 80 ms | 0 |
| Thu 11 | 0 | 0.0 | 66 ms | 0 |
| Thu 13 | 0 | 0.0 | 107 ms | 0 |
| Thu 15 | 0 | 0.0 | 125 ms | 0 |
| Thu 17 | 0 | 0.0 | 102 ms | 0 |
| Thu 19 | 0 | 0.0 | 73 ms | 0 |
| Thu 21 | 0 | 0.0 | 124 ms | 0 |
| Thu 23 | 0 | 0.0 | 153 ms | 0 |
| Fri 01 | 0 | 0.0 | 151 ms | 0 |
| Fri 03 | 0 | 0.0 | 218 ms | 0 |
| Fri 06 | 0 | 0.0 | 197 ms | 0 |
| Fri 08 | 0 | 0.0 | 128 ms | 0 |
| Fri 10 | 0 | 0.0 | 72 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 13 | 0 | 0.0 | 92 ms | 0 |
| Fri 15 | 0 | 0.0 | 120 ms | 0 |
| Fri 17 | 0 | 0.0 | 75 ms | 0 |
| Fri 18 | 0 | 0.0 | 130 ms | 0 |
| Fri 19 | 0 | 0.0 | 76 ms | 0 |
| Fri 21 | 0 | 0.0 | 165 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Carbon yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Carbon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Carbon alerts to Slack, Discord or a webhook — free.
We track Carbon (carbon3d.com) as part of the Cloud & developer group. From rapid prototyping to end-use parts, the Carbon Digital Light Synthesis Process is the dream of Additive Manufacturing realized.
Carbon publishes an official status page at status.carbon3d.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 127 ms average, 68–218 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Carbon incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
127 ms on average over the last 24 hours (68–218 ms).
Yes, at https://status.carbon3d.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Carbon here at once, the problem is on Carbon's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Carbon. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.