User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 25 min ago. Last stored result reached it in 467 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 419 ms | 0 |
| Tue 01 | 0 | 0.0 | — | 1 |
| Tue 03 | 0 | 0.0 | 462 ms | 0 |
| Tue 05 | 0 | 0.0 | 490 ms | 0 |
| Tue 07 | 0 | 0.0 | 300 ms | 0 |
| Tue 09 | 0 | 0.0 | 517 ms | 0 |
| Tue 11 | 0 | 0.0 | 439 ms | 0 |
| Tue 14 | 0 | 0.0 | 459 ms | 0 |
| Tue 16 | 0 | 0.0 | 513 ms | 0 |
| Tue 18 | 0 | 0.0 | 328 ms | 0 |
| Tue 20 | 0 | 0.0 | 425 ms | 0 |
| Tue 23 | 0 | 0.0 | 562 ms | 0 |
| Wed 01 | 0 | 0.0 | 325 ms | 0 |
| Wed 03 | 0 | 0.0 | 443 ms | 0 |
| Wed 05 | 0 | 0.0 | 489 ms | 0 |
| Wed 07 | 0 | 0.0 | 455 ms | 0 |
| Wed 10 | 0 | 0.0 | 497 ms | 0 |
| Wed 12 | 0 | 0.0 | 454 ms | 0 |
| Wed 14 | 0 | 0.0 | 333 ms | 0 |
| Wed 16 | 0 | 0.0 | 498 ms | 0 |
| Wed 18 | 0 | 0.0 | 383 ms | 0 |
| Wed 20 | 0 | 0.0 | 436 ms | 0 |
| Wed 23 | 0 | 0.0 | 523 ms | 0 |
| Thu 01 | 0 | 0.0 | 596 ms | 0 |
| Thu 03 | 0 | 0.0 | 498 ms | 0 |
| Thu 05 | 0 | 0.0 | 480 ms | 0 |
| Thu 07 | 0 | 0.0 | 369 ms | 0 |
| Thu 09 | 0 | 0.0 | 498 ms | 0 |
| Thu 11 | 0 | 0.0 | 492 ms | 0 |
| Thu 13 | 0 | 0.0 | 333 ms | 0 |
| Thu 15 | 0 | 0.0 | 531 ms | 0 |
| Thu 16 | 0 | 0.0 | 334 ms | 0 |
| Thu 18 | 0 | 0.0 | 457 ms | 0 |
| Thu 20 | 0 | 0.0 | 475 ms | 0 |
| Thu 22 | 0 | 0.0 | 522 ms | 0 |
| Fri 00 | 0 | 0.0 | 374 ms | 0 |
| Fri 02 | 0 | 0.0 | 905 ms | 0 |
| Fri 04 | 0 | 0.0 | 363 ms | 0 |
| Fri 06 | 0 | 0.0 | 390 ms | 0 |
| Fri 08 | 0 | 0.0 | 436 ms | 0 |
| Fri 10 | 0 | 0.0 | 437 ms | 0 |
| Fri 12 | 0 | 0.0 | 483 ms | 0 |
| Fri 14 | 0 | 0.0 | 458 ms | 0 |
| Fri 16 | 0 | 0.0 | 486 ms | 0 |
| Fri 17 | 0 | 0.0 | 413 ms | 0 |
| Fri 18 | 0 | 0.0 | 515 ms | 0 |
| Fri 19 | 0 | 0.0 | 441 ms | 0 |
| Fri 21 | 0 | 0.0 | 467 ms | 0 |
98.78% 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 Ecamm 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 Ecamm goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ecamm alerts to Slack, Discord or a webhook — free.
We track Ecamm (ecamm.com) as part of the Cloud & developer group. Powerful Facebook, YouTube, Instagram, X, Twitch, and LinkedIn Livestreaming platform for Mac.
Ecamm publishes an official status page at status.ecamm.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 98.78% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 481 ms average, 363–905 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 Ecamm incident since monitoring began 8 days ago.
From our own checks: 98.78% over 8 days of checks.
481 ms on average over the last 24 hours (363–905 ms).
Yes, at https://status.ecamm.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 Ecamm here at once, the problem is on Ecamm'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 Ecamm. 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.