Ayrshare Status - Incident history https://status.ayrshare.com Ayrshare Wed, 20 May 2026 14:12:10 +0000 Industry reports about LinkedIn Connection Issues Type: Incident Duration: 3 hours and 40 minutes Affected Components: LinkedIn May 20, 14:12:10 GMT+0 - Investigating - Some other vendors are reporting problems connecting Linkedin accounts today. We haven't seen any issues with Ayrshare customers yet, but please let us know if you are having any trouble connecting new accounts to Linkedin. May 20, 17:52:05 GMT+0 - Resolved - We didn't have any issues reported by customers for this, so we're closing this note. Type: Incident

Duration: 3 hours and 40 minutes

Affected Components:

<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>14:12:10</var> GMT+0</small><br><strong>Investigating</strong> - Some other vendors are reporting problems connecting Linkedin accounts today. We haven't seen any issues with Ayrshare customers yet, but please let us know if you are having any trouble connecting new accounts to Linkedin. .</p> <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>17:52:05</var> GMT+0</small><br><strong>Resolved</strong> - We didn't have any issues reported by customers for this, so we're closing this note..</p> ]]> Wed, 20 May 2026 14:12:10 +0000 https://status.ayrshare.com/incident/cmpe553ns006lp3mlycherga0 https://status.ayrshare.com/incident/cmpe553ns006lp3mlycherga0 Bluesky Users are Reporting A Global Outage Type: Incident Duration: 35 minutes Affected Components: Bluesky Apr 16, 10:00:21 GMT+0 - Monitoring - There are widespread reports of a Bluesky outage. We'll monitor and update you here. This is not related to Ayrshare's code. Apr 16, 10:35:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 35 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>10:00:21</var> GMT+0</small><br><strong>Monitoring</strong> - There are widespread reports of a Bluesky outage. We'll monitor and update you here. This is not related to Ayrshare's code. .</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>10:35:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 16 Apr 2026 10:00:21 +0000 https://status.ayrshare.com/incident/cmo1b6asm00x1vb3bk2a0cccw https://status.ayrshare.com/incident/cmo1b6asm00x1vb3bk2a0cccw Intermittent Instagram Publishing Errors Type: Incident Duration: 15 hours and 48 minutes Affected Components: Instagram Mar 31, 18:17:50 GMT+0 - Monitoring - In the last 24 hours, we’ve seen 846 Instagram posting errors across 340 unique UIDs, and \~6,000+ successful posts from \~2,962 unique UIDs. The failure rate of \~12% is elevated above the normal \~3-5% baseline. (Usually from problematic media files, duplicate posts, etc. ) The dominant cause is Meta-side transient errors (errCode 2, "An unexpected error has occurred") — 245 events (29%). This is a Meta infrastructure issue, not an Ayrshare code bug. The error spiked dramatically on March 30 at 20:00-22:00 UTC (347 errors in 3 hours), subsided overnight, and shows a secondary elevation on March 31 starting around 12:00 UTC. We also saw multiple issues with a smaller number of users that had expired Oauth tokens. That issue was identified and announced on March 30th 2026-03-30 and is fully resolved — zero error 190 "Invalid OAuth access token" events remain. Details are available on <https://status.ayrshare.com/> The key issue on our end is that error 138 continues to mask multiple distinct underlying causes, making it difficult for customers to self-diagnose. We’re working on two fixes: 1. Reworking the Meta error codes to make them easier for you to understand 2. Improved automatic unlinking of the expired Oauth tokens. We’re sorry for ambiguity for you and your users. Our team is working on these fixes right now. Unfortunately, transient issues like this happen with Meta periodically and they rarely update their status page. We’ll be delivering clearer messaging in the future to ensure that you can help debug your customers. Apr 1, 10:06:18 GMT+0 - Resolved - Starting March 30, Instagram media processing requests were failing at high-traffic times. We saw a significant spike in errors between 20:00–22:00 UTC (3pm–5pm ET) on March 30, with 347 errors in just 3 hours. Errors were concentrated at the top of each hour (:00–:05 UTC), when scheduled posts from many accounts hit Instagram simultaneously — 59% of all failures occurred in those first 5 minutes. The peak was at 02:00 UTC (9pm ET), accounting for 45% of hourly errors. Overall, the Instagram failure rate rose from our normal 3-5% baseline to approximately 12% during this period. What we've done: We've extended the wait times for Instagram media processing and retries. Instagram Reels and video content require server-side processing before they can be published, and during high-traffic periods, this processing was taking longer than our previous timeout windows allowed. By extending these wait times, posts that previously would have timed out and failed are now completing successfully. What's coming next: We will be extending these timeouts even further to handle more of these processing delays automatically, without requiring you to retry on your end. Our goal is to absorb Instagram's variable processing times so that high-traffic periods don't result in failed posts for you. We appreciate your patience and apologize for the disruption. If you're still seeing failures, please let us know with specific RefIDs and we'll investigate immediately. Type: Incident

