← Back to Twilio History
minor✓ Resolved

Subset of API Requests Blocked with 403 Response

Twilio•
Status
resolved
Duration
50m
Updates
4
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
This incident related to API requests being blocked with 403 response is now resolved and service is fully restored.
monitoring
We are observing a recovery in API requests blocked with 403 response. We will continue to monitor to ensure full service recovery. We expect to provide another update in 30 minutes or as soon as more information becomes available.
investigating
Some requests are being blocked by our WAF with a 403 response due to stricter rules. We are working to mitigate the issue as quickly as possible and will provide updates here. We will provide another update in 1 hour or as soon as additional information is available.
investigating
Some requests are being blocked by our WAF with a 403 response due to stricter rules. We are working to mitigate the issue as quickly as possible and will provide updates here.

📊 TECHNICAL DETAILS

Internal ID
803baee9-870c-414a-b305-c39b45665bbc
External ID
gvcb0dssh6mg
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
50m
Total Duration
4
Status Updates
Affected Components
REST API
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