Ayrshare Status - Incident history https://status.ayrshare.com Ayrshare Thu, 18 Jun 2026 10:30:00 +0000 Instagram Post and Social Analytics Type: Incident Affected Components: Instagram Jun 18, 10:30:00 GMT+0 - Resolved - Facebook (Meta) has deprecated a set of Facebook Insights metrics across all versions of its Graph API, with the change taking effect on June 15, 2026\. As a result, some fields are currently missing from Facebook post and page analytics responses, including impression/reach metrics and 3-second video-view metrics. We have identified the cause and have deployed an update to our Facebook analytics requests. This update restores the fields Meta still supports (including reactions, video views, video view time, and media views) and adopts Meta's new replacement metrics (Total Unique Media Views). Some metrics have been permanently retired by Meta and are no longer available from their API: the unique-impression fields (unique impressions and their paid, organic, and fan breakdowns) and the unique 3-second video-view fields. Meta is replacing these with its new Media Views and Unique Views metrics. This is a platform-wide Meta change that affected endpoints that use Facebook's analytics API; it is not specific to Ayrshare. We have deployed an update for Facebook post and social analytics. Additional details: <https://www.ayrshare.com/docs/whatsnew/latest#june-2026> Type: Incident

Affected Components:

<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br><strong>Resolved</strong> - Facebook (Meta) has deprecated a set of Facebook Insights metrics across all versions of its Graph API, with the change taking effect on June 15, 2026\. As a result, some fields are currently missing from Facebook post and page analytics responses, including impression/reach metrics and 3-second video-view metrics. We have identified the cause and have deployed an update to our Facebook analytics requests. This update restores the fields Meta still supports (including reactions, video views, video view time, and media views) and adopts Meta's new replacement metrics (Total Unique Media Views). Some metrics have been permanently retired by Meta and are no longer available from their API: the unique-impression fields (unique impressions and their paid, organic, and fan breakdowns) and the unique 3-second video-view fields. Meta is replacing these with its new Media Views and Unique Views metrics. This is a platform-wide Meta change that affected endpoints that use Facebook's analytics API; it is not specific to Ayrshare. We have deployed an update for Facebook post and social analytics. Additional details: <https://www.ayrshare.com/docs/whatsnew/latest#june-2026>.</p> ]]> Thu, 18 Jun 2026 10:30:00 +0000 https://status.ayrshare.com/incident/cmqi4ik1e05no2jmu3imn26kk https://status.ayrshare.com/incident/cmqi4ik1e05no2jmu3imn26kk Meta Publishing Issues Type: Incident Duration: 6 hours and 58 minutes Affected Components: Facebook, Threads, Instagram Jun 12, 21:30:03 GMT+0 - Resolved - This incident has been resolved by Meta and the system is operating as normal. Jun 12, 14:31:42 GMT+0 - Investigating - We are currently investigating an issue with publishing on Meta platforms. This issue has been reported by multiple other social products in the market, so we believe it's on the Meta side. We'll investigate and update here. Jun 12, 14:37:21 GMT+0 - Identified - The media are reporting a global outage on Meta, include Facebook, Instagram and Messenger. We'll update this page as soon as they resolve the issue. Jun 12, 15:48:53 GMT+0 - Monitoring - Meta is starting to recover - we're seeing a roughly 50% success rate on posts right now. Type: Incident

Duration: 6 hours and 58 minutes

Affected Components: , ,

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>21:30:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved by Meta and the system is operating as normal..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>14:31:42</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue with publishing on Meta platforms. This issue has been reported by multiple other social products in the market, so we believe it's on the Meta side. We'll investigate and update here. .</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>14:37:21</var> GMT+0</small><br><strong>Identified</strong> - The media are reporting a global outage on Meta, include Facebook, Instagram and Messenger. We'll update this page as soon as they resolve the issue. .</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>15:48:53</var> GMT+0</small><br><strong>Monitoring</strong> - Meta is starting to recover - we're seeing a roughly 50% success rate on posts right now. .</p> ]]> Fri, 12 Jun 2026 14:31:42 +0000 https://status.ayrshare.com/incident/cmqb0ysz0099onu9zjqgab2o0 https://status.ayrshare.com/incident/cmqb0ysz0099onu9zjqgab2o0 Issue publishing for some Instagram users Type: Incident Duration: 10 days, 8 hours and 57 minutes Affected Components: Instagram May 26, 18:08:56 GMT+0 - Resolved - Our team has developed a workaround for this issue. We're able to bypass the problematic check media endpoint to allow Instagram publishing for affected users to succeed. However, posts using this workaround will not receive a post URL in the response. For now, you can still use the history API to "get post history for a platform" for the relevant post and receive the URL: <https://www.ayrshare.com/docs/apis/history/history-platform> Our team will work on a solution for the missing URLs and raise a bug report with Meta about the underlying issues. May 27, 13:31:04 GMT+0 - Resolved - Meta has now fixed the underlying issue and the URLs are being properly returned again. May 26, 14:00:00 GMT+0 - Identified - We're seeing a new issue from the Instagram API, where Meta is not returning a success response when we check status on media files via their API (as part of the publishing process). this is only affecting some users that use their Facebook account to control the related Instagram page. Our team is working on a workaround and we'll be deploying it soon. Type: Incident

Duration: 10 days, 8 hours and 57 minutes

Affected Components:

