Ayrshare Dashboard - Operational
Ayrshare Dashboard
Ayrshare API - Operational
Ayrshare API
Bluesky - Operational
Bluesky
Facebook - Operational
Google Business Profile - Operational
Google Business Profile
Instagram - Operational
LinkedIn - Operational
Pinterest - Operational
Reddit - Operational
Snapchat - Operational
Snapchat
Telegram - Operational
Telegram
Threads - Operational
Threads
TikTok - Operational
TikTok
YouTube - Operational
YouTube
X/Twitter - Operational
X/Twitter
Ayrshare Link Shortener - Operational
Notice history
May 2026
- UpdateUTCUpdateUTC
Meta has now fixed the underlying issue and the URLs are being properly returned again.
- ResolvedUTCResolvedUTC
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. - IdentifiedUTCIdentifiedUTC
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.
Mar 2026
- ResolvedUTCResolvedUTC
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. - MonitoringUTCMonitoringUTC
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:
Reworking the Meta error codes to make them easier for you to understand
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.
- ResolvedUTCResolvedUTC
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 [email protected] if you see any TikTok issues.
- IdentifiedUTCIdentifiedUTC
It appears that the issue where video uploads are stuck in pending state are only affecting US TikTok users.
- InvestigatingUTCInvestigatingUTC
We have some users experiencing issues with TikTok posts getting stuck in pending state and not completing. We're investigating now.
- ResolvedUTCResolvedUTCThis incident has been resolved.
- MonitoringUTCMonitoringUTC
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/