Agora Pulse Outage History

Started Oct 08, 2026, 11:06 AM UTC· resolved Oct 09, 2026, 04:22 PM UTC

1. identified Oct 08, 2026, 11:06 AM UTC

   We’re currently monitoring an issue with Youtube Tokens, the Youtube API is currently unstable and can give wrong information about the token health. We are working toward a solution internally to prevent as many errors as possible.

2. identified Oct 08, 2026, 05:29 PM UTC

   We’re currently monitoring an issue with Youtube Tokens, the Youtube API is currently unstable and can give wrong information about the token health. We are working toward a solution internally to prevent as many errors as possible.

3. monitoring Oct 09, 2026, 08:23 AM UTC

   We're continuing to keep an eye on this situation. The error rate is low, but we want to ensure YouTube connections are working as expected for all users before marking this issue as resolved.

4. resolved Oct 09, 2026, 04:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 28, 2026, 02:50 PM UTC· resolved Sep 29, 2026, 03:32 PM UTC

1. investigating Sep 28, 2026, 02:50 PM UTC

   We received several reports of the app being slow within the publishing part of the tool : Opening posts, create and save posts, upload medias. We are investigating the issue.

2. identified Sep 28, 2026, 04:12 PM UTC

   The issue has been identified and a fix is being implemented. Reloading the page has helped users who have seen temporary loading issues. We will update you as we learn more.

3. monitoring Sep 28, 2026, 06:27 PM UTC

   Performance has improved and we continue to monitor the situation. If you continue to experience any issues, please contact Support.

4. resolved Sep 29, 2026, 03:32 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 23, 2026, 07:19 AM UTC· resolved Sep 23, 2026, 02:47 PM UTC

1. investigating Sep 23, 2026, 07:19 AM UTC

   Links are well published, but they are not displayed within Facebook posts preview. We are currently investigating the issue.

2. resolved Sep 23, 2026, 02:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 16, 2026, 03:51 PM UTC· resolved Sep 16, 2026, 06:54 PM UTC

1. identified Sep 16, 2026, 03:51 PM UTC

   We are currently experiencing an issue affecting Agorapulse Listening. Users are unable to create new keyword searches or update existing keyword searches across Facebook, Instagram, YouTube, Reddit, and Web sources. Ingestion of new listening data is paused on these sources. Our engineering team is actively investigating the underlying cause.

2. monitoring Sep 16, 2026, 05:37 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 16, 2026, 06:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 22, 2026, 02:39 PM UTC· resolved Jul 22, 2026, 07:13 PM UTC

1. investigating Jul 22, 2026, 02:39 PM UTC

   Meta is currently experiencing a partial outage. As a result, you may encounter errors when replying to Facebook and Instagram messages, as well as delays in item syncing. We are monitoring the situation and will provide updates as new information becomes available.

2. monitoring Jul 22, 2026, 05:21 PM UTC

   Error rates have significantly decreased. Any Facebook or Instagram message replies that previously failed can now be retried. We are continuing to monitor the situation closely to ensure full stability.

3. resolved Jul 22, 2026, 07:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 07, 2026, 03:30 PM UTC· resolved Jul 08, 2026, 04:06 PM UTC

1. investigating Jul 07, 2026, 03:30 PM UTC

   We are currently investigating this issue.

2. monitoring Jul 08, 2026, 09:33 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 08, 2026, 04:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2026, 03:37 PM UTC· resolved Jul 02, 2026, 02:37 PM UTC

1. investigating Jul 01, 2026, 03:37 PM UTC

   We are currently facing an issue regarding sentiment classification of inbox elements appearing as undefined or loading status, we are investigating the issue.

2. monitoring Jul 02, 2026, 09:17 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 02, 2026, 02:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 03:55 PM UTC· resolved Jun 30, 2026, 01:17 PM UTC

1. investigating Jun 29, 2026, 03:55 PM UTC

   We are currently facing an issue with the Sentiment classification of inbox elements. We are currently investigationg the issue.

2. monitoring Jun 30, 2026, 09:20 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jun 30, 2026, 01:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 12, 2026, 02:02 PM UTC· resolved Jun 12, 2026, 07:10 PM UTC

1. identified Jun 12, 2026, 02:02 PM UTC

   Meta is experiencing an outage, which is affecting their native sites and API functionality since around 1:30pm UTC. A common error seen in publishing and inbox replies is: `An unknown error has occurred` for Instagram, Facebook & Threads. We will monitor sites such as https://downdetector.com/ and https://metastatus.com/ for updates and share once we know more.

2. monitoring Jun 12, 2026, 05:04 PM UTC

   Error rates are improving, it seems Meta has implemented some fixes. We will continue to closely monitor the situation. Thank you for your patience.

3. resolved Jun 12, 2026, 07:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 02, 2026, 04:54 PM UTC· resolved Jun 03, 2026, 02:23 PM UTC

1. investigating Jun 02, 2026, 04:54 PM UTC

   Inbox replies to Twitter DMs are displaying a "Message is null" error, however the reply is still being sent successfully. Our team is investigating the root cause. If you see this error, your reply has still been sent. We advise against resending to avoid duplicate messages. Thank you for your patience, we will update as we know more.

