← Back to Twilio History
minor✓ Resolved

User Authentication Identity Gateway API Failure Increase for EnStream in Canada

Twilio•
Status
resolved
Duration
10h 43m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
The incident has been resolved and User Authentication Identity Gateway API failure increase for EnStream in Canada is operating normally.
monitoring
We have observed a recovery in User Authentication Identity Gateway API failure increase for EnStream in Canada and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.
monitoring
We have observed a recovery in User Authentication Identity Gateway API failure increase for EnStream in Canada and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
identified
Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for EnStream in Canada. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available.
identified
Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for EnStream in Canada. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available.
identified
Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for EnStream in Canada. Our team has identified the cause, and is 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
8bd3dfc3-01e5-4bbc-8b17-4bd58d7e1d3f
External ID
f2fshvcdkbg3
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
10h 43m
Total Duration
6
Status Updates
Affected Components
Lookup Identity Match
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