Twilio: Hosted Number Verification Calls not Reaching Customers
Affected components: PHONE NUMBERS
Timeline of updates
- investigating
Our monitoring systems have detected a potential issue with OTP calls for Hosted SMS Verification. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
- investigating
We are investigating an issue with Hosted Numbers. Users may experience delays in receiving OTP verification calls. We will provide another update in 1 hour or as soon as more information becomes available.
- investigating
We continue investigating an issue with Hosted Numbers. Users may experience delays in receiving OTP verification calls. We will provide another update in 2 hours or as soon as more information becomes available.
- identified
We have identified the cause of an issue affecting one-time passcode verification calls for Hosted Numbers. Some customers are not receiving these calls, which prevents them from verifying their numbers and continuing with SMS hosting.
Customers may need to enable the required geo permissions on their account and retry the verification call. We are working to resolve this and will provide another update in 4 hours or as soon as more information becomes available. - monitoring
We are seeing recovery for the issue affecting one-time passcode verification calls for Hosted Numbers. 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.
Changes Rewindex caught on this incident
- Incident updated: Hosted Numbers OTP Call Delivery Delays
- Incident updated: Hosted Number Verification Calls not Reaching Customers
- Incident updated: Hosted Number Verification Calls not Reaching Customers
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
88071322f16ed549…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
0a08d7b58e3bd7f0…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
02d2a3e3fd8cdad8…Version 4 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
044b9619c6a053d8…
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Twilio, started 2026-10-22 14:56 UTC, not resolved, 5 update(s); edited after publishing.
- Title
- Hosted Number Verification Calls not Reaching Customers
- Vendor
- Twilio
- Date
- URL
- https://rewindex.com/company/twilio/incidents/r4tnl81fj8cm
Twilio profileRecent Twilio incidentsAll outages on October 22, 2026Twilio in October 2026MarkdownJSON