Agorapulse Outage History
36 incidents recorded over the last 365 days, 36 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Agorapulse Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 8, 2026 | Youtube token issueThis incident has been resolved. | 29h 15m | Resolved |
| Sep 28, 2026 | App slowness within the publishing part of the toolThis incident has been resolved. | 24h 41m | Resolved |
| Sep 23, 2026 | Links are not displayed within Facebook posts previewThis incident has been resolved. | 7h 27m | Resolved |
| Sep 16, 2026 | Listening Search Creation, Updates, and Sync on Keyword SearchesThis incident has been resolved. | 3h 2m | Resolved |
| Jul 22, 2026 | Meta outage affecting Facebook and Instagram inboxesThis incident has been resolved. | 4h 33m | Resolved |
| Jul 7, 2026 | Unresponsive Calendar when duplicating postsThis incident has been resolved. | 24h 36m | Resolved |
| Jul 1, 2026 | Undefined sentiment in all inboxesThis incident has been resolved. | 23h 0m | Resolved |
| Jun 29, 2026 | Undefined sentiment within all inboxesThis incident has been resolved. | 21h 22m | Resolved |
| Jun 12, 2026 | Meta OutageThis incident has been resolved. | 5h 8m | Resolved |
| Jun 2, 2026 | Replies to X/Twitter DMs are displaying a "Message is null" error, but sent successfully.This incident has been resolved. | 21h 29m | Resolved |
| May 25, 2026 | Instagram Reels - Publishing FailuresPublishing failures affecting Instagram Reels are no longer occurring. The root cause originated in Meta's API. Meta did not provide a formal explanation, but error rates remain normal. | 179h 51m | Resolved |
| May 8, 2026 | Reports: Delayed PDF ExportsThis incident has been resolved. | 100h 27m | Resolved |
| May 1, 2026 | Increase in Facebook Publishing Errors: "reduce the amount of data"This incident has been resolved. | 119h 7m | Resolved |
| Apr 29, 2026 | Instagram publishing error (code 9004, subcode 2207052) // Video container status error, “Media upload has failed” (error code 2207076).This incident has been resolved. | 12h 6m | Resolved |
| Apr 27, 2026 | Instagram Publishing ErrorThis incident has been resolved. | 5h 48m | Resolved |
| Apr 15, 2026 | LinkedIn publishing errorsThe issue affecting LinkedIn post publishing has been fully resolved. Our team has confirmed that post-delivery is back to normal and all systems are operational. We apologize for any disruption this caused to your… | 2h 16m | Resolved |
| Mar 26, 2026 | TikTok Posts Stuck PendingTikTok publishing is working as expected. Any affected posts can be retried. Thank you for your patience! | 145h 44m | Resolved |
| Mar 25, 2026 | TikTok Posts Stuck PendingFollowing the earlier reports of TikTok posts being stuck in 'pending,' we can confirm that the issue has been resolved. Our team has verified that new posts are uploading successfully. Please retry your posts. | 7h 51m | Resolved |
| Mar 13, 2026 | TikTok post stuck pendingThis incident has been resolved. | 90h 48m | Resolved |
| Mar 12, 2026 | Facebook Video Publishing FailuresThis incident has been resolved. | 25h 26m | Resolved |
| Mar 11, 2026 | Unable to reply to Instagram messages or post commentsThis incident has been resolved. | 46 min | Resolved |
| Mar 10, 2026 | Unable to see Private messagesThis incident has been resolved. | 1h 19m | Resolved |
| Feb 26, 2026 | Instagram video posts failing with error (code 100, subcode 2207089)This incident has been resolved. | 24h 23m | Resolved |
| Feb 24, 2026 | Meta API issue impacting some Instagram postsWhile Meta hasn't provided root cause details, the issue has improved since our initial report to them. We're monitoring for recurrence. Most affected users resolve this by retrying their post after a few minutes. | 247h 5m | Resolved |
| Jan 30, 2026 | Threads Image Publishing IssuesThis incident has been resolved. | 11h 55m | Resolved |
| Jan 26, 2026 | No LinkedIn followers data received since 15th of JanuaryLinkedIn has acknowledged the matter and assigned it to their engineering department. We will maintain regular communication with their team until a full resolution is reached. | 26h 34m | Resolved |
| Jan 26, 2026 | Issue Publishing Posts to TikTokPublishing to TikTok has returned to normal. If your account lost its connection during the API outage, it will need to be renewed to resume publishing normally. Thank you for your patience. | 10h 23m | Resolved |
| Jan 20, 2026 | All profiles selected after openeing a post in the CalendarThis incident has been resolved. | 9h 2m | Resolved |
| Jan 8, 2026 | Delayed Inbox ItemsThis incident has been resolved. | 13h 45m | Resolved |
| Jan 6, 2026 | DM's appearing as encrypted in inboxThis incident has been resolved. | 12 min | Resolved |
| Dec 16, 2025 | Issue Publishing Posts to LinkedInAs the LinkedIn error rate has continued to drop, we are marking this as Resolved. Thank you for your patience. | 51 min | Resolved |
| Dec 3, 2025 | Unable to edit subscriptionThis incident has been resolved. | 3h 17m | Resolved |
| Dec 3, 2025 | Subscription Access Interruption (Billing Error)This incident has been resolved. | 4h 50m | Resolved |
| Nov 26, 2025 | Old post published across multiple social profilesThis incident has been resolved. | 1h 11m | Resolved |
| Nov 18, 2025 | Cloudflare OutageThis incident has been resolved. | 2h 37m | Resolved |
| Nov 12, 2025 | Facebook Reels failing to publish due to a Meta issueThis incident has been resolved. | 121h 42m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Agorapulse incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Agorapulse Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Agorapulse acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Agorapulse outage in this window ran 10d 7h, against a mean recovery of 1d 13h. If you depend on Agorapulse in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.