CallHippo had 16 outages in the last 2 years totaling 35h 37m of downtime — averaging 0.7 incidents per month.
There were 16 CallHippo outages since July 8, 2024 totaling 35h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're aware of a disruption affecting calling services routed through our Bangalore datacenter. Our engineering team is actively investigating. Calls through other regions are unaffected.
All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
We're investigating a disruption affecting the CallHippo dialer and calling services. Our engineers are working urgently to restore full service.
The dialer and calling services are back to normal. We're sorry for the inconvenience caused.
We're experiencing an issue with the CallHippo web dashboard. Our team is actively investigating and working on a fix, no call data is at risk.
The web dashboard is fully operational again. All features and data are accessible. Thank you for bearing with us.
We're investigating an issue with the CallHippo APIs, which may impact call logs, activity feeds, webhooks, and third-party integrations. Our team is actively diagnosing the root cause.
The CallHippo APIs are fully restored. Call logs, activity data, and all integrations are syncing normally. Thank you for your patience.
We're aware of a disruption impacting outbound and inbound calls routed through our Bangalore datacentre. Our engineering team is actively investigating. Calls through other regions are unaffected.
All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
We are currently experiencing calling issues in Spain and Austria due to an issue with a primary carrier. Our team is actively investigating the problem and working with the carrier to restore services as soon as possible. Some calls may fail or experience disruptions during this time.
This incident has been resolved.
We are currently facing issues with our primary carrier, which may affect calling services. Our team is investigating the issue and working on a fix.
This incident has been resolved.
Our monitoring system has detected a potential downstream issue affecting the India calling service for Bangalore datacentre.
We have identified the issue related to the data center network routing. Our team is currently working on resolving it
A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure calling service are back to normal.
This incident has been resolved.
Callhippo is aware of, and investigating an issue which potentially impacts multiple customers. Further detail will be provided as more information becomes available.
We are currently experiencing an issue due to a Cloudflare outage affecting CallHippo services. Our team is closely monitoring the situation and working on a resolution. Some users may experience service disruptions. We appreciate your patience and will provide updates as soon as possible.
We are seeing services recover, but customers may continue to observe higher-than-normal error rates as we continue remediation efforts.
A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal.
Callhippo services are currently operating normally. We are no longer observing elevated errors or latency across the network. This incident has been resolved.
Our monitoring has alerted us to a potential downstream service issue with our suppliers that may be impacting multiple services
We’re currently experiencing a global outage affecting calls due to issues with AWS, Vonage, and Twilio. Our teams are actively working with partners to restore services soon.
We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to monitor and provide additional information.
This incident has been resolved.
Resolved This incident has been resolved. Oct 03, 2025 - 12:55 UTC Monitoring A fix has been implemented and we are monitoring the results. Oct 03, 2025 - 15:37 UTC Identified Callhippo has identified an increased level of errors on API: customers may observe sporadic 504 errors in requests. The issue has been identified, and a fix is in progress. Oct 03, 2025 - 15:25 UTC
Resolved This incident has been resolved. Oct 07, 2025 - 16:30 UTC Monitoring A fix has been implemented and we are monitoring the results. Oct 07, 2025 - 16:05 UTC Identified We have identified the cause of the issue and have taken corrective actions. We are monitoring the impact of those mitigations. Oct 07, 2025 - 15:40 UTC Update We are continuing to investigate the issue. During this time some of call will drop Oct 07, 2025 - 15:35 UTC Investigating We are currently investigating a delay in database operations Oct 07, 2025 - 15:20 UTC
Resolved: Resolution: 10:25 UTC A fix has been implemented, and all services are now operating normally. We continue to monitor the systems to ensure stability. Identification: 10:10 UTC During a scheduled database upgrade, some internal changes unexpectedly impacted our database, leading to temporary service disruptions across multiple platforms. Impact: New call connectivity was failing Call recordings were not being generated
Resolution: 08:15 UTC - A fix has been implemented and the issue is resolved. Impact: - Automatically logged out from the web and dialer - Unable to log in to the web and dialer
Resolution: 17:45 UTC - A fix has been implemented and the issue is resolved Identification: 17:15 UTC - We have identified that MongoDB has changed the indexation in one of their clusters. This has impacted one of our database operations, resulting in the above issues being faced by some users. Impact: - Unable to log in to the web - Unable to log in to the dialer - Unable to log in to the mobile applications - Calling is not working - Dialer is loading
Resolution: 11:10 UTC - We have increased our infrastructure resources' capacities to avoid such occurrences in future. Identification: 10:30 UTC - Some of the customers may be facing delay in calls getting connected for India calling. The delay is due to the high call volume. Impact: - Calls are taking longer than expected to get connected. - Calls are not connected for India Numbers.