MightyCall logo and current status indicator

MightyCall Incident History

MightyCall is currently operational with all systems functioning normally.

Last checked Jul 26, 2026 8:47 AM UTC from MightyCall's official status page

Incident History

Showing incidents from the last 15 days

Report: "Issues with inbound calls"

Last update
resolved

The 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.

monitoring

The upstream carrier has confirmed that the issue with inbound call routing has been resolved, and calls are now connecting as expected. We will continue monitoring the service for stability. If you experience any further issues with inbound calls, please reach out to our support team. A final update will follow, once the issue is fully confirmed as resolved.

investigating

We have identified the root cause of the inbound calling issue affecting some users. The disruption is related to routing difficulties on the upstream carrier's side, and our team is actively working with the carrier to restore normal service. We will provide another update once the fix has been implemented.

Report: "Webphone Issues"

Last update
resolved

The 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 address and resolve the problem.

monitoring

A fix has been successfully deployed to resolve the issue with the unstable network conditions affecting the webphone. We're currently monitoring the platform closely to ensure stability. If you experience any further delays or issues with the webphone, please reach out to our support team. A final update will follow, once the issue is fully confirmed as resolved.

investigating

We're currently investigating the issue with the unstable network conditions affecting the webphone reported by some users. Our team is working to identify the root cause and restore normal operation as soon as possible.