2. monitoring Jun 02, 2026, 08:11 PM UTC

   The rate of these errors has decreased, we will continue to monitor the situation. The root cause was an incorrect response from X/Twitter's API when sending direct messages.

3. resolved Jun 03, 2026, 02:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 25, 2026, 02:10 AM UTC· resolved Jun 01, 2026, 02:01 PM UTC

1. investigating May 25, 2026, 02:10 AM UTC

   We are currently seeing failures when publishing Instagram Reels. Video posts are remaining in a pending state for an extended period before failing with the following error: "Received Facebook error response of type GraphMethodException: Authorization Error (code 100, subcode 33)" We are actively investigating this issue and will post an update as soon as we have more information.

2. identified May 25, 2026, 07:45 AM UTC

   We can confirm that the issue comes from Meta's API directly, other competitor tools are impacted as well, we are monitoring the situation and will post an update as soon as we have more information.

3. identified May 27, 2026, 09:57 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring May 28, 2026, 01:46 PM UTC

   The error rate is back to normal and the issue is resolved, we are still investigating with Meta and trying to get informations about the issue.

5. resolved Jun 01, 2026, 02:01 PM UTC

   Publishing 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.

Read the full incident report →

Started May 08, 2026, 02:58 PM UTC· resolved May 12, 2026, 07:25 PM UTC

1. investigating May 08, 2026, 02:58 PM UTC

   PDF exports from Reports are delayed and may take several hours to arrive. This does not affect CSV or other formats, which are working normally. We're sorry for the inconvenience and will update this area as we get more information.

2. monitoring May 11, 2026, 01:09 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring May 12, 2026, 01:46 PM UTC

   While improvements were made, some report exports are still delayed. We're sorry for the inconvenience this may cause, but are actively working on a solution.

4. resolved May 12, 2026, 07:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 01, 2026, 04:22 PM UTC· resolved May 06, 2026, 03:30 PM UTC

1. investigating May 01, 2026, 04:22 PM UTC

   We are currently investigating an increase in errors affecting some Facebook post publishing attempts. Posts are typically published successfully despite the error message returned from Meta: `Received Facebook error response of type null: Please reduce the amount of data you're asking for, then retry your request (code 1, subcode null)` If a post does not publish, manually retrying the post will usually resolve the issue. We will update you as we learn more, see updates from Meta, or notice improvements.

2. monitoring May 01, 2026, 06:55 PM UTC

   We've confirmed this issue extends to other 3rd party Meta publishing integrations. We'll continue monitoring.

3. resolved May 06, 2026, 03:30 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 29, 2026, 07:01 AM UTC· resolved Apr 29, 2026, 07:08 PM UTC

1. investigating Apr 29, 2026, 07:01 AM UTC

   We are receiving more reports of Instagram post failing with the following errors : - Only photo or video can be accepted as media type. (code 9004, subcode 2207052) 'Media download has failed. The media URI doesn't meet our requirements. - Please check the limitations section in our development document for more information: https://developers.facebook.com/docs/instagram-platform/instagram-graph-api/reference/ig-user/media#creating' - Video container status error, “Media upload has failed” (error code 2207076). We are currently investigating the issue.

2. monitoring Apr 29, 2026, 02:44 PM UTC

   The issue is confirmed to be originating from Meta directly. We are no longer seeing any occurences of the errors since 10am Paris time. We are currently monitoring the situation.

3. resolved Apr 29, 2026, 07:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 27, 2026, 02:41 AM UTC· resolved Apr 27, 2026, 08:29 AM UTC

1. investigating Apr 27, 2026, 02:41 AM UTC

   We’re seeing reports of Instagram image and video posts failing to publish. Our team is investigating this closely to identify the cause. The errors reported are: For video posts, “Media upload has failed (2207076)"; For image posts, "Only photo or video can be accepted as media type. (code 9004, subcode 2207052) 'Media download has failed. The media URI doesn't meet our requirements" Some posts are publishing normally. If any posts failed during this period, use the “Retry Now” button to republish. We’re keeping a close eye on this and will share updates as we learn more.

2. resolved Apr 27, 2026, 08:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 15, 2026, 07:59 PM UTC· resolved Apr 15, 2026, 10:16 PM UTC

1. investigating Apr 15, 2026, 07:59 PM UTC

   We're investigating an issue affecting LinkedIn post publishing. Users may see publishing failures when attempting to post content to LinkedIn.

2. identified Apr 15, 2026, 08:30 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 15, 2026, 08:44 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 15, 2026, 10:16 PM UTC

   The 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 social media scheduling.

Read the full incident report →

Started Mar 26, 2026, 01:34 PM UTC· resolved Apr 01, 2026, 03:18 PM UTC

1. identified Mar 26, 2026, 01:34 PM UTC

   We’re seeing reports of TikTok video posts stuck in a 'pending' state. It looks like a wider issue with TikTok's API. Posts affected eventually fail with 'This post took too much time to compute and failed'. We will update as we know more.