Duration: 15 hours and 48 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>18:17:50</var> GMT+0</small><br><strong>Monitoring</strong> - In the last 24 hours, we’ve seen 846 Instagram posting errors across 340 unique UIDs, and \~6,000+ successful posts from \~2,962 unique UIDs. The failure rate of \~12% is elevated above the normal \~3-5% baseline. (Usually from problematic media files, duplicate posts, etc. ) The dominant cause is Meta-side transient errors (errCode 2, "An unexpected error has occurred") — 245 events (29%). This is a Meta infrastructure issue, not an Ayrshare code bug. The error spiked dramatically on March 30 at 20:00-22:00 UTC (347 errors in 3 hours), subsided overnight, and shows a secondary elevation on March 31 starting around 12:00 UTC. We also saw multiple issues with a smaller number of users that had expired Oauth tokens. That issue was identified and announced on March 30th 2026-03-30 and is fully resolved — zero error 190 "Invalid OAuth access token" events remain. Details are available on <https://status.ayrshare.com/> The key issue on our end is that error 138 continues to mask multiple distinct underlying causes, making it difficult for customers to self-diagnose. We’re working on two fixes: 1. Reworking the Meta error codes to make them easier for you to understand 2. Improved automatic unlinking of the expired Oauth tokens. We’re sorry for ambiguity for you and your users. Our team is working on these fixes right now. Unfortunately, transient issues like this happen with Meta periodically and they rarely update their status page. We’ll be delivering clearer messaging in the future to ensure that you can help debug your customers..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>10:06:18</var> GMT+0</small><br><strong>Resolved</strong> - Starting March 30, Instagram media processing requests were failing at high-traffic times. We saw a significant spike in errors between 20:00–22:00 UTC (3pm–5pm ET) on March 30, with 347 errors in just 3 hours. Errors were concentrated at the top of each hour (:00–:05 UTC), when scheduled posts from many accounts hit Instagram simultaneously — 59% of all failures occurred in those first 5 minutes. The peak was at 02:00 UTC (9pm ET), accounting for 45% of hourly errors. Overall, the Instagram failure rate rose from our normal 3-5% baseline to approximately 12% during this period. What we've done: We've extended the wait times for Instagram media processing and retries. Instagram Reels and video content require server-side processing before they can be published, and during high-traffic periods, this processing was taking longer than our previous timeout windows allowed. By extending these wait times, posts that previously would have timed out and failed are now completing successfully. What's coming next: We will be extending these timeouts even further to handle more of these processing delays automatically, without requiring you to retry on your end. Our goal is to absorb Instagram's variable processing times so that high-traffic periods don't result in failed posts for you. We appreciate your patience and apologize for the disruption. If you're still seeing failures, please let us know with specific RefIDs and we'll investigate immediately..</p> ]]> Tue, 31 Mar 2026 18:17:50 +0000 https://status.ayrshare.com/incident/cmnexwfot00yy12o74bn5xxpy https://status.ayrshare.com/incident/cmnexwfot00yy12o74bn5xxpy Intermittent Instagram Publishing Issues Type: Incident Duration: 6 days, 20 hours and 34 minutes Affected Components: Instagram Mar 30, 20:46:08 GMT+0 - Investigating - We've seen a number of customers experiencing intermittent errors from the Meta API for instagram posting. We're investigating now and will update here. Mar 30, 21:58:46 GMT+0 - Investigating - We're still seeing many successful instagram posts as well as frequent error responses from the Meta API. If you are retrying posts, it might be helpful to have a longer wait between retries. We're investigating the logs to analyze the flakiness. Mar 30, 23:30:42 GMT+0 - Resolved - While over 95% of instagram posts were publishing successfully, a small number of users were making a large number of retries with expired Oauth tokens. We're going to work on a solution to improve the code and error messaging related to this issue. Type: Incident

