Is Ayrshare down?

Type: Incident Duration: 46 minutes Affected Components: Pinterest Aug 14, 15:15:27 GMT+0 Resolved - Pinterest publishing has returned to normal success rates. Posts that failed during this incident were not published — please resend any affected posts. The root cause was an image-processing delay on Pinterest's side. No Ayrshare configuration or customer action was required to resolve it.. Aug 14, 14:29:08 GMT+0 Identified - Pinterest posts are failing at an elevated rate and returning error code 251 with the message "Sorry! Something went wrong on our end." This is an issue on Pinterest's side, not with your account, credentials, or images. Pinterest is timing out while fetching the image for new posts. Posts to all other social networks are unaffected. What you can do: retry the affected post after a few minutes. The same image usually publishes successfully on a later attempt. You can use the retry endpoint: <https://www.ayrshare.com/docs/apis/post/retry-post> Please avoid retrying the same post repeatedly in quick succession — immediate retries fail the same way, and rapid repeat attempts can be flagged by Pinterest. Waiting a few minutes between attempts is more effective..

Type: Incident Duration: 1 hour and 5 minutes Affected Components: Ayrshare API Aug 11, 17:05:00 GMT+0 Resolved - The issue has been resolved. After deeper investigation, we've determined that the customer visible impacts of this issue were minimal enough to update the impact report. We have increased our minimum set of always on hardware to protect against future issues. However the new V3 platform continues to operate with very low error rates during high load times of day.. Aug 11, 16:20:00 GMT+0 Identified - Despite the excellent performance so far of the new V3 backend, a small number of posts were encountered errors when our autoscaling wasn't keeping up with load today. We're very sorry for the inconvenience. The issue has been resolved and we've increased our minimum base of always on hardware to protect against future issues, and we're continuing to focus on stability as we fully release v3..