← Back to Twilio History
minor✓ Resolved

Gateway API (Lookup API) Failure Increase on Verizon in United States

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

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
The incident has been resolved and Lookup API transactions involving Verizon in the United States are operating normally.
monitoring
We have observed the recovery for Lookup API transactions involving Verizon in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available.
investigating
Twilio customers may be experiencing failure responses for Lookup API transactions on Verizon in the United States. Our team is actively investigating the issue. We will provide another update in 8 hours or as soon as more information becomes available.
investigating
Twilio customers may be experiencing failure responses for Lookup API transactions on Verizon in the United States. Our team is actively investigating the issue. We will provide another update in 4 hours or as soon as more information becomes available.
investigating
Twilio customers may be experiencing failure responses for Lookup API transactions on Verizon in the United States. Our team is actively investigating the issue. We will provide another update in 2 hours or as soon as more information becomes available.
investigating
Twilio customers may be experiencing failure responses for Lookup API transactions on Verizon in the United States. Our team is actively investigating the issue. We will provide another update in 1 hour or as soon as more information becomes available.

📊 TECHNICAL DETAILS

Internal ID
2adc854c-9ff4-4cb4-88ec-e6113913f52a
External ID
d7cx8sdb4hr8
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
10h 23m
Total Duration
6
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 request generation of one.
0 / 100 requests100 more needed