Minor impactResolvedCommunication

Twilio incident: Even Though the AU Sender Ids Were Registered With Acma and Shared Across the Sub Accounts Sms Are Delivered as Unverified From Today

Twilio reported this minor-impact incident on its official status page on Jul 1, 2026, 00:16 UTC. It was resolved after 6 min.

Right now Twilio is operational. Live Twilio status →

🔔 Get alerted when Twilio has issuesFree · email alerts · no credit card
Jul 1, 2026, 00:16 UTC
started
Jul 1, 2026, 00:22 UTC
resolved
6 min
duration
Minor
impact

Timeline

updates from Twilio's status page ↗
  1. resolvedJul 1, 2026, 00:22 UTC

    The issue affecting Verify messages being delivered using default TWVerify has been resolved, and the service is functioning normally at this time.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Twilio's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Twilio have incidents?

Twilio reported 501 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 5h 49m. See Twilio's uptime and incident history

← Previous: Conversation Intelligence Is Not Processing Conversations and Will Have Delays Running Operators (Jun 30, 2026)Next: Issue With Some Verified Senders Appearing as Unverified (Jul 1, 2026) →
Twilio incident on Jul 1, 2026: Even Though the AU Sender Ids Were Registered With Acma and Shared Across the Sub Accounts Sms Are Delivered as Unverified From Today · APIStatus.watch