2. monitoring Mar 27, 2026, 03:57 PM UTC

   TikTok publishing rates have improved, but we will continue to monitor the situation.

3. resolved Apr 01, 2026, 03:18 PM UTC

   TikTok publishing is working as expected. Any affected posts can be retried. Thank you for your patience!

Read the full incident report →

Started Mar 13, 2026, 03:21 PM UTC· resolved Mar 17, 2026, 10:09 AM UTC

1. investigating Mar 13, 2026, 03:21 PM UTC

   We are currently investigating an issue where we see TikTok post stuck pending, ultimately failing with the error : This post took too much time to compute and failed. We will give update as soon as we have more information about this issue.

2. monitoring Mar 16, 2026, 08:51 AM UTC

   We’ve analyzed the logs and confirmed that the videos are successfully reaching TikTok, however we detected a change in how TikTok is currently moderating content which was causing posts to fail.

3. monitoring Mar 16, 2026, 09:10 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Mar 17, 2026, 10:09 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 12, 2026, 01:18 PM UTC· resolved Mar 13, 2026, 02:44 PM UTC

1. investigating Mar 12, 2026, 01:18 PM UTC

   We are investigating reports of Facebook video posts failing with an error from Meta: There was a problem uploading your video file. Please try again with another file". (code 6000) We will provide updates as soon as we have more information.

2. identified Mar 12, 2026, 03:48 PM UTC

   While we continue to see Facebook video posts failing, others using the Meta API have reported the same. We are continuing to monitor the situation and will update as we learn more.

3. monitoring Mar 13, 2026, 09:57 AM UTC

   We are not seeing anymore errors within or monitoring tool for this issue, we keep monitoring the situation on our side.

4. resolved Mar 13, 2026, 02:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2026, 08:02 AM UTC· resolved Mar 11, 2026, 08:48 AM UTC

1. investigating Mar 11, 2026, 08:02 AM UTC

   Some users are seeing an OpenSearch error when they try to reply to Instagram messages or post comments from the Inbox. The error prevents them from sending any response.

2. resolved Mar 11, 2026, 08:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 10, 2026, 10:20 AM UTC· resolved Mar 10, 2026, 11:39 AM UTC

1. investigating Mar 10, 2026, 10:20 AM UTC

   We are currently investigating this issue.

2. identified Mar 10, 2026, 10:32 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Mar 10, 2026, 11:15 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Mar 10, 2026, 11:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 10:08 AM UTC· resolved Feb 27, 2026, 10:32 AM UTC

1. investigating Feb 26, 2026, 10:08 AM UTC

   Instagram video posts (Reels) are currently failing with this error : Error on publishing, Invalid parameter (code 100, subcode 2207089) "Carousel Item Cannot Be Published Standalone – Media created with media_type=VIDEO is a carousel item and cannot be published as a standalone post. To publish a standalone video, use media_type=REELS instead." We are currently investigating the issue.

2. identified Feb 26, 2026, 01:20 PM UTC

   The issue has been identified and is coming from Meta's API directly. We’re continuing to monitor error rates and will share updates as we learn more.

3. identified Feb 26, 2026, 03:43 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Feb 27, 2026, 10:32 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 24, 2026, 12:02 PM UTC· resolved Mar 06, 2026, 07:08 PM UTC

1. identified Feb 24, 2026, 12:02 PM UTC

   We identified the source of the issue which is coming from the Meta API. We’re continuing to monitor error rates and will share updates as we learn more.

2. identified Feb 25, 2026, 05:20 PM UTC

   We have reached out to Meta via a direct support ticket, and their team is currently investigating the root cause within their API. Current Error Message: An unexpected error has occurred. Please retry your request later. (Code 2) We will provide further updates as soon as we receive word from Meta's support team.

3. monitoring Mar 04, 2026, 09:44 PM UTC

   We are continuing to monitor the situation. The error is still occurring for some users, but occurrences have decreased in recent days. We will provide further updates as soon as we hear from Meta’s support team.

4. resolved Mar 06, 2026, 07:08 PM UTC

   While 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.

Read the full incident report →

Started Jan 30, 2026, 02:01 PM UTC· resolved Jan 31, 2026, 01:57 AM UTC

1. identified Jan 30, 2026, 02:01 PM UTC

   The Threads API is currently experiencing a disruption where image posts are failing with the error: "An unknown error has occurred." Our team is monitoring the situation and waiting for a fix from Meta.

2. monitoring Jan 30, 2026, 06:52 PM UTC

   Meta has acknowledged the issue on their status page, we are continuing to monitor the situation.

3. resolved Jan 31, 2026, 01:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 26, 2026, 02:02 PM UTC· resolved Jan 27, 2026, 04:36 PM UTC

1. investigating Jan 26, 2026, 02:02 PM UTC

   We opened a direct support ticket with LinkedIn as the issue appears to come from their API directly.

2. identified Jan 27, 2026, 03:12 PM UTC

   LinkedIn has confirmed the issue and escalated it to their engineering team. We will continue to provide updates as new information becomes available

3. resolved Jan 27, 2026, 04:36 PM UTC

   LinkedIn 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.

Read the full incident report →