Duration: 6 days, 20 hours and 34 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>20:46:08</var> GMT+0</small><br><strong>Investigating</strong> - We've seen a number of customers experiencing intermittent errors from the Meta API for instagram posting. We're investigating now and will update here. .</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>21:58:46</var> GMT+0</small><br><strong>Investigating</strong> - We're still seeing many successful instagram posts as well as frequent error responses from the Meta API. If you are retrying posts, it might be helpful to have a longer wait between retries. We're investigating the logs to analyze the flakiness. .</p> <p><small>Mar <var data-var='date'> 30</var>, <var data-var='time'>23:30:42</var> GMT+0</small><br><strong>Resolved</strong> - While over 95% of instagram posts were publishing successfully, a small number of users were making a large number of retries with expired Oauth tokens. We're going to work on a solution to improve the code and error messaging related to this issue. .</p> ]]> Mon, 30 Mar 2026 20:46:08 +0000 https://status.ayrshare.com/incident/cmndnralx08o0zmjx66kr5ep9 https://status.ayrshare.com/incident/cmndnralx08o0zmjx66kr5ep9 TikTok Video Publishing Type: Incident Duration: 19 hours and 59 minutes Affected Components: TikTok Mar 27, 16:42:45 GMT+0 - Resolved - We've upgraded our backend to handle slow responses from the TikTok API. This was causing some users to have video posts stuck in a pending state, that problem should be solved now. Please reach out to [support@ayrshare.com](mailto:support@ayrshare.com) if you see any TikTok issues. Mar 26, 20:43:36 GMT+0 - Investigating - We have some users experiencing issues with TikTok posts getting stuck in pending state and not completing. We're investigating now. Mar 26, 21:19:30 GMT+0 - Identified - It appears that the issue where video uploads are stuck in pending state are only affecting US TikTok users. Type: Incident

Duration: 19 hours and 59 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>16:42:45</var> GMT+0</small><br><strong>Resolved</strong> - We've upgraded our backend to handle slow responses from the TikTok API. This was causing some users to have video posts stuck in a pending state, that problem should be solved now. Please reach out to [support@ayrshare.com](mailto:support@ayrshare.com) if you see any TikTok issues..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>20:43:36</var> GMT+0</small><br><strong>Investigating</strong> - We have some users experiencing issues with TikTok posts getting stuck in pending state and not completing. We're investigating now..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>21:19:30</var> GMT+0</small><br><strong>Identified</strong> - It appears that the issue where video uploads are stuck in pending state are only affecting US TikTok users. .</p> ]]> Thu, 26 Mar 2026 20:43:36 +0000 https://status.ayrshare.com/incident/cmn7xwmxk040el3jkrydnhsee https://status.ayrshare.com/incident/cmn7xwmxk040el3jkrydnhsee TikTok Video Publishing Issues Type: Incident Duration: 5 hours and 3 minutes Affected Components: TikTok Mar 26, 15:23:29 GMT+0 - Resolved - This incident has been resolved. Mar 26, 10:20:07 GMT+0 - Identified - We're getting reports on TikTok video posting failing for some users. We are receiving success responses form TikTok when we send posts to their API, but webhooks are stuck in pending and posts aren't completing. The Ayrshare TikTok API is working, but we're looking into any possible amelioration for this issue. Mar 26, 11:05:42 GMT+0 - Monitoring - We're seeing posts succeeding now on production, we'll continue to mintor. Type: Incident

Duration: 5 hours and 3 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>15:23:29</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>10:20:07</var> GMT+0</small><br><strong>Identified</strong> - We're getting reports on TikTok video posting failing for some users. We are receiving success responses form TikTok when we send posts to their API, but webhooks are stuck in pending and posts aren't completing. The Ayrshare TikTok API is working, but we're looking into any possible amelioration for this issue..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>11:05:42</var> GMT+0</small><br><strong>Monitoring</strong> - We're seeing posts succeeding now on production, we'll continue to mintor..</p> ]]> Thu, 26 Mar 2026 10:20:07 +0000 https://status.ayrshare.com/incident/cmn7bmtk601ma99y9iedlnuj0 https://status.ayrshare.com/incident/cmn7bmtk601ma99y9iedlnuj0 Meta API is having issues with some Facebook video uploads Type: Incident Duration: 14 hours and 46 minutes Affected Components: Facebook Mar 13, 10:02:32 GMT+0 - Resolved - This incident has been resolved. Mar 12, 19:16:11 GMT+0 - Monitoring - This is intermittent, only affecting some posts. The issue is happening on Meta's side - here's a thread we're following for more details: <https://developers.facebook.com/community/threads/1249634937370976/> Type: Incident

Duration: 14 hours and 46 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 13</var>, <var data-var='time'>10:02:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>19:16:11</var> GMT+0</small><br><strong>Monitoring</strong> - This is intermittent, only affecting some posts. The issue is happening on Meta's side - here's a thread we're following for more details: <https://developers.facebook.com/community/threads/1249634937370976/>.</p> ]]> Thu, 12 Mar 2026 19:16:11 +0000 https://status.ayrshare.com/incident/cmmnumaac0a0c5dpm8cw7gagv https://status.ayrshare.com/incident/cmmnumaac0a0c5dpm8cw7gagv TikTok API is having intermittent issues Type: Incident Duration: 14 hours and 41 minutes Affected Components: TikTok Mar 3, 18:51:23 GMT+0 - Monitoring - The TikTok API is having some intermittent post issues. This happened previously with the new US ownership, and we expect this is a similar issue. We're continuing to monitor the situation. Mar 4, 09:32:39 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 14 hours and 41 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>18:51:23</var> GMT+0</small><br><strong>Monitoring</strong> - The TikTok API is having some intermittent post issues. This happened previously with the new US ownership, and we expect this is a similar issue. We're continuing to monitor the situation. .</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>09:32:39</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 3 Mar 2026 18:51:23 +0000 https://status.ayrshare.com/incident/cmmayrq930fgaw0jvj5h17yyg https://status.ayrshare.com/incident/cmmayrq930fgaw0jvj5h17yyg Instagram Video & Reel Posts — Temporary Failures Due to Meta API Issue Type: Incident Affected Components: Instagram, Facebook Feb 26, 04:30:00 GMT+0 - Resolved - On February 26 at approximately 4:30 AM GMT, Instagram video posts and Reels began failing due to a regression in Meta's Instagram Graph API. Meta's system was incorrectly classifying video uploads during processing, causing them to be rejected. Image posts were not affected. This was an industry-wide issue confirmed across multiple platforms that integrate with Instagram's API. Meta resolved the issue on their end on February 27 at approximately 12:30 AM GMT (\~20 hours). No Ayrshare code changes were required. Affected customers should retry any failed Instagram video or Reel posts from this window. If you continue to experience issues, please contact support. Feb 27, 00:30:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components: ,

<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>04:30:00</var> GMT+0</small><br><strong>Resolved</strong> - On February 26 at approximately 4:30 AM GMT, Instagram video posts and Reels began failing due to a regression in Meta's Instagram Graph API. Meta's system was incorrectly classifying video uploads during processing, causing them to be rejected. Image posts were not affected. This was an industry-wide issue confirmed across multiple platforms that integrate with Instagram's API. Meta resolved the issue on their end on February 27 at approximately 12:30 AM GMT (\~20 hours). No Ayrshare code changes were required. Affected customers should retry any failed Instagram video or Reel posts from this window. If you continue to experience issues, please contact support..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 26 Feb 2026 04:30:00 +0000 https://status.ayrshare.com/incident/cmmaqms4q000ybrz6dbtborav https://status.ayrshare.com/incident/cmmaqms4q000ybrz6dbtborav TikTok API for US users Type: Incident Duration: 4 days Affected Components: TikTok Jan 29, 18:04:59 GMT+0 - Monitoring - We're still seeing occasional reports of issues from US Tiktok users and there's no official announcement from TikTok since this: "We've made significant progress in recovering our U.S. infrastructure with our U.S. data center partner. However, the U.S. user experience may still have some technical issues, including when posting new content. We're committed to bringing TikTok back to its full capacity as soon as possible. We'll continue to provide updates. Thanks for your patience." Feb 2, 18:05:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 days

