Freshcaller incident
On Call Engineers are Investigating Elevated HTTP 500 errors
Freshcaller experienced a minor incident on September 9, 2021 affecting Inbound Calls and Outbound Calls and 1 more component, lasting 1h 50m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 09, 2021, 04:55 PM UTC
Our monitoring systems have detected a potential issue causing elevated rates of HTTP 500 errors for Programmable Messaging and Programmable Voice REST API requests. Our engineering team has been alerted and is actively investigating. We will update as soon as we have more information.
- investigating Sep 09, 2021, 05:22 PM UTC
We are currently investigating an elevated rate of HTTP 500 errors when accessing or modifying A2P brand registration or Programmable Voice call recordings. Our engineers are working on the issue, and we will provide another update in 1 hour or as soon as more information becomes available
- monitoring Sep 09, 2021, 06:11 PM UTC
We are seeing recovery from the API errors for voice call recordings and are monitoring closely for any changes. We are now reporting the status of the A2P brand registration API resource as a separate incident. We will provide another update in 30 minutes or as soon as more information becomes available.
- resolved Sep 09, 2021, 06:45 PM UTC
The issue causing elevated rates of HTTP 500 errors for the Programmable Voice recordings API resource has been resolved, and the service is operating normally at this time.