Ecamm Outage History
2 incidents recorded over the last 365 days, 2 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 Ecamm Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jun 26, 2026 | Error Messages in Ecamm AppThis incident has been resolved. If you are still seeing error message connecting to Ecamm servers, try changing your Mac's DNS server, or contact our support team for additional troubleshooting. | 22h 11m | Resolved |
| Jun 26, 2026 | Ecamm DNS IssueA DNS issue prevented many Ecamm services from functioning on Friday morning. The issue has been corrected but users may see connection issues until DNS changes propagate throughout the afternoon. | -311 min | Resolved |
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 Ecamm 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 Ecamm 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 Ecamm 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 Ecamm outage in this window ran 22h 11m, against a mean recovery of 22h 11m. If you depend on Ecamm 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.