← Back to Twilio History
minor✓ Resolved

Caller ID Name Failures

Twilio•
Status
resolved
Duration
2h 32m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
The issue has been resolved and Caller ID Name (CNAM) information look up for Trunking Originating calls in the us2 region is operating normally at this time.
monitoring
Caller ID Name (CNAM) information look up for Trunking Originating calls in the us2 region is now operating normally. We will continue to monitor for system stability. We'll provide another update in 30 minutes or as soon as more information becomes available.
identified
The issue looking up Caller ID Name (CNAM) information for Trunking Originating calls in the us2 region has been identified. We are actively working with our Engineering Team to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
identified
The issue looking up Caller ID Name (CNAM) information for Trunking Originating calls in the us2 region has been identified. We are actively working with our Engineering Team to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
investigating
We are experiencing an issue looking up Caller ID Name (CNAM) information for Trunking Originating calls in the us2 region. Customers may also experienced increased post dial delay (PDD). Our engineers are working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available.

📊 TECHNICAL DETAILS

Internal ID
27b4e840-44c2-4732-a101-1dbb63463c26
External ID
qdbh3n7mf54f
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
2h 32m
Total Duration
5
Status Updates
Affected Components
Origination US1
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed