Some disruptions to WhatsApp API Messaging Service

On behalf of 360Dialog, a workaround has been implemented to mitigate the impact of the reported issue.
Meta has acknowledged an issue on their side and confirmed that it is affecting multiple WhatsApp BSPs. Meta’s engineering team is currently investigating the root cause.
As the service has been stabilized through the applied solution, this incident is being marked as resolved for the time being.
A public Root Cause Analysis (RCA) will be published on this status page as soon as all details are made available by Meta.

Good afternoon, 360Dialog indicates that today, January 20, 2026, at 15:37 UTC,
Meta modified the /media_id endpoint by introducing a fragmented transfer encoding response. This caused temporary issues retrieving media. We will soon publish a workaround to address this change. If you want to consult the official page https://status.360dialog.com/cmkml9hhl000x55k50jjp4rkb

Although 360Dialog has implemented a fix, they are still receiving reports of errors when sending or receiving multimedia messages in certain cases. 360Dialog is actively investigating. See https://status.360dialog.com/

The provider 360Dialog is implementing a solution and they are seeing signs of recovery. We are monitoring the situation and will update the information soon. In the meantime, you can check https://status.360dialog.com/

The 360Dialog team has identified the issue and is working to resolve it. We will update this information as soon as possible. In the meantime, you can continue to track the incident at https://status.360dialog.com/

The 360Dialog BSP is experiencing some issues with the WhatsApp API messaging service. This may affect the functionality of PureSocial. The BSP is investigating and working to resolve the problem.
You can check the BSP status at https://status.360dialog.com/