Affected Components:

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>18:04:59</var> GMT+0</small><br><strong>Monitoring</strong> - We're still seeing occasional reports of issues from US Tiktok users and there's no official announcement from TikTok since this: "We've made significant progress in recovering our U.S. infrastructure with our U.S. data center partner. However, the U.S. user experience may still have some technical issues, including when posting new content. We're committed to bringing TikTok back to its full capacity as soon as possible. We'll continue to provide updates. Thanks for your patience.".</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>18:05:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 29 Jan 2026 18:04:59 +0000 https://status.ayrshare.com/incident/cmkzrky2u0lsqvqphds9w34w9 https://status.ayrshare.com/incident/cmkzrky2u0lsqvqphds9w34w9 TikTok US Infrastructure Problems Type: Incident Duration: 1 day, 5 hours and 13 minutes Affected Components: TikTok Jan 29, 11:12:53 GMT+0 - Resolved - TikTok hasn't made any public announcement, but the API appears to be working for US users. We'll continue to monitor it. Jan 28, 06:00:00 GMT+0 - Monitoring - The new owners of TikTok in the US have acknowledged this issue and they're working on a solution: <https://x.com/tiktokusdsjv/status/2016174448722817146?s=20> Type: Incident

Duration: 1 day, 5 hours and 13 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>11:12:53</var> GMT+0</small><br><strong>Resolved</strong> - TikTok hasn't made any public announcement, but the API appears to be working for US users. We'll continue to monitor it..</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - The new owners of TikTok in the US have acknowledged this issue and they're working on a solution: <https://x.com/tiktokusdsjv/status/2016174448722817146?s=20>.</p> ]]> Wed, 28 Jan 2026 06:00:00 +0000 https://status.ayrshare.com/incident/cmkxtbjq300m0141p34lx5t9j https://status.ayrshare.com/incident/cmkxtbjq300m0141p34lx5t9j The Tiktok API is having intermittent outages Type: Incident Duration: 1 day, 18 hours and 41 minutes Affected Components: TikTok Jan 25, 16:30:00 GMT+0 - Monitoring - We're monitoring the issues with TikTok, this is a general outage and not specific to Ayrshare. Jan 27, 11:11:29 GMT+0 - Resolved - It appears that TikTok has resolved this issue. Type: Incident

Duration: 1 day, 18 hours and 41 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 25</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Monitoring</strong> - We're monitoring the issues with TikTok, this is a general outage and not specific to Ayrshare..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>11:11:29</var> GMT+0</small><br><strong>Resolved</strong> - It appears that TikTok has resolved this issue..</p> ]]> Sun, 25 Jan 2026 16:30:00 +0000 https://status.ayrshare.com/incident/cmkwelc1t0g0vk44o6sa8y6q8 https://status.ayrshare.com/incident/cmkwelc1t0g0vk44o6sa8y6q8 Cloudflare Outage Type: Incident Affected Components: X/Twitter, Ayrshare Dashboard Nov 18, 12:00:00 GMT+0 - Resolved - There is currently a global Cloudflare outage affecting access to Ayrshare's dashboard and endpoints that involve the X/Twitter API. Endpoints not involving X/Twitter are functioning. Nov 18, 14:30:00 GMT+0 - Resolved - This global Cloudflare issue has since been resolved. Cloudflare stated that the problem was caused by a configuration file and that there is no evidence this was caused by cyberattack. Type: Incident

Affected Components: ,

