Resolved -
This incident has been resolved.
Feb 12, 10:32 EST
Update -
Out of an abundance of caution, and to allow for additional testing and validation, we will be postponing the maintenance to re-enable CNAM that was previously planned for Monday morning.
Once testing and verification are complete, we will share the new maintenance date here and publish an official maintenance notice on Trust.
Feb 6, 17:05 EST
Update -
CNAM services remain temporarily disabled for the affected DIDs. The carrier has confirmed that both inbound calling and CNAM services have been restored for their other Non-Sangoma customers. Out of an abundance of caution, we have requested that CNAM services for our impacted DIDs be re-enabled during a planned maintenance window on Monday at 4:00 AM Eastern Time, which represents the lowest call-volume period of the week. Our engineering team will be on a joint bridge with the upstream carrier during this maintenance to validate service restoration and to immediately roll back the change if any issues are observed. This maintenance activity will be posted to Trust before the scheduled window.
Feb 4, 18:21 EST
Update -
The carrier informed us that CNAM was turned back on, which created the problem state once again. CNAM has been disabled, and we have confirmation from carrier leadership and engineering that the CNAM feature will not be touched again without our consent and without testing in a non-production environment first.
Feb 3, 16:24 EST
Update -
We are still investigating Inbound Failures and working with the carrier team.
Feb 3, 16:10 EST
Update -
We are aware that customers may still be experiencing inbound call failures. We are investigating all reports.
Feb 3, 15:46 EST
Monitoring -
Engineers have identified and resolved the issue causing inbound call failures. The affected Business Voice numbers were hosted by a specific backend voice carrier. The issue was traced to a degraded CNAM platform, which led to overload of a buffer on the carrier’s SBC and resulted in inbound calls failing for our subset of customers.
To restore service, the CNAM servers were disabled, and inbound calling has since been fully restored. At this time, CNAM functionality remains unavailable. Engineers from the hosting carrier are actively working to restore this service as quickly as possible.
Feb 3, 15:25 EST
Identified -
The issue has been identified and a fix is being implemented.
Feb 3, 15:07 EST
Update -
We are continuing work on a solution for customers who remain impacted.
Feb 3, 14:32 EST
Update -
We are continuing to investigate this issue.
Feb 3, 13:58 EST
Update -
We have identified a group of Business Voice customers who are experiencing inbound calling failures. Engineers have isolated the problem and are working on a fix.
Feb 3, 13:26 EST
Update -
We are continuing to investigate this issue.
Feb 3, 13:06 EST
Investigating -
We have discovered an issue with inbound calls that is currently affecting a subset of Business Voice and Business Voice+ customers. Our engineering team is actively investigating the matter.
Feb 3, 13:05 EST