Buffer Status · History · Incident #5465
RESOLVEDIssue with Threads comments
Major · Started Jul 13, 2026 · 8:48 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Buffer Status · History · Incident #5465
RESOLVEDMajor · Started Jul 13, 2026 · 8:48 AM
Duration
6d 1h 31m
Severity
Major
Detection lead
—
User reports
—
Summary
This issue has been resolved, and new Threads comments should now be delivered normally. Our backup mechanism has also recovered recent comments that were delayed during the incident. We sincerely apologise for the disruption.
Started
Jul 13, 2026 · 8:48 AM
Resolved
Jul 19, 2026 · 10:20 AM
Duration
6d 1h 31m
Severity
Major
Event timeline
Investigating
Jul 13 · 8:48 AM BufferWe're currently experiencing a delay while updating new comments from Threads API. Our engineering team is currently investigating the cause, and we'll provide updates here as soon as we know more.
Identified
Jul 13 · 10:39 AM BufferWe've confirmed that an issue with the Meta API is causing the delay, and we’re working with the Threads/Meta team to restore normal delivery of new comments. In the meantime, as a mitigation, we’ve enabled a backup mechanism to help recover recent comments. You can also trigger a manual sync by visiting the Threads channel page in Community or clicking **Sync now**.
Resolved
Jul 19 · 10:20 AM BufferThis issue has been resolved, and new Threads comments should now be delivered normally. Our backup mechanism has also recovered recent comments that were delayed during the incident. We sincerely apologise for the disruption.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026