<p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Resolved</strong> - There is currently a global Cloudflare outage affecting access to Ayrshare's dashboard and endpoints that involve the X/Twitter API. Endpoints not involving X/Twitter are functioning. .</p> <p><small>Nov <var data-var='date'> 18</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Resolved</strong> - This global Cloudflare issue has since been resolved. Cloudflare stated that the problem was caused by a configuration file and that there is no evidence this was caused by cyberattack. .</p> ]]> Tue, 18 Nov 2025 12:00:00 +0000 https://status.ayrshare.com/incident/cmi4u8api002qjedih3beo2rv https://status.ayrshare.com/incident/cmi4u8api002qjedih3beo2rv Issue Publishing Facebook Videos & Reels Type: Incident Affected Components: Facebook Nov 15, 09:40:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>09:40:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sat, 15 Nov 2025 09:40:36 +0000 https://status.ayrshare.com/incident/cmi04n7c4019h4hiqgfvfs3nm https://status.ayrshare.com/incident/cmi04n7c4019h4hiqgfvfs3nm Facebook having issues with Reels and Video Publishing Type: Incident Duration: 1 day, 6 hours and 47 minutes Affected Components: Facebook Nov 14, 03:00:00 GMT+0 - Monitoring - We're monitoring an issue with the Meta API regarding video publishing. Nov 15, 09:46:57 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 6 hours and 47 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - We're monitoring an issue with the Meta API regarding video publishing. .</p> <p><small>Nov <var data-var='date'> 15</var>, <var data-var='time'>09:46:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 14 Nov 2025 03:00:00 +0000 https://status.ayrshare.com/incident/cmi04upg10hv6vuvu0yyfbhsi https://status.ayrshare.com/incident/cmi04upg10hv6vuvu0yyfbhsi Issue Unlinking YouTube Accounts Type: Incident Duration: 1 hour and 23 minutes Affected Components: YouTube Nov 13, 23:13:56 GMT+0 - Identified - We are investigating this issue now. Nov 14, 00:37:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 23 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>23:13:56</var> GMT+0</small><br><strong>Identified</strong> - We are investigating this issue now. .</p> <p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>00:37:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 13 Nov 2025 23:13:56 +0000 https://status.ayrshare.com/incident/cmhy1po6u08snsimld19z20c4 https://status.ayrshare.com/incident/cmhy1po6u08snsimld19z20c4 Account unlinking issues Type: Incident Duration: 9 hours and 37 minutes Affected Components: Ayrshare Dashboard Nov 14, 00:37:00 GMT+0 - Resolved - This incident has been resolved. Nov 13, 23:00:00 GMT+0 - Investigating - We had a temporary issue where accounts could not be unlinked or deleted. That issue was quickly resolved and the dashboard is working as usual. Thank you to the users who reported the issue in such a timely manner! Type: Incident

Duration: 9 hours and 37 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 14</var>, <var data-var='time'>00:37:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We had a temporary issue where accounts could not be unlinked or deleted. That issue was quickly resolved and the dashboard is working as usual. Thank you to the users who reported the issue in such a timely manner!.</p> ]]> Thu, 13 Nov 2025 23:00:00 +0000 https://status.ayrshare.com/incident/cmhymylv80163xndokv4gjf69 https://status.ayrshare.com/incident/cmhymylv80163xndokv4gjf69 Limits on Facebook history API Type: Incident Duration: 1 day, 10 hours and 43 minutes Affected Components: Facebook Oct 28, 08:52:50 GMT+0 - Investigating - We've seen multiple customers who are not able to receive full History API results from Facebook when pulling a large number of posts. The History API is correctly returning results for smaller data pulls. We're investigating and we will update with more information soon. Oct 29, 19:35:55 GMT+0 - Resolved - We've isolated the problem and are deploying a fix. Type: Incident

Duration: 1 day, 10 hours and 43 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>08:52:50</var> GMT+0</small><br><strong>Investigating</strong> - We've seen multiple customers who are not able to receive full History API results from Facebook when pulling a large number of posts. The History API is correctly returning results for smaller data pulls. We're investigating and we will update with more information soon. .</p> <p><small>Oct <var data-var='date'> 29</var>, <var data-var='time'>19:35:55</var> GMT+0</small><br><strong>Resolved</strong> - We've isolated the problem and are deploying a fix. .</p> ]]> Tue, 28 Oct 2025 08:52:50 +0000 https://status.ayrshare.com/incident/cmhabwnll01nqsf92wnmyb8sz https://status.ayrshare.com/incident/cmhabwnll01nqsf92wnmyb8sz Investigating an issue with the Link Shortener Type: Incident Duration: 13 hours and 15 minutes Affected Components: Ayrshare Link Shortener Oct 24, 14:15:36 GMT+0 - Resolved - This incident has been resolved - all past links should be working now, Oct 24, 01:00:11 GMT+0 - Identified - We are currently investigating this incident. Shortened links ([https://ayrs.io/xxxx)](https://ayrs.io/%5FJPL-v) may not be resolving for all users. Type: Incident

