Is CallHippo down?
Last checked 2m agoNo incidents right now.
CallHippo is operational right now. Last checked 2m ago; the most recent incident resolved 1d ago.
Real-time CallHippo status, recent outages, and incident history — pulled directly from CallHippo's official status page at https://callhippo.statuspage.io every 5 minutes. Pingoru tracks 9 CallHippo services and has captured 34 incidents in the last 90 days (99.99% uptime). Get email, Slack, Discord, or webhook alerts the moment CallHippo reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 2 updates
- investigating · Jun 12, 2026, 03:04 PM UTC
We're investigating a disruption affecting the CallHippo dialer and calling services. Our engineers are working urgently to restore full service.
- resolved · Jun 12, 2026, 03:05 PM UTC
The dialer and calling services are back to normal. We're sorry for the inconvenience caused.
Latest: The dialer and calling services are back to normal. We're sorry for the inconvenience caused.
-
-
Timeline · 2 updates
- investigating · Jun 12, 2026, 05:31 AM UTC
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.
- resolved · Jun 12, 2026, 05:34 AM UTC
All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
Latest: All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
-
-
Timeline · 2 updates
- investigating · Jun 12, 2026, 04:51 AM UTC
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.
- resolved · Jun 12, 2026, 04:54 AM UTC
All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
Latest: All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
-
-
Timeline · 2 updates
- investigating · Jun 12, 2026, 12:15 AM UTC
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.
- resolved · Jun 12, 2026, 12:22 AM UTC
All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
Latest: All calling services via our Bangalore datacenter have been fully restored. We apologize for the disruption and appreciate your patience.
-
-
Timeline · 2 updates
- investigating · Jun 10, 2026, 03:04 PM UTC
We're investigating a disruption affecting the CallHippo dialer and calling services. Our engineers are working urgently to restore full service.
- resolved · Jun 10, 2026, 03:05 PM UTC
The dialer and calling services are back to normal. We're sorry for the inconvenience caused.
Latest: The dialer and calling services are back to normal. We're sorry for the inconvenience caused.
-
See the full CallHippo outage history
29 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse CallHippo outage history →Or sign up free to get alerts when CallHippo breaks · 10 free monitors · No credit card
- Started Jun 12, 2026, 03:04 PM UTC · Resolved Jun 12, 2026, 03:05 PM UTC · 57s
- Started Jun 12, 2026, 05:31 AM UTC · Resolved Jun 12, 2026, 05:34 AM UTC · 2m
- Started Jun 12, 2026, 04:51 AM UTC · Resolved Jun 12, 2026, 04:54 AM UTC · 2m
- Started Jun 12, 2026, 12:15 AM UTC · Resolved Jun 12, 2026, 12:22 AM UTC · 6m
- Started Jun 10, 2026, 03:04 PM UTC · Resolved Jun 10, 2026, 03:05 PM UTC · 1m
- Started May 29, 2026, 06:14 PM UTC · Resolved May 29, 2026, 06:18 PM UTC · 4m
- Started May 25, 2026, 05:03 PM UTC · Resolved May 25, 2026, 05:04 PM UTC · 1m
- Started May 24, 2026, 04:28 AM UTC · Resolved May 24, 2026, 04:36 AM UTC · 7m