PureSocial Outage History

Started Oct 16, 2026, 05:27 PM UTC· resolved Oct 17, 2026, 06:28 PM UTC

1. investigating Oct 16, 2026, 05:27 PM UTC

   The BSP is reporting degraded performance events, specifically: Some disruptions to messaging 360dialog WhatsApp Business API The BSP is currently working on the issue.

2. investigating Oct 16, 2026, 07:05 PM UTC

   The BSP implemented a temporary solution and continues working with Meta.

3. resolved Oct 17, 2026, 06:28 PM UTC

   Meta detected an unexpected change in messaging permissions that affected one of the BSP's applications. The situation has been resolved, and the service is currently functioning correctly.

Read the full incident report →

Started Aug 23, 2026, 06:07 PM UTC· resolved Aug 26, 2026, 01:52 PM UTC

1. investigating Aug 23, 2026, 06:07 PM UTC

   We are currently experiencing an issue where some X direct messages are not reaching PureSocial/Genesys. This behavior does not appear to affect all accounts. Based on checks performed so far, the root cause may be related to the X platform. The matter is still under investigation, and we will keep you updated on any relevant developments.

2. monitoring Aug 24, 2026, 11:23 PM UTC

   ; X implemented a fix to resolve the issue,

3. monitoring Aug 24, 2026, 11:35 PM UTC

   We are continuing to monitor for any further issues.

4. monitoring Aug 24, 2026, 11:36 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Aug 26, 2026, 01:52 PM UTC

   X informed us that they identified an error in a configuration applied to the PureSocial account; this error generated HTTP 503 responses during direct message (DM) queries and affected message delivery. According to the information provided by X, the issue occurred between August 21, 2026, at 23:04 UTC and August 24, 2026, at 16:08 UTC, at which point the necessary correction was made. The configuration has now been corrected by X.

Read the full incident report →

Started Jul 08, 2026, 02:00 PM UTC· resolved Jul 12, 2026, 05:49 PM UTC

1. investigating Jul 08, 2026, 02:00 PM UTC

   We are currently experiencing issues processing private messages on Channel X (formerly Twitter). Our team is investigating the cause of this behavior to identify the issue and implement a solution as soon as possible. We will keep you updated on any relevant developments or once the incident has been resolved. Thank you for your understanding.

2. identified Jul 08, 2026, 02:19 PM UTC

   The incident did not originate from a PureSocial platform failure, but rather from a change made by X to their service, which was implemented without prior notice. While this change was in progress, the service exhibited intermittent behavior, resulting in the temporary rejection of some requests and affecting the integration's functionality. The development team is working on a solution.

3. monitoring Jul 08, 2026, 08:49 PM UTC

   An improvement was implemented to correct the impact caused by the changes made by X. The solution is currently being monitored to confirm its proper functioning and stability.

4. resolved Jul 12, 2026, 05:49 PM UTC

   The development team made adjustments to changes made by X, resolving the issue.

Read the full incident report →

Started Jun 12, 2026, 02:09 PM UTC· resolved Jun 14, 2026, 09:49 PM UTC

1. investigating Jun 12, 2026, 02:09 PM UTC

   WhatsApp is experiencing an outage; messages cannot be replied to. The problem is being investigated and will be resolved as soon as possible.

2. investigating Jun 12, 2026, 02:15 PM UTC

   BSP 360 Dialog reported a Meta issue June 12, 2026 at 8:08 AM Meta is returning a 500 Internal Server Error while sending messages via the Meta API. We have reported the issue to the Meta Engineers to investigate it. We will provide an update as soon as we hear from Meta Engineers. We are monitoring the situation closely and waiting on Meta.

3. identified Jun 12, 2026, 02:48 PM UTC

   Meta Engineers have confirmed they are currently experiencing high disruptions impacting the WhatsApp Cloud API. https://metastatus.com/whatsapp-business-api

4. monitoring Jun 12, 2026, 05:30 PM UTC

   Me¿ta has informed tha the issue was Resolved Resolved Jun 12 2026 11:17 AM CST We have recovered from an earlier outage impacting Cloud API - Calling, and services have now been restored. We apologize for any inconvenience that this may have caused.

5. resolved Jun 14, 2026, 09:49 PM UTC

   Meta resolved the issue June 12, 2026 at 8:08 AM Meta is returning a 500 Internal Server Error while sending messages via the Meta API.

Read the full incident report →

Started May 24, 2026, 04:09 PM UTC· resolved Jun 02, 2026, 05:58 PM UTC

1. investigating May 24, 2026, 04:09 PM UTC

   We are informing you that customers using Instagram Wall are currently experiencing an issue receiving messages. Based on our initial assessments, Meta appears to have made changes to the policy of the standard used by the integration without prior notice, which is causing the observed blockage. Our team is already working on analyzing and resolving this issue.

