Freshcaller incident
Twilio Incident - Scoped Phone Number Filtering Endpoints Not Returning Filtered Results
Freshcaller experienced a minor incident on August 5, 2020, lasting 5h 22m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Aug 05, 2020, 09:16 PM UTC
Our Service provider has identified three impacted endpoints /IncomingPhoneNumbers/TollFree, /IncomingPhoneNumbers/Local, and /IncomingPhoneNumbers/Mobile. API calls to these endpoints will not return the appropriate filtering, instead will return all phone numbers. The default /IncomingPhoneNumbers endpoint works as expected. We will update as soon as we have more information.
- investigating Aug 05, 2020, 09:28 PM UTC
Our service provider has identified three impacted endpoints; /IncomingPhoneNumbers/TollFree, /IncomingPhoneNumbers/Local, and /IncomingPhoneNumbers/Mobile. API calls to these endpoints will not return the appropriate filtering, instead returning all phone numbers. The default /IncomingPhoneNumbers endpoint works as expected. We will update as soon as we have more information.
- investigating Aug 05, 2020, 09:54 PM UTC
Our service provider has identified three impacted endpoints; /IncomingPhoneNumbers/TollFree, /IncomingPhoneNumbers/Local, and /IncomingPhoneNumbers/Mobile. API calls to these endpoints will not return the appropriate filtering, instead returning all phone numbers. The default /IncomingPhoneNumbers endpoint works as expected. We will update as soon as we have more information.
- investigating Aug 05, 2020, 10:52 PM UTC
Our service provider has identified the problem issue causing the three endpoints to return incorrect filtering results.We will update as soon as we have more information.
- investigating Aug 06, 2020, 12:51 AM UTC
Our service provider has deployed a fix to restore functionality to the three impacted endpoints. We will update as soon as we have more information
- investigating Aug 06, 2020, 01:21 AM UTC
Our service provider has deployed a fix to restore functionality to the three impacted endpoints.We will update as soon as we have more information
- resolved Aug 06, 2020, 02:38 AM UTC
The issue has been resolved at our service provider’s end. We are closely monitoring it.