Freshcaller incident
Voice Calls Failures to a subset of Hong Kong Long Codes
Freshcaller experienced a minor incident on November 13, 2021 affecting Inbound Calls and Inbound Calls and 1 more component, lasting 6h 56m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 13, 2021, 08:27 PM UTC
Our telecom provider has become aware of a potential issue with voice calls failures from local and international numbers to a subset of Hong Kong long codes. Our engineers are working with our telecom provider to resolve the issue. We will update as soon as we have more information.
- investigating Nov 13, 2021, 09:08 PM UTC
We continue to observe call failures from local and international numbers to a subset of Hong Kong long codes. We are currently working with our carrier partner to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
- investigating Nov 13, 2021, 09:40 PM UTC
We continue to observe call failures from local and international numbers to a subset of Hong Kong long codes. We are currently working with our carrier partner to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
- investigating Nov 13, 2021, 11:41 PM UTC
We continue to observe call failures from local and international numbers to a subset of Hong Kong long codes. We are currently working with our carrier partner to resolve the issue. We expect to provide another update in 4 hours or as soon as more information becomes available.
- investigating Nov 14, 2021, 01:30 AM UTC
We have started seeing recovery for call failures to a subset of Hong Kong long codes. We will continue to monitor to ensure a full recovery. We expect to provide another update in 2 hours or as soon as more information becomes available.
- resolved Nov 14, 2021, 03:23 AM UTC
We are no longer observing call failures from local and international numbers to a subset of Hong Kong long codes. This incident has been resolved.