<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>18:08:56</var> GMT+0</small><br><strong>Resolved</strong> - Our team has developed a workaround for this issue. We're able to bypass the problematic check media endpoint to allow Instagram publishing for affected users to succeed. However, posts using this workaround will not receive a post URL in the response. For now, you can still use the history API to "get post history for a platform" for the relevant post and receive the URL: <https://www.ayrshare.com/docs/apis/history/history-platform> Our team will work on a solution for the missing URLs and raise a bug report with Meta about the underlying issues. .</p> <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>13:31:04</var> GMT+0</small><br><strong>Resolved</strong> - Meta has now fixed the underlying issue and the URLs are being properly returned again. .</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br><strong>Identified</strong> - We're seeing a new issue from the Instagram API, where Meta is not returning a success response when we check status on media files via their API (as part of the publishing process). this is only affecting some users that use their Facebook account to control the related Instagram page. Our team is working on a workaround and we'll be deploying it soon. .</p> ]]> Tue, 26 May 2026 14:00:00 +0000 https://status.ayrshare.com/incident/cmpmw5q0j0tk4p2mer86nvqws https://status.ayrshare.com/incident/cmpmw5q0j0tk4p2mer86nvqws Temporary Platform Outage - Now Fixed Type: Incident Duration: 1 day and 11 hours Affected Components: Ayrshare API May 25, 15:15:00 GMT+0 - Resolved - This incident has been resolved. May 25, 14:40:00 GMT+0 - Identified - As part of our missions to continuously improve the reliability of our product, the Ayrshare team has been working on a major platform upgrade with much more precise logging. This will be a huge step forward for the platform, but there was a misconfiguration in today's deployment which has now been fixed. We are deeply sorry for any inconvenience this caused. In addition to our automated testing for all code we write, we do full tests of the entire platform multiple times every day, however they take time to complete. In order to prevent future similar issues we're connecting the timing of the full regression testing to future production merges to prevent a possible recurrence of this issue. The improved logging is now live, and our team will continue our focus on improving the speed and reliability of the product for our customers. Type: Incident

Duration: 1 day and 11 hours

Affected Components:

<p><small>May <var data-var='date'> 25</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>14:40:00</var> GMT+0</small><br><strong>Identified</strong> - As part of our missions to continuously improve the reliability of our product, the Ayrshare team has been working on a major platform upgrade with much more precise logging. This will be a huge step forward for the platform, but there was a misconfiguration in today's deployment which has now been fixed. We are deeply sorry for any inconvenience this caused. In addition to our automated testing for all code we write, we do full tests of the entire platform multiple times every day, however they take time to complete. In order to prevent future similar issues we're connecting the timing of the full regression testing to future production merges to prevent a possible recurrence of this issue. The improved logging is now live, and our team will continue our focus on improving the speed and reliability of the product for our customers. .</p> ]]> Mon, 25 May 2026 14:40:00 +0000 https://status.ayrshare.com/incident/cmpletfej0srzqkp1l6hyw0vh https://status.ayrshare.com/incident/cmpletfej0srzqkp1l6hyw0vh Instagram Publishing - Intermittent success rate Type: Incident Duration: 2 days, 22 hours and 47 minutes Affected Components: Instagram May 23, 10:00:00 GMT+0 - Monitoring - Starting Saturday, May 23, 2026, with a notable spike on May 24, 2026 from 12:00pm – 12:05pm UTC, posts published to Instagram have encountered a degraded success rate, and we're continuing to see intermittent publishing issues. Our investigation indicates this is caused by a degradation in Meta's Instagram Graph API, specifically during the media publishing process. Ayrshare's systems are operating normally — posts are being submitted successfully, but Meta's API is returning errors when processing them. Other networks (Facebook, Threads, LinkedIn, etc.) are not affected. We recommend not retrying failed posts at this time, as the issue is on Meta's side and repeated attempts are unlikely to succeed until Meta resolves the degradation. Ayrshare is actively monitoring the situation and will share updates as the status changes. We apologize for the inconvenience. May 26, 08:46:37 GMT+0 - Resolved - The Instagram publishing issue first observed on Saturday, May 23, 2026 has been resolved. Meta has addressed the degradation in the Instagram Graph API, and publishing success rates have returned to normal. Thank you for your patience while Meta worked through the issue, and we apologize for any inconvenience this caused to your publishing workflows. As always, we’ll continue monitoring closely and will communicate promptly if any related issues arise. Type: Incident

Duration: 2 days, 22 hours and 47 minutes

Affected Components:

<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Monitoring</strong> - Starting Saturday, May 23, 2026, with a notable spike on May 24, 2026 from 12:00pm – 12:05pm UTC, posts published to Instagram have encountered a degraded success rate, and we're continuing to see intermittent publishing issues. Our investigation indicates this is caused by a degradation in Meta's Instagram Graph API, specifically during the media publishing process. Ayrshare's systems are operating normally — posts are being submitted successfully, but Meta's API is returning errors when processing them. Other networks (Facebook, Threads, LinkedIn, etc.) are not affected. We recommend not retrying failed posts at this time, as the issue is on Meta's side and repeated attempts are unlikely to succeed until Meta resolves the degradation. Ayrshare is actively monitoring the situation and will share updates as the status changes. We apologize for the inconvenience..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>08:46:37</var> GMT+0</small><br><strong>Resolved</strong> - The Instagram publishing issue first observed on Saturday, May 23, 2026 has been resolved. Meta has addressed the degradation in the Instagram Graph API, and publishing success rates have returned to normal. Thank you for your patience while Meta worked through the issue, and we apologize for any inconvenience this caused to your publishing workflows. As always, we’ll continue monitoring closely and will communicate promptly if any related issues arise..</p> ]]> Sat, 23 May 2026 10:00:00 +0000 https://status.ayrshare.com/incident/cmpl4rl2k0cjfp2ml9ws8lu6z https://status.ayrshare.com/incident/cmpl4rl2k0cjfp2ml9ws8lu6z 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