Duration: 13 hours and 15 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>14:15:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved - all past links should be working now, .</p> <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>01:00:11</var> GMT+0</small><br><strong>Identified</strong> - We are currently investigating this incident. Shortened links ([https://ayrs.io/xxxx)](https://ayrs.io/%5FJPL-v) may not be resolving for all users. .</p> ]]> Fri, 24 Oct 2025 01:00:11 +0000 https://status.ayrshare.com/incident/cmh459f3o000d12rhsbxzx8a0 https://status.ayrshare.com/incident/cmh459f3o000d12rhsbxzx8a0 Threads Connection Issue Type: Incident Duration: 2 days, 1 hour and 43 minutes Affected Components: Threads Aug 22, 14:48:34 GMT+0 - Investigating - Meta Threads currently has an issue linking Threads accounts with Ayrshare. This is a system wide issue at Meta. Current connections do not have issues posting, getting analytics, etc. Aug 24, 16:31:38 GMT+0 - Resolved - Update: The Threads authorization bug has been resolved by Meta. Users can now successfully authenticate their Threads accounts. Type: Incident

Duration: 2 days, 1 hour and 43 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>14:48:34</var> GMT+0</small><br><strong>Investigating</strong> - Meta Threads currently has an issue linking Threads accounts with Ayrshare. This is a system wide issue at Meta. Current connections do not have issues posting, getting analytics, etc..</p> <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>16:31:38</var> GMT+0</small><br><strong>Resolved</strong> - Update: The Threads authorization bug has been resolved by Meta. Users can now successfully authenticate their Threads accounts..</p> ]]> Fri, 22 Aug 2025 14:48:34 +0000 https://status.ayrshare.com/incident/cmemy42200001nrbmqrrx9p8n https://status.ayrshare.com/incident/cmemy42200001nrbmqrrx9p8n Facebook or Instagram with a Facebook Page Account Verification Required Type: Incident Aug 14, 14:13:08 GMT+0 - Resolved - This incident has been resolved. Aug 14, 13:30:08 GMT+0 - Resolved - You may receive a message indicating that your user needs to log in to [Facebook.com](http://Facebook.com) to verify the account for both Facebook and Instagram (with a connect Facebook Page and not Instagram Login) connections. Meta conducted an unannounced verification campaign earlier today that affected some accounts. If you encounter this message, please follow these steps: **1\. Log in to** [**Facebook.com**](http://Facebook.com) Visit [facebook.com](http://facebook.com) and log into your account. You may see a Facebook Advanced Protection verification check that simply requires clicking a button, or you may not see any additional prompts at all. **2\. Retry your API calls** After logging in, attempt your Facebook and Instagram API calls again. The API calls should now work successfully. **3\. If issues persist** If you're still experiencing problems, try unlinking and relinking your Facebook and Instagram accounts on the Ayrshare social accounts linking page, then attempt your API calls once more. Please don't hesitate to reach out if you have any questions or need further assistance. Type: Incident

<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>14:13:08</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>13:30:08</var> GMT+0</small><br><strong>Resolved</strong> - You may receive a message indicating that your user needs to log in to [Facebook.com](http://Facebook.com) to verify the account for both Facebook and Instagram (with a connect Facebook Page and not Instagram Login) connections. Meta conducted an unannounced verification campaign earlier today that affected some accounts. If you encounter this message, please follow these steps: **1\. Log in to** [**Facebook.com**](http://Facebook.com) Visit [facebook.com](http://facebook.com) and log into your account. You may see a Facebook Advanced Protection verification check that simply requires clicking a button, or you may not see any additional prompts at all. **2\. Retry your API calls** After logging in, attempt your Facebook and Instagram API calls again. The API calls should now work successfully. **3\. If issues persist** If you're still experiencing problems, try unlinking and relinking your Facebook and Instagram accounts on the Ayrshare social accounts linking page, then attempt your API calls once more. Please don't hesitate to reach out if you have any questions or need further assistance..</p> ]]> Thu, 14 Aug 2025 13:30:08 +0000 https://status.ayrshare.com/incident/cmebilrs9002j6dqi8lisqs60 https://status.ayrshare.com/incident/cmebilrs9002j6dqi8lisqs60 Developer Dashboard Google Login Type: Incident Duration: 4 hours and 40 minutes Affected Components: Ayrshare Dashboard Jul 18, 15:31:54 GMT+0 - Identified - Google is currently experiencing a global outage with their Google Authentication, so you may be unable to login to the Ayrshare Developer Dashboard using Google Auth. We are monitoring the situation for a Google fix. Jul 18, 20:12:23 GMT+0 - Resolved - This incident has been resolved by Google. You should no longer have issue using Google Auth to login to the Ayrshare Developer Dashboard. Type: Incident

Duration: 4 hours and 40 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>15:31:54</var> GMT+0</small><br><strong>Identified</strong> - Google is currently experiencing a global outage with their Google Authentication, so you may be unable to login to the Ayrshare Developer Dashboard using Google Auth. We are monitoring the situation for a Google fix..</p> <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>20:12:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved by Google. You should no longer have issue using Google Auth to login to the Ayrshare Developer Dashboard..</p> ]]> Fri, 18 Jul 2025 15:31:54 +0000 https://status.ayrshare.com/incident/cmd8z8z0r003owuocf6uu6bph https://status.ayrshare.com/incident/cmd8z8z0r003owuocf6uu6bph Google Global Outage Type: Incident Duration: 7 hours and 44 minutes Affected Components: Google Business Profile, YouTube, Ayrshare Dashboard Jun 12, 18:40:51 GMT+0 - Investigating - Google is currently experiencing a global outage that is affecting our Developer Dashboard access, YouTube, and other system. We will keep you informed on Google resolving the issue. Jun 13, 02:24:46 GMT+0 - Resolved - Google has resolved their outage and all system have returned to normal. Please let us know if you have any questions. Type: Incident

