WhatsApp Media Sending Instability
Timeline · 4 updates
- investigating Jun 16, 2026, 04:10 PM UTC
We are investigating an issue affecting message sending through Blip Desk. Customers may experience failures or delays when sending messages. Our technical teams are actively investigating the scenario and working to better understand the scope and impact. We will provide a new update as soon as more information becomes available.
- investigating Jun 16, 2026, 04:37 PM UTC
We continue investigating an issue affecting media message delivery on the WhatsApp channel. The scenario remains unchanged, and some customers may still experience failures when sending media messages. Our teams remain actively engaged in the investigation and are closely monitoring the situation. A high-priority case has been opened with the service provider involved, while additional analyses continue in parallel. We will provide further updates as soon as new information becomes available.
- monitoring Jun 16, 2026, 05:09 PM UTC
We have observed a significant reduction in the errors associated with this incident, and recent tests involving media message delivery through the WhatsApp channel have been successful. While the service behavior indicates signs of recovery, we are still awaiting official confirmation from the service provider regarding the root cause and full resolution of the issue. Our teams continue to closely monitor the situation and will provide further updates as soon as additional information becomes available.
- resolved Jun 16, 2026, 07:03 PM UTC
The incident affecting media message delivery through the WhatsApp channel has been resolved. We observed a significant reduction in errors starting at approximately 13:50 (GMT-3), and subsequent validation tests were completed successfully without further issues. After further investigation, Meta informed us that an internal issue related to its Forward Proxy service had been identified and resolved. The service has remained stable since then, and no new impacts have been observed. This incident is now considered resolved.