MightyCall Outage History
12 incidents recorded over the last 365 days, 4 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 MightyCall Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 21, 2026 | Issues with inbound callsThe issue with inbound calls experienced by some users has been fully resolved. All services are now operating normally. We appreciate your patience while our team worked to address and resolve the problem. | 1h 16m | Resolved |
| Jul 13, 2026 | Webphone IssuesThe issue with the unstable network conditions affecting the webphone experienced by some users has been fully resolved. All services are now operating normally. We appreciate your patience while our team worked to… | 2h 1m | Resolved |
| Mar 3, 2026 | Issues with Inbound/Outbound CallsThe issue with inbound/outbound calls experienced by some users has been fully resolved. All services are now operating normally. We appreciate your patience while our team worked to address and resolve the problem. | 43 min | Resolved |
| Jan 30, 2026 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 29, 2026 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 20, 2026 | Call Center Service Availability IssuesThe DDoS attack impacting access to the web & mobile platforms for some Call Center users has been fully mitigated, and service has remained stable. This incident is now resolved. We have confirmed there is no evidence… | 15 min | Resolved |
| Jan 13, 2026 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 13, 2026 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 23, 2025 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 4, 2025 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 4, 2025 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Nov 6, 2025 | Scheduled system updateThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 MightyCall 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 MightyCall 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 MightyCall 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 MightyCall outage in this window ran 2h 1m, against a mean recovery of 1h 1m. If you depend on MightyCall 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.