← Back to Twilio History
minor✓ Resolved

User Authentication Identity Gateway API Failure Increase and Gateway API High Latency for Verizon in United States

Twilio•Thu, Jun 4, 2026, 02:51 AM
Status
resolved
Duration
3h 24m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Jun 4, 2026, 06:15 AM
This incident has been resolved.
monitoringThu, Jun 4, 2026, 04:10 AM
We have observed a recovery in User Authentication Identity Gateway API failure increase and Gateway API high latency for Verizon in United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
identifiedThu, Jun 4, 2026, 04:08 AM
Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for Verizon in the United States. 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.
identifiedThu, Jun 4, 2026, 03:08 AM
Twilio customers may be experiencing User Authentication Identity Gateway API failure increase & high latency for Verizon in the United States. 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.
investigatingThu, Jun 4, 2026, 02:51 AM
Twilio customers may be experiencing User Authentication Identity Gateway API failure increase for Verizon in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available.

📊 TECHNICAL DETAILS

Internal ID
a4aa7854-1a2a-4f6a-adc2-44dd23c33de1
External ID
znt2wh3rcys8
🕐 Started
Thu, Jun 4, 2026, 02:51 AM
🔄 Last Updated
Thu, Jun 4, 2026, 06:15 AM
✓ Resolved
Thu, Jun 4, 2026, 06:15 AM
MINOR
Impact Level
3h 24m
Total Duration
4
Status Updates
Affected Components
Lookup SIM SwapLegacy Identity MatchAndAttributes
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed