It wasn't your wifi. It wasn't your phone.
En un martes ordinario de mayo, miles de personas en México, Brasil y Estados Unidos descubrieron casi simultáneamente que el hilo digital que los conecta con familiares, colegas y amigos había dejado de responder. La caída de WhatsApp, que comenzó a las 5:03 de la tarde y acumuló 710 reportes en menos de una hora, recordó una vez más cuán frágil es la infraestructura invisible sobre la que descansa buena parte de la comunicación humana contemporánea. Meta, la empresa que administra esa infraestructura, guardó silencio mientras sus usuarios buscaban respuestas en las mismas redes que también fallaban.
- A las 5:03 PM del martes, WhatsApp dejó de funcionar para miles de usuarios en tres países al mismo tiempo, sin previo aviso y sin explicación.
- En menos de cuarenta minutos, los reportes de falla escalaron de cero a 710, con WhatsApp Web como el punto más vulnerable: seis de cada diez afectados no podían cargar ni una sola conversación desde el navegador.
- Los usuarios se encontraron atrapados entre pantallas en blanco, mensajes de error, sesiones que pedían un inicio de sesión de Facebook y dispositivos que se negaban a sincronizarse entre sí.
- La caída no fue un evento aislado: ese mismo día Instagram había registrado su propio tropiezo horas antes, sumando otra señal de inestabilidad en la infraestructura de Meta.
- Mientras los reportes seguían acumulándose al caer la noche, Meta permanecía en silencio absoluto: sin comunicado, sin cronograma de restauración, sin reconocimiento público del problema.
No era el wifi. No era el teléfono. A partir de las 5:03 de la tarde de un martes, WhatsApp dejó de funcionar para miles de personas en México, Brasil y Estados Unidos, y la primera confirmación de que algo estaba realmente roto llegó de desconocidos en internet que reportaban exactamente lo mismo.
En media hora, la plataforma DownDetector —que monitorea cuándo los grandes servicios digitales colapsan— ya registraba 576 reportes. A las 5:43 PM, el conteo había llegado a 710. Quienes intentaban usar WhatsApp Web desde sus computadoras encontraban una pantalla en blanco con un mensaje de error. Quienes abrían la aplicación de escritorio veían, en cambio, una pantalla de inicio de sesión de Facebook. Otros simplemente no podían sincronizar su teléfono con su computadora, quedando desconectados de su historial de mensajes en uno u otro dispositivo.
El patrón de la falla fue revelador: el 60% de los reportes correspondía a WhatsApp Web, el 17% a problemas con la app móvil y el 14% a errores de inicio de sesión. No era un fallo localizado ni aleatorio, sino el tipo de colapso que sugiere una ruptura en la infraestructura central del sistema.
México concentró la mayoría de los reportes, pero la interrupción cruzó fronteras sin dificultad. Y llegó en un día en que Instagram, la otra gran plataforma de Meta, ya había tenido su propio tropiezo horas antes, aunque de menor escala.
Meta no emitió ningún comunicado. Sin explicaciones, sin disculpas, sin cronograma de recuperación. Mientras la tarde se convertía en noche, millones de usuarios seguían esperando —o buscando alternativas— sin saber qué había fallado ni cuándo volvería a funcionar.
It wasn't your wifi. It wasn't your phone. Starting just after five in the afternoon on a Tuesday, WhatsApp stopped working for thousands of people across three countries at once, and the first sign most of them had that something was actually broken came from strangers on the internet saying the same thing was happening to them.
The outage began at 5:03 PM, and within half an hour it had peaked. By 5:33, DownDetector—the service that tracks when major platforms go dark—had logged 576 separate reports from users unable to send messages. The numbers kept climbing. By 5:43 PM, the count had reached 710. People were trying to use WhatsApp Web on their computers and seeing a blank screen with an error message: the page failed to load. Others opened the desktop app only to find themselves staring at a Facebook login screen instead of their conversations. Some couldn't get their phone and computer versions to sync at all, leaving them cut off from their message history on one device or the other.
The breakdown followed a clear pattern. WhatsApp Web—the browser-based version people use at their desks—accounted for 60 percent of the reports. The mobile app itself generated 17 percent of complaints. Another 14 percent involved login failures. The remaining 9 percent scattered across other issues. It was a coordinated failure, the kind that suggests something fundamental had broken in the system's infrastructure rather than a localized glitch.
Mexico bore the brunt of the reports, but the problem wasn't confined to one country. Users in Brazil and the United States were experiencing the same cascade of failures at the same moment. The outage also arrived on a day when Instagram, Meta's other major platform, had already stumbled earlier in the afternoon—though that disruption had been smaller, generating only 119 reports before service returned.
Meta, the parent company that owns WhatsApp, offered no explanation. No statement about what had gone wrong, no timeline for restoration, no apology. The company simply remained silent as the reports accumulated and users across three continents tried to figure out whether to wait it out or find another way to reach the people they needed to contact. The situation was still developing as the evening wore on, with no clear indication of when service would be fully restored or what had caused the collapse in the first place.
Notable Quotes
The page failed to load— Error message users saw when attempting to access WhatsApp Web
The Hearth Conversation Another angle on the story
So this happened to millions of people at the exact same time across three different countries. That's not a coincidence, is it?
No. When something breaks that simultaneously across geographies, it means the failure is upstream—in the core infrastructure that serves all those regions. It's not a local server problem. It's something central.
And they still haven't said what it was?
Not at the time of reporting. Meta just went quiet. That's actually more telling than an explanation would be, because it suggests they were still figuring it out themselves.
Why would WhatsApp Web be hit so much harder than the app itself? Sixty percent of reports versus seventeen?
The web version is probably more fragile. It's running through a browser, it needs to sync with servers, it's doing more work to authenticate and load your entire conversation history. The mobile app is more direct, more optimized. When something breaks, the more complex system breaks first.
Instagram had problems the same day. Is that connected?
Probably not directly—Instagram only had 119 reports, much smaller. But it's the same company, same infrastructure in some ways. When you see multiple Meta services stumbling on the same day, it makes you wonder if there's something systemic they're not telling us about.
What do you do if you can't reach someone and you need to?
You find another way. Call them. Text them. Email. It's a reminder that we've built our entire communication system on one company's servers.