Historical record of incidents for CallHub
Report: "CallHub is facing service disruption with voice calls broadcast for US / Canada numbers"
Last updateThis incident has been fixed and voice calls are working fine. It was a caching issue on one of our servers. We are considering it resolved now. Sorry for the inconvenience caused to you.
We have identified the problem and placed a fix to resolve it. Voice calls should work for all CallHub customers. We will share more insights later. We are still monitoring the voice services at our end.
We are currently investigating the matter with the concerned team and will keep you posted on it. Sorry for the inconvenience.
Report: "CallHub services are currently disrupted due to technical issues"
Last updateWe are considering this incident resolved. Root Cause: A sudden surge in database load and high data transfer overwhelmed the system. We've undertaken the necessary steps to address these situations.
We are continuing to monitor for any further issues.
The system is now operating, with full restoration expected imminently. Please anticipate slightly longer wait times momentarily, but these will soon decrease. Thank you for your continued patience as we work towards complete normalization.
The problem has been pinpointed, and a solution is en route. Thank you for your patience as we work swiftly to implement the fix. Stay tuned for further updates. We appreciate your understanding.
We regret to inform you that the CallHub services like calling & texting have been impacted at the moment since 04:50 PM PST. Our technical team is conducting a thorough investigation to identify the root cause of the interruption. We will provide regular updates on the progress. We apologize for any inconvenience this may cause and appreciate your understanding.
Report: "The CallHub dashboard is throwing HTTP error 403 and experiencing a similar issue on the mobile app."
Last updateRCA - One of the database connection pooler system configuration settings was incorrectly set to lower limit when we upgraded the servers which resulted in failure of application to db server connections when the traffic was high. Impact - System was entirely down from 5:16pm PST to 5:35pm PST - 19min complete outage. System was available with degraded performance (slowness) from 5:35pm PST till about 5:50pm PST - 15min degraded performance.
On Feb 14, 2024, CallHub users experienced disruption on the CallHub dashboard, encountering HTTP error 403. This issue also affected the performance of the mobile app during the period from 5:16 PM to 5:50 PM PST. Upon conducting an initial investigation, we identified the root cause related to auto-scaling processes. The issue has been promptly addressed, and as of now, all services have been restored to normal functionality. Our team actively monitors the services to ensure stability. We apologize for any inconvenience caused during this period.
Report: "Again, CallHub calling services are affected due to a current service interruption at one of our third-party services."
Last updateThis incident has been resolved.
The concerned team has implemented a fix, and your services are back to normal. We are still monitoring the system. Sorry for the inconvenience caused to you.
We are working with the concerned team to get a fix or other feasible solution as soon as possible. Our engineering is also working on a fallback mechanism to avoid such instances. Stay tuned.
Report: "Due to a current service interruption at one of our third-party services, CallHub calling services are affected for all customers."
Last updateThe concerned team has implemented a fix and the calling service should be back to normal for you. This incident has been resolved.
We are still working with the concerned teams on a fix. Please stay tuned.
We are working with the concerned team and will keep you posted here. A fix is being implemented. Stay tuned.
Report: "Due to a current service interruption at one of our third-party services, CallHub calling services are affected for all customers."
Last updateThis incident has been resolved.
The concerned team has implemented a fix and is monitoring the impact. The calling service should be back to normal for you. Still, we are monitoring the system.
We are working with the concerned team and will keep you posted here.
Report: "We encounter sporadic Call Centre problems while making calls in the web browser. This is due to an ongoing issue with one of our telecom carriers."
Last updateThe calling service has been fully restored and is now operational.
A fix has been implemented, and the browser call is returning to normal. However, we are still monitoring the system.
We are actively investigating the problem and collaborating with relevant teams to resolve it quickly.
Report: "Intermittent service interruption happened for CallHub US customers"
Last updateOur engineering team has deployed the fix on servers to avoid such instances in the future. After monitoring the services for the last six hours, we consider it resolved.
We briefly observed a substantial slowdown with DB queries between 23:15 & 23:25 and 23:46 & 23:57 UTC on October 18, 2022. After that, there have been no interruptions, and all services are functioning normally. Our team is thoroughly looking into the issue and will shortly present a root cause investigation.
Report: "Customers in US/Canada of CallHub may experience service interruption"
Last updateThis incident has been resolved.
We have deployed the fix, and CallHub services are resumed now. However, we are still monitoring the situation.
We are continuing to work on the fix of this issue.
Our teams are investigating the matter, and they have identified the issue. Please stay tuned.
Report: "CallHub users may experience 5xx errors or timeouts while reaching to CallHub domains"
Last updateThis incident has been resolved and we are closing it for the time.
We identified the issue with one of our third-party services (Cloudflare’s network), and they have deployed the fix. As a result, all CallHub domains are accessible now, and we are still monitoring the situation.
We are currently investigating the matter and will keep you posted on it.
Report: "Non EU CallHub customers are facing slowness or intermittent service interruption"
Last updateThe issue has been resolved.
A fix has been implemented and services recovery is there. CallHub application should be for you now. We are still monitoring the system for the time.
The issue has been identified and the concerned teams are working to deploy the fix. Please stay tuned. Sorry for the inconvenience.
We are continuing to investigate this issue.
We are facing an infrastructure issue with one of our vendors (AWS) and working on this matter along with their team. Please stay tuned.
Report: "Voice Rest APIs services degradation at Telecom Carrier's end"
Last updateThis incident has been resolved.
A fix has been implemented and the services are recovering successfully. Voice calls should work for you. Still, we are monitoring for the time.
We are currently investigating an intermittent issue with latency and timeout errors—one of our Telecom Carriers Voice services got impacted. We are actively working on it. Please stay tuned.
Report: "Voice Broadcasting and Messaging services are downgraded"
Last updateThis incident has been resolved.
All services are restored and we are monitoring the situation. Please stay tuned.
You may experience failed calls, latency/time outs, or delayed or failed messages intermittently. We are currently investigating the matter with our Telecom Carrier.
Report: "Voice Broadcasting and Messaging services are impacted"
Last updateBoth services (Voice Broadcast & Messaging) are back to normal at the Telecom Carrier end. Therefore, we are considering it as resolved for the time being.
We have identified that the issue is still occurring, and both services calling and messaging are impacted. As a result, you may be experiencing failed calls, latency/time outs, and delayed or failed messages. The problem is happening at the Telecom Carrier end. We are in constant touch on this. Sorry for the inconvenience.
CallHub Messaging service is functional now and we are still monitoring for the time. Voice Broadcast service is partially restored and it will be normal soon. Please stay tuned!
With CallHub, a few customers are facing service interruption with voice broadcast and texting. We have identified the issue and are actively working on it. Please stay tuned for further updates.
Report: "Calling is not functional on one of CallHub's servers(NA)"
Last updateThe calling functionality is back to normal. We are considering it as resolved for the time being.
After identifying the issue, a fix has been implemented. As a result, the Calling functionality is back to normal. We are still monitoring the system.
We are currently investigating the issue and will keep you posted on it.
Report: "Service Interruption happened on one of CallHub's servers (NA)"
Last updateOne of the web services got halted and we need to restart the service to fix it.
Report: "SMS & MMS services got interrupted due to Telecom Carrier APIs issue"
Last updateSMS & MMS services are back to normal. We are considering it as resolved. Thanks!
SMS & MMS services are resumed as it is fixed by Telecom Carrier. We are still monitoring the situation.
Our engineering team has been alerted and is actively working on it. We will update you posted on it.
Report: "Analytics services impacted across all regions"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Analytics services are intermittently failing across all geographies. We are actively working to resolve this.
Report: "CallHub Voice & SMS services are impacted for some customers"
Last updateThis issue is resolved now. Note: If your account was switched to a different carrier, please continue to work with support team in case of any trouble.
Cause of the Issue: It came to our attention that one of the accounts using our services was sending misleading and unsolicited texts. This is a violation of our terms of service and the offending account has been suspended. Unfortunately, this incident has impacted our partner carrier poorly. As a result, services have been disrupted for some of our customers. Please visit https://callhub.io/callhub-outage-aug2020/ for more details. Resolution: We are moving affected accounts to a different carrier on request. If you want us to move your account, please reach out to our support team at support@callhub.io and we will get started immediately. Below article contains the detailed instructions to resolve the issue https://support.callhub.io/hc/en-us/articles/900002213163-CallHub-Outage-steps-to-resolve
We are continuing to investigate this issue.
CallHub Voice & SMS services impacted across all geographies, due to issues with our telecom carriers. We're working with them on resolving these issues. We will keep you posted on the updates. If you have any queries please do send them to support@callhub.io.
Report: "CallHub Voice & SMS services are impacted due to carriers"
Last updateThis incident has been resolved.
This issue is now resolved.
CallHub Voice & SMS services impacted across all geographies, due to issues with our telecom carriers. We're working with them on resolving these issues. We will keep you posted on the updates. If you have any queries please do send them to support@callhub.io.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
Report: "Elevated API Errors"
Last updateThis incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.