Resolved after 1 day 3 hours, affecting ServiceCall.ai, on January 18, 2024.
We are confirming persistent reports of successful DNS propagation. We are monitoring full operation of telephony features in ServiceCall.ai.
Affected components
Update timeline
- investigating Jan 18, 2024, 01:23 PM UTC
We are investigating reports of issues accessing ServiceCall.ai.
- monitoring Jan 18, 2024, 02:29 PM UTC
A fix has been implemented and we are monitoring the results.
- investigating Jan 18, 2024, 03:05 PM UTC
We are investigating reports of telephony issues within the ServiceCall.ai product. We are working with our technology provider partners on this issue. We will update as additional information becomes available.
- identified Jan 19, 2024, 02:13 AM UTC
The issue has been identified. We are working with openDNS to restore domain lookup which is impacting inbound telephony features in ServiceCall.ai.
- identified Jan 19, 2024, 01:47 PM UTC
We persist in our collaboration with openDNS to restore domain lookup functionality, impacting inbound telephony features within ServiceCall.ai.
- monitoring Jan 19, 2024, 03:13 PM UTC
We are confirming persistent reports of successful DNS propagation. We are monitoring full operation of telephony features in ServiceCall.ai.
- resolved Jan 19, 2024, 04:30 PM UTC
This incident has been resolved.
Your product runs on more than Service Fusion
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services