2. monitoring May 24, 2026, 06:00 PM UTC

   A temporary workaround has been implemented to allow interactions to resume while Meta provides or defines the new conditions applicable to posts. With this workaround in place, it is now possible to receive and reply to posts; however, the link associated with the post or comment is currently not displaying correctly.

3. resolved Jun 02, 2026, 05:58 PM UTC

   the incident has been resolved

Read the full incident report →

Started May 14, 2026, 02:02 PM UTC· resolved May 14, 2026, 06:06 PM UTC

1. investigating May 14, 2026, 02:02 PM UTC

   t has been reported that the BSP 360Dialog is experiencing a Performance Degradation event, which may cause some interactions to have sending/receiving problems. The BSP is investigating the event.

2. monitoring May 14, 2026, 02:21 PM UTC

   The BSP has reported that the incident has been resolved.

3. monitoring May 14, 2026, 02:29 PM UTC

   The BSP has reported that the incident has been resolved.

4. resolved May 14, 2026, 06:06 PM UTC

   May 14, 2026 at 8:05 AM The issue is now resolved.

Read the full incident report →

Started Mar 30, 2026, 04:10 PM UTC· resolved Apr 12, 2026, 01:58 AM UTC

1. investigating Mar 30, 2026, 04:10 PM UTC

   Delays were detected in the processing of some WhatsApp interactions. The development team is working to determine the cause and resolve this issue as soon as possible.

2. investigating Mar 30, 2026, 04:51 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 31, 2026, 04:55 PM UTC

   Se aplicaron medidas de contención de manera oportuna y, desde entonces, el servicio ha operado con normalidad. Asimismo, se ha identificado la causa raíz del incidente y se tiene previsto implementar un cambio correctivo orientado a eliminar dicha causa y prevenir su recurrencia.

4. resolved Apr 12, 2026, 01:58 AM UTC

   The incident has been resolved. The root cause was identified as contention caused by concurrent write operations on the same document, triggered by multiple simultaneous update operations. On March 31, changes were implemented to the data model structure with the aim of improving consistency and preventing this type of concurrency conflict in the future.

Read the full incident report →

Started Mar 24, 2026, 07:44 PM UTC· resolved Mar 27, 2026, 04:29 PM UTC

1. investigating Mar 24, 2026, 07:44 PM UTC

   We are reporting a delay in the processing of some interactions. We are working to determine the cause and resolve this issue as soon as possible.

2. monitoring Mar 24, 2026, 09:28 PM UTC

   Some actions will be applied and the processing of messages has been normalized, but the cause is still being investigated

3. resolved Mar 27, 2026, 04:29 PM UTC

   The incident was caused by multiple processes running simultaneously on the same element, which caused congestion in the system. Operational adjustments will be made to reduce the accumulated load and normalize the process flow. These actions will gradually stabilize the platform

Read the full incident report →

Started Jan 20, 2026, 04:39 PM UTC· resolved Jan 21, 2026, 03:24 AM UTC

1. monitoring Jan 20, 2026, 04:39 PM UTC

   Despite 360Dialog indicating on their status page that the issue has been mitigated, we are still observing the reported behavior. At this time, the incident has not been fully resolved and the issue persists. We will remain under active monitoring and continue tracking the situation until full service stability is confirmed. Any relevant updates will be communicated accordingly. You can check the official 360Dialog status: https://status.360dialog.com/cmkml9hhl000x55k50jjp4rkb

2. resolved Jan 21, 2026, 03:24 AM UTC

   January 20, 2026 at 3:27 PM Meta has applied a fix. We'll monitor it closely. A public RCA will be published on this status page as soon as all details are made available by Meta. https://status.360dialog.com/

Read the full incident report →

Started Dec 10, 2025, 12:30 PM UTC· resolved Dec 10, 2025, 12:30 PM UTC

1. resolved Dec 10, 2025, 07:30 PM UTC

   An unannounced change was identified in the SAE1 (Americas – São Paulo) region of Genesys Cloud, where a new attribute was added to outbound message events delivered through the Open Messaging webhook. This modification altered the expected payload structure and caused our platform to discard some events, resulting in processing errors limited exclusively to this region. The necessary adjustments have been implemented, and the service is now fully restored. No impact was observed in any other regions.

Read the full incident report →

Started Apr 22, 2025, 04:39 PM UTC· resolved Apr 25, 2025, 07:47 PM UTC

1. investigating Apr 22, 2025, 04:39 PM UTC

   Dear Customers, We are experiencing disruptions due to intermittent messages causing messages to accumulate in the queue. Our engineering teams are investigating the issue. We reiterate our commitment to providing better service. Sincerely,

2. investigating Apr 22, 2025, 09:53 PM UTC

   Dear Customers: We inform you that the queuing event has been contained, no delay in outgoing messages has been identified, and our team continues to investigate the root cause of the intermittency. We reiterate our commitment to providing better service. Sincerely,

3. monitoring Apr 23, 2025, 04:21 AM UTC

   Dear Customers, Please note that the queue issue has been controlled, no further delays in outgoing messages have been detected, and we are continuing to monitor message delivery. Our team is continuing to investigate the root cause of the intermittency. We reiterate our commitment to providing better service. Sincerely,

4. resolved Apr 25, 2025, 07:47 PM UTC

   Dear Customers, The incident related to message queue delays has been resolved. Message traffic has returned to normal parameters, and no further anomalies have been observed during the monitoring period Stability has been confirmed, and all systems are operating as expected We reiterate our commitment to providing better service Sincerely,

Read the full incident report →

Started Mar 13, 2025, 04:13 PM UTC· resolved Mar 26, 2025, 10:18 PM UTC

1. investigating Mar 13, 2025, 04:13 PM UTC

   Dear Customers, We have identified intermittent messages that caused a message queue. It is important to note that we are no longer experiencing message delays. We are continuing to investigate the cause. We reiterate our commitment to providing better service. Sincerely

2. investigating Mar 13, 2025, 08:20 PM UTC

   Dear Customers, We are informing you of the ongoing investigation related to the previously reported intermittent message issues. While we are no longer experiencing message delays, our team is still actively working to identify the root cause of the message queue behavior. We understand the importance of reliable service and assure you that identifying the root cause remains our top priority. We will keep you informed as soon as we have more information. Thank you for your patience and continued trust in our services. Sincerely,

3. resolved Mar 26, 2025, 10:18 PM UTC

   Dear Customers, The intermittent message issues have been fully resolved. Our team successfully restored service on the same day of the incident, and we have continued monitoring system performance to ensure stability. We appreciate your patience and trust. If you need further assistance, our support team is available to help. Best regards

Read the full incident report →

Started Feb 05, 2025, 12:40 AM UTC· resolved Feb 05, 2025, 02:23 PM UTC

1. investigating Feb 05, 2025, 12:40 AM UTC

   BSP is aware of an issue affecting Cloud API numbers, in particular the messaging service for incoming messages. The BSP engineering team is actively investigating the root cause. We will share an update as soon as more information is available.

2. investigating Feb 05, 2025, 05:25 AM UTC

   We are continuing to investigate this issue.

3. identified Feb 05, 2025, 12:01 PM UTC

   Our BSP has identified the cause of message delays affecting Cloud API numbers as a Meta issue, and we are awaiting their response. Meta has acknowledged this issue on their status page: "Our engineering teams have identified the root cause of the medium disruptions impacting webhooks on WhatsApp Cloud API. We are currently deploying the fix, and the expected deployment time is 8 hours. We will provide another update within 4 hours or sooner if additional information becomes available." https://metastatus.com/ His engineering team is preparing a workaround to mitigate the issue for WhatsApp Business Accounts with a single number until Meta resolves it on their side

4. resolved Feb 05, 2025, 02:23 PM UTC

   Meta has announced that they have resolved the issue with webhooks in WhatsApp Cloud API via the following post on their portal. https://metastatus.com/whatsapp-business-api “We have recovered from an earlier outage impacting Cloud API, and services have now been restored. We apologize for any inconvenience that this may have caused.”

Read the full incident report →

Started Dec 11, 2024, 06:56 PM UTC· resolved Dec 12, 2024, 03:46 AM UTC

1. investigating Dec 11, 2024, 06:56 PM UTC

   Dear, We would like to inform you that there is currently a general outage in Meta services. This could affect platforms such as Facebook, Instagram and WhatsApp. We are aware of the inconvenience this situation may cause and we appreciate your understanding while the Meta technical team works on its resolution. We appreciate your patience and understanding.

2. investigating Dec 11, 2024, 07:03 PM UTC

   The META team is reporting that they are currently experiencing a major outage affecting message delivery on their platforms. This issue began at 9:58 AM PST. The META engineering team is currently investigating the issue. We will provide another update within 1 hour or sooner if additional information becomes available.

3. investigating Dec 11, 2024, 10:14 PM UTC

   The META team reports that they are continuing to work on service recovery

4. resolved Dec 12, 2024, 03:46 AM UTC

   Dear customers We would like to inform you that the META team has recovered from previous service interruptions. We apologize for the inconvenience. We reiterate our commitment to providing the best service Best regards

Read the full incident report →