Twilio

The Swedish regulator is asking whether calls that should have been blocked reached the network. Behind the inquiry lies a divided obligation: one provider admits the call, while another may hold the information needed to check it.

Twilio says it has identified the cause of SMS delivery failures to subscribers of a network it calls Dukagjjni in Kosovo, but it has not published that cause or a recovery time. A second, earlier incident object still says investigating, leaving customers with two open provider records and a transaction ledger to reconcile.

For two hours and 43 minutes on 3 August, Twilio tracked a major incident in which ConversationRelay customers configured with Deepgram’s nova-2 or nova-3 speech models were described as “hard down.” Other named model paths remained available, but Twilio’s own advice contained the crucial qualification: a customer should consider Google only if that option had already been validated for the use case.

Twilio says SMS delivery receipts on a route to Safaricom subscribers in Kenya recovered after a 57-minute public incident window. The underlying messages may have succeeded while their acknowledgements arrived late. Service is being monitored, not declared resolved, and the operator has not explained the cause or quantified the affected traffic.

Twilio reported delays and failures from some alphanumeric sender IDs and long codes to Safaricom subscribers in Kenya. It identified an undisclosed cause, observed recovery after 94 minutes and was still monitoring stability at the fixed cutoff.

For 2 hours and 42 minutes on 1 August, Twilio reported delayed SMS delivery receipts from its phone numbers to Globe Telecom subscribers in the Philippines. Messages could still succeed. That distinction matters because applications often treat the receipt as a control signal even when the underlying transport outcome is different.

Twilio opened a minor incident at 02:57:20.918 UTC on 1 August for SMS delivery delays from a subset of its short codes to Claro subscribers in Colombia. At the fixed 03:17:59 cutoff, 20 minutes and 38.082 seconds had elapsed. There was no identified cause, recovery signal or resolution to report.

Twilio had observed recovery in SMS delivery toward Africell subscribers in Angola four times by the fixed 00:13:55 UTC cutoff on 1 August. It had not declared the minor incident resolved. The public case had been open for 25 hours, 42 minutes and 51.122 seconds, while cause, delay distribution, message scale and the remaining condition stayed undisclosed.

Twilio resolved a minor voice-call incident affecting a subset of origin numbers toward Claro subscribers in Colombia at 02:09:34.991 UTC on 31 July. During the 5-hour, 41-minute and 10.935-second case, “Mobile Numbers” became “Phone Numbers” and one update omitted Claro. The record never says those edits represented a wider technical footprint.

Twilio resolved a 3-hour, 21-minute and 39.361-second incident affecting SMS delivery toward Celcom subscribers in Malaysia at 02:12:32.051 UTC on 31 July. The case moved from investigation to observed recovery and then resolution; it never displayed an identified state. No delay distribution, message population or root cause was published.

Twilio closed a minor SMS incident affecting a subset of its phone numbers on the route to C+W LIME subscribers in the Cayman Islands at 06:18:08.210 UTC on 31 July. The case had opened the previous day and lasted 12 hours, 27 minutes and 40.379 seconds. The narrow route and origin subset are public; the size of that subset, cause and retry outcomes are not.

For 9 hours, 41 minutes and 49.987 seconds on 31 July, Twilio tracked delayed SMS delivery receipts for messages sent toward Telefónica subscribers in El Salvador. Its most important qualification was present from the first notice: message delivery might succeed while the receipt arrived late. Service was declared normal at 16:17:09.745 UTC, but the cause and delay distribution remained private.

Twilio said voice calls from its phone numbers to subscribers on multiple networks in Brazil were recovering on 31 July, but the incident was not resolved at the 20:19:07 UTC reporting cutoff. The first monitoring update came more than 18 hours after the case opened. Across that interval, the company acknowledged call failures and high post-dial delay, said it had identified the cause, and never disclosed what that cause was.

Twilio recorded delays in both inbound and outbound delivery for RCS and WhatsApp on 31 July. The incident opened at 15:35:24.910 UTC, moved to monitoring at 16:44:39.656 and was declared resolved at 17:14:27.140. The chronology is clear; the scale and cause are not. Twilio disclosed neither a geography nor a message count, and “delay” does not establish loss, duplication or corruption.

Twilio is a risk and accountability case because the accountability issue is that an authentication service stores data attackers can use to target the very people relying on it for protection, so enumeration prevention and notice specificity become core trust duties. The public record matters for Authy users, security teams, fraud analysts, mobile-account holders, developers, regulators, and authentication-service buyers who needed evidence that phone-number exposure was contained and translated into actionable protection guidance.

Twilio's 2022 breach began with messages that made a false login page look like ordinary work, but its significance lies beyond the stolen employee credentials. A cloud communications provider concentrated customer support access, phone-number verification, authentication services, and downstream user data behind those identities. The incident shows how a provider's internal authority becomes customer risk, why cheap and renewable abuse infrastructure can exhaust slower reporting channels, and what accountability requires after a company replaces a phishable control with a stronger one.