Duration: 7 hours and 44 minutes

Affected Components: , ,

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:40:51</var> GMT+0</small><br><strong>Investigating</strong> - Google is currently experiencing a global outage that is affecting our Developer Dashboard access, YouTube, and other system. We will keep you informed on Google resolving the issue..</p> <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>02:24:46</var> GMT+0</small><br><strong>Resolved</strong> - Google has resolved their outage and all system have returned to normal. Please let us know if you have any questions..</p> ]]> Thu, 12 Jun 2025 18:40:51 +0000 https://status.ayrshare.com/incident/cmbtq5atg0028abtgnraug1fj https://status.ayrshare.com/incident/cmbtq5atg0028abtgnraug1fj X Video Posting Type: Incident Duration: 49 minutes Affected Components: X/Twitter Jun 3, 13:34:28 GMT+0 - Investigating - We are currently investigating a issue with posting videos to X. When posting a video to X you may receive an error. Jun 3, 14:23:20 GMT+0 - Resolved - This X video incident has been resolved. X made an undocumented API change that we've now compensated for, and you should have no further issues posting X videos. Type: Incident

Duration: 49 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>13:34:28</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating a issue with posting videos to X. When posting a video to X you may receive an error..</p> <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>14:23:20</var> GMT+0</small><br><strong>Resolved</strong> - This X video incident has been resolved. X made an undocumented API change that we've now compensated for, and you should have no further issues posting X videos..</p> ]]> Tue, 3 Jun 2025 13:34:28 +0000 https://status.ayrshare.com/incident/cmbgk8m8o000b5qaxbatgyhkm https://status.ayrshare.com/incident/cmbgk8m8o000b5qaxbatgyhkm X Account Linking Type: Incident Duration: 2 days, 13 hours and 15 minutes Affected Components: X/Twitter May 23, 00:31:38 GMT+0 - Identified - We're currently experiencing an outage with the X API that is preventing account linking functionality. The X API team is actively working to resolve this issue. Posting continues to function, but we are seeing some issues with retrieving post analytics. May 24, 14:38:38 GMT+0 - Identified - The issue with the X API is due to a fire in one of their data centers. The X engineering team is continuing to work on restoring linking X accounts. May 25, 13:46:43 GMT+0 - Resolved - X has resolved the issues and you may now link your X with Ayrshare and get analytics. If you have any issues, please let us know. Type: Incident

Duration: 2 days, 13 hours and 15 minutes

Affected Components:

<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>00:31:38</var> GMT+0</small><br><strong>Identified</strong> - We're currently experiencing an outage with the X API that is preventing account linking functionality. The X API team is actively working to resolve this issue. Posting continues to function, but we are seeing some issues with retrieving post analytics..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>14:38:38</var> GMT+0</small><br><strong>Identified</strong> - The issue with the X API is due to a fire in one of their data centers. The X engineering team is continuing to work on restoring linking X accounts..</p> <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>13:46:43</var> GMT+0</small><br><strong>Resolved</strong> - X has resolved the issues and you may now link your X with Ayrshare and get analytics. If you have any issues, please let us know..</p> ]]> Fri, 23 May 2025 00:31:38 +0000 https://status.ayrshare.com/incident/cmb02fift006uhurp68dwgo87 https://status.ayrshare.com/incident/cmb02fift006uhurp68dwgo87