Resolved after 2 days 19 hours, affecting Twitter Channel, on August 23, 2026.
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.
Affected components
Update timeline
- 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.
- monitoring Aug 24, 2026, 11:23 PM UTC
; X implemented a fix to resolve the issue,
- monitoring Aug 24, 2026, 11:35 PM UTC
We are continuing to monitor for any further issues.
- monitoring Aug 24, 2026, 11:36 PM UTC
We are continuing to monitor for any further issues.
- 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.
Your product runs on more than PureSocial
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services