Twilio's Dominican Republic SMS Crisis: What Three Weeks of Delivery Failures Teach Us About Telecom Resilience
When your two-factor authentication code doesn't arrive, you probably don't think about SS7 protocol handshakes. But for businesses in the Dominican Republic, that technical detail has become a very expensive problem.
Twilio, one of the world's largest communications platforms, is experiencing ongoing SMS delivery issues to Orange and Altice networks in the Dominican Republic as of January 2026, with error rates fluctuating between 15% and 25% depending on time of day and message content, according to Twilio's Status Page (January 8, 2026). Here's why this matters more than a typical service hiccup, and what it reveals about telecommunications infrastructure in the Caribbean.
The Technical Breakdown
The root cause isn't some vague "technical difficulties" placeholder. According to an Internal Twilio Engineering Report from January 5, 2026, the primary issue is attributed to routing problems between Twilio's aggregator and the Orange/Altice networks, specifically persistent failures in the SS7 protocol handshake that prevent messages from being delivered correctly.
SS7 (Signaling System 7) is the backbone protocol that makes phone networks talk to each other. When these handshakes fail, messages essentially get stuck in digital limbo, unable to complete their journey from sender to recipient.
What makes this particularly concerning? Orange and Altice collectively hold approximately 75% of the mobile subscriber market share in the Dominican Republic as of Q4 2025, per the INDOTEL Market Share Report. That's not a niche carrier problem, that's most of the country's mobile users.
The Duration Problem
This isn't Twilio's first rodeo with Caribbean SMS issues. In Q3 2025, they experienced a similar disruption affecting SMS delivery to Claro Dominican Republic that lasted 48 hours, according to a Downdetector Report from that period. Frustrating, but manageable.
The current Orange/Altice issue has now persisted intermittently for over three weeks, surpassing the previous incident significantly. When error rates fluctuate between 15-25%, you can't even plan around it. Sometimes messages go through, sometimes they don't. That uncertainty is almost worse than a complete outage.
Real Business Impact
Let's talk numbers. Based on a survey of businesses affected by the SMS outage, a conservative estimate puts daily financial losses at $50,000 across the banking, e-commerce, and tourism sectors, attributable to failed transaction verifications and customer communications, according to the Dominican Republic Chamber of Commerce Survey from January 2026.
Banks can't send OTPs for transactions. E-commerce sites can't confirm orders. Hotels can't send booking confirmations. Every failed message represents either a blocked transaction or additional support costs as customers reach out asking where their code is.
The intermittent nature makes it worse. You can't just switch to email or push notifications when 15-25% of your messages randomly fail. You need SMS as a backup, but that backup is unreliable.
What Users Actually Experience
From a consumer perspective, this manifests as frustrating phantom problems. You're trying to log into your banking app, the code never arrives, and you're left wondering if it's your phone, the bank, or something else entirely. Most users have no idea Twilio exists, let alone that there's an SS7 handshake problem three layers deep in the infrastructure.
Critical communications just vanish. Delivery notifications, security alerts, appointment reminders, all potentially lost to the void. And because the error rates vary, sometimes everything works fine, which makes troubleshooting nearly impossible from a user perspective.
The Bigger Picture
This incident exposes something important about telecommunications resilience in regions that don't always get top billing in infrastructure discussions. When 75% of your market is served by carriers experiencing protocol-level issues with a major platform like Twilio, you've got a single point of failure problem that goes beyond any one company's control.
The technical debt in telecommunications infrastructure is real, and it shows up in exactly this kind of prolonged, intermittent failure. SS7 is decades-old technology still running critical infrastructure, which means these problems won't simply disappear with a software patch.
For businesses operating in the Caribbean, this is a wake-up call: SMS redundancy isn't optional. Having fallback providers, alternative notification channels, and clear communication strategies for when primary channels fail isn't paranoia, it's operational necessity.
Three weeks is a long time to be flying half-blind. The question isn't whether this gets resolved eventually, it's what breaks in the meantime.