PureSocial incident
Problems processing private messages on Channel X
PureSocial experienced a notice incident on July 8, 2026 affecting Twitter Channel, lasting 4d 3h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- 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.
- resolved Jul 12, 2026, 05:49 PM UTC
The development team made adjustments to changes made by X, resolving the issue.