Is Agorapulse Down Right Now? Check if there is a current outage ongoing.

We're currently seeing issues with publishing and inbox replies for Google My Business and YouTube. This is due to widespread outages affecting Google and other major online services. We're monitoring the situation closely.

We are currently investigating the issue.

This issue has been resolved, thank you for your patience.

Our technical team has identified the issue with the X API. We're working on a fix to resolve the errors affecting direct message replies.

We are currently investigating the issue.

We are currently investigating the issue.

The fix to prevent post failures on our end due to Twitter/X system issues is working as expected.

Twitter/X has acknowledged issues with their API (see: https://docs.x.com/status#). We've implemented a workaround to help prevent post failures on our end until their service is operating normally.

We’re currently investigating an issue causing image and video posts for Twitter/X to fail with the error: <i>“Upload initialization failed”</i>. We’re sorry for the trouble and will share updates as we learn more.

This incident has been resolved, Inbox usage is back to normal

We are currently investigating the issue.

This incident has been resolved, Inbox usage is back to normal

We are currently investigating the issue.

The fix has been implemented, this incident is resolved

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

We identified an issue regarding Inbox loading indefinitely. We are working on a fix at the moment.

The fix has been implemented, this incident is resolved

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

We identified an issue regarding Inbox loading indefinitely. We are working on a fix at the moment.

Twitter/X has acknowledged issues with their API (see: https://docs.x.com/status#). We've implemented a workaround to help prevent post failures on our end until their service is operating normally.

We’re currently investigating an issue causing image and video posts for Twitter/X to fail with the error: “Upload initialization failed”. We’re sorry for the trouble and will share updates as we learn more.

Comment syncing and replies on Instagram ads are now working normally again. Thanks for your patience as we resolved the issue.

We’ve released a fix for this Instagram ad comment issue. We're monitoring to confirm it's fully resolved. Thank you for your patience.

We're currently experiencing an issue where Instagram ad comments are not appearing in the inbox. In addition, replies to existing Instagram ad comments may not be functioning as expected. Our team is working on a fix. Thank you for your patience and understanding.

We're currently experiencing an issue where Instagram ad comments are not appearing in the inbox. Our team is working on a fix. Thank you for your patience and understanding.

Comment syncing and replies on Instagram ads are now working normally again. Thanks for your patience as we resolved the issue.

We’ve released a fix for this Instagram ad comment issue. We're monitoring to confirm it's fully resolved. Thank you for your patience.

We're currently experiencing an issue where Instagram ad comments are not appearing in the inbox. In addition, replies to existing Instagram ad comments may not be functioning as expected. Our team is working on a fix. Thank you for your patience and understanding.

We're currently experiencing an issue where Instagram ad comments are not appearing in the inbox. Our team is working on a fix. Thank you for your patience and understanding.

This issue has been resolved and BlueSky publishing has returned to normal. We thank you for your patience while we worked on this issue.

We've identified the issue preventing BlueSky videos from publishing and are working on a fix. We appreciate your continued patience.

We're currently experiencing an issue where BlueSky videos are failing to publish. Our team is investigating the issue. Thank you for your patience and understanding.

This issue has been resolved and BlueSky publishing has returned to normal. We thank you for your patience while we worked on this issue.

We've identified the issue preventing BlueSky videos from publishing and are working on a fix. We appreciate your continued patience.

We're currently experiencing an issue where BlueSky videos are failing to publish. Our team is investigating the issue. Thank you for your patience and understanding.

The earlier issue affecting account connection and token renewal with X/Twitter has been resolved.Thank you for your patience.

X/Twitter is experiencing a partial outage, affecting account connection and token renewal. X/Twitter has acknowledged the issue at https://docs.x.com/statusThank you for your patience, we will continue to monitor the issue.

The earlier issue affecting account connection and token renewal with X/Twitter has been resolved. Thank you for your patience.

X/Twitter is experiencing a partial outage, affecting account connection and token renewal. X/Twitter has acknowledged the issue at https://docs.x.com/status Thank you for your patience, we will continue to monitor the issue.

This issue has been resolved, and LinkedIn posts and their comments are now syncing as expected. Thank you for your patience while we worked to resolve it.

We're investigating issues syncing LinkedIn posts into the calendar and fetching comments from LinkedIn posts to the inbox. We will provide updates as we learn more.

X / Twitter has now marked the issue as resolved: https://docs.x.com/status Thank you for your patience while we awaited their resolution.

X / Twitter is currently experiencing intermittent outages. As a result, you may encounter issues with account connections, failed publishing attempts, or difficulties replying in the inbox. We are monitoring the situation at https://docs.x.com/status Thank you for your patience!

Meta has rolled out a fix for the issue, and it's now possible to add a Threads account or renew an expired token. Thank you for your patience while we awaited their resolution.

We are continuing to investigate this issue.

We are currently seeing some issues when trying to connect a Threads account or renewing an invalid token. Our team is investigating and we will post an update as soon as we have more information.

This issue is resolved, and YouTube channels can now be added as expected. Thanks for your patience as we worked through this with Google.

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

Our team is actively investigating the issue alongside with Google, and we will provide updates as we learn more. We apologize for the inconvenience and appreciate your patience.

This incident has been resolved.

A fix has been implemented and we are monitoring results

Our team has identified the issue and is currently working on a fix, we will provide updates as soon as possible. We apologize for the inconvenience and appreciate your patience.

This incident has been resolved.

Our team has identified the issue and is actively working on a fix, we will provide updates as soon as possible. We apologize for the inconvenience and appreciate your patience.

X (Twitter) has resolved this issue. Services are back to normal, and you should no longer experience issues with account connections, publishing, or replying in the inbox. Thank you for your patience while this issue was ongoing.

X (Twitter) is currently experiencing intermittent outages. As a result, you may encounter issues with account connections, failed publishing attempts, or difficulties replying in the inbox. We are monitoring the situation and appreciate your patience.

This incident has been resolved.

We are currently experiencing network connectivity issues with one of our main databases AWS. Our team is actively working to resolve this issue and restore normal service as quickly as possible. Thank you for your patience, and we apologize for any inconvenience caused.

Meta has closed the bug https://developers.facebook.com/support/bugs/1190080988960235/ related to Instagram carousels failing. Publishing has returned to normal. We apologise for this inconvenience.

Carousel Posts for Instagram seem to be publishing without failure again, however we are still waiting on an official update from META on this bug here https://developers.facebook.com/support/bugs/1190080988960235/

We apologise for the continued disruption to publishing carousel posts on Instagram. We are waiting to hear from META on this outage as reported here https://developers.facebook.com/support/bugs/1190080988960235/

We are experiencing an issue when publishing to Instagram with the following error (#2) Service temporarily unavailable (code 2, subcode null) 'null - null' This seems to be affecting all 3rd Party tools and is only for carousel-type posts (multi-image). We advise using the send to mobile to complete these until META resolves this issue. We will keep you updated on this issue when we hear more from META. We apologise for this inconvenience.

Meta has resolved the API issue affecting Facebook and Instagram. Some users may need to renew any lost tokens to restore complete functionality. Please note it may take several hours for everything to be fully synced. We appreciate your patience during the disruption and apologize for any inconvenience this may have caused.

The issue has been identified by META and we are waiting on a fix from them to resolve this API issue. Thank you for your patience while we wait for this fix.

We are currently facing an issue due to an unexpected disruption with the Meta API, which is impacting full access to the service. Our team is in close communication with Meta to identify the root cause and expedite the resolution. We are committed to restoring normal service as swiftly as possible. We understand how critical this service is to your operations and sincerely apologize for any inconvenience this may cause. We will provide updates as soon as Meta shares more information or the issue is resolved. Thank you for your patience and understanding.

We are currently experiencing an issue impacting full access to the Meta API. Our team is actively investigating the root cause and working diligently to restore normal service as quickly as possible. We understand the importance of this service to your operations and we apologize for any inconvenience this may cause. We will provide updates as soon as we have more information. Thank you for your patience and understanding.

Meta has rolled out a fix and Instagram publishing is back to normal. Thank you for your patience while we waited for this fix from Meta.

Meta is currently experiencing an API issue that is affecting the ability to publish videos on Instagram. We are closely monitoring the situation and will provide updates as soon as possible.

The issue appears to have been resolved by Meta and the majority of posts are publishing without issue. Thank you for your patience while this issue was ongoing.

Meta is currently experiencing an API issue that is affecting the ability to publish videos on Instagram. We are closely monitoring the situation and will provide updates as soon as possible.

This incident has been resolved.

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

We are currently investigating this issue.

After monitoring the fix that was implemented by Meta, we're seeing that everything is back to normal. We have concluded that the issue has been completely resolved. Thank you for your patience.

Meta has released a fix on their end. We will continue to monitor the situation and provide another update soon.

We're currently experiencing an issue with Facebook's private messaging service that is preventing users from responding to messages. This problem is caused by a technical issue on Meta's end and is limited to Facebook's private messaging feature. Meta has acknowledged this problem, and you can read about it here: https://metastatus.com/messenger. We apologise for any inconvenience and will keep you updated on the status of this issue.

This incident has been resolved.

The maintenance operation on our infrastructure is taking longer than expected. The platform is still not available, it will be back up in the next hour.

Meta have marked this issue as resolved. Please do contact us if you face any issues renewing tokens or adding Pages or Instagram accounts

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

Meta have updated their status page for this issue and their engineers are working on a fix, https://loom.com/i/136c389b08bf43b6b69716f9ba58e5eb https://metastatus.com/graph-api We will keep you updated on when they release a fix for this issue. Thank you for your patience on this matter.

We are currently investigating an issue where users are impacted by not being able to add some pages/Instagram accounts or renewing tokens even though the relevant roles are assigned correctly. There is a reported bug here https://developers.facebook.com/support/bugs/994034301555870/?join_id=f3c066c65ca6f88 and we are also troubleshooting with Meta directly. We are sorry for the inconvenience and will keep you updated as and when we receive more information from Meta.

We can confirm this is incident is now resolved. Thanks for your patience.

LinkedIn have confirmed they are facing an issue that is impacting replies to comments. Agorapulse users may see this error when trying to reply to LinkedIn comments in their Inbox: Error while publishing a comment on Linkedin. java.util.concurrent.ExecutionException: com.linkedin.restli.server.RestLiServiceException [HTTP Status:422]: com.linkedin.restli.client.RestLiResponseException: Response status 422, serviceErrorMessage: ERROR :: /parent :: ReadOnly field present in a create request We are waiting for more information from LinkedIn. We will update date this status with any further developments. We apologise for this inconvenience.

Meta have confirmed they have resolved this issue. Thank you for your patience during this outage. https://metastatus.com/graph-api

The Meta team has acknowledged the current video auto-publishing outage and is currently working on a resolution. We'll be monitoring the issue while we wait for this resolution. Live updates on their status can be found here https://metastatus.com/

We are continuing to investigate this issue.

We are currently investigating an issue where video posts for Instagram are failing to publish, resulting in the following error: Facebook error: Media ID is not available (code 9007, subcode 2207027) 'Cannot Publish - The media is not ready for publishing, please wait for a moment Posts with photos are publishing as normal. As soon as we get more information from Instagram we will update this status. Meta have acknowledged the issue as you can read here https://metastatus.com/graph-api Please accept our apologies for this issue while we wait for their fix

This incident has been resolved.

We're still monitoring the issue which seems to be resolved now. Syncing Instagram direct messages are back to normal and reply to direct messages now appear to deliver successfully.

We are currently investigating an issue where Instagram direct messages are not syncing and replies are failing with the error message: 'Received Facebook error response of type OAuthException: (#100) The thread owner has archived or deleted this conversation, or the thread does not exist. (code 100, subcode 2534001)' We are checking with Instagram in relation to this issue. Please subscribe to receive additional updates. We apologize for the inconvenience.

Facebook has implemented a fix which is now live and video publishing has returned to normal. We are very sorry for the inconvenience this issue may have caused and thank you for your patience while we waited for the fix from Facebook.

We are facing an issue where Video posts for Instagram are failing to publish. Facebook/Instagram are looking into this issue here https://developers.facebook.com/support/bugs/429918432227032/?join_id=f1c73a91905e174 and we are waiting for more information on this issue. We apologize for the inconvenience and will post another update as soon as we learn more.

After monitoring the fix that was implemented by Instagram, we're seeing that Instagram publishing is back to normal. We've concluded the issue has been fully resolved. Thank you for your patience.

Instagram have implemented a fix for the publishing issue and at the moment all posts are starting to publish successfully. We will continue to monitor this situation to ensure the fix is working completely

We are currently investigating an issue where Instagram posts aren't currently publishing successfully and receive the following error message An unexpected error has occurred. Please retry your request later. (code 2, subcode null) We are checking with Instagram in relation to this issue.

While Facebook have not yet marked this issue as resolved, there has been no further incidents of failed posts since Feb 6th so we will close this incident. We will continue to monitor this bug with Facebook. Thank you for your patience while this matter was ongoing.

Publishing to Instagram has returned to normal, however Facebook still have their bug open https://developers.facebook.com/support/bugs/340584821269339/, we will continue to monitor this until they mark the bug as resolved. Thank you for your patience while we wait.

We are continuing to investigate this issue.

We are currently investigating an issue with Instagram publishing, where you receive the following error message " Received Facebook error response of type OAuthException: The requested resource does not exist (code 24, subcode 2207006) 'Media Not Found - The media cannot be found.' The issue has been reported to Facebook and we are waiting for feedback from them on this issue. https://developers.facebook.com/support/bugs/672632157209046/ https://developers.facebook.com/support/bugs/340584821269339/ https://developers.facebook.com/support/bugs/665158288165343/

Thank you for your patience, the site is up and running again. Have a lovely day!

We're currently releasing an updated infrastructure for our front-end application which has caused some resources to be unavailable preventing the Agorapulse desktop app to load correctly. The Agorapulse mobile app has not been affected. We will resolve this status as soon as the update has been completed. Thank you for your patience.

We deployed a fix, and the issue is now resolved: User's mentions in replies are working correctly both for Facebook and Twitter. Thanks again for your patience!

The issue is now fixed for Twitter. We're still working on a solution for Facebook and will keep you updated. Thanks for your patience.

We are continuing to monitor for any further issues.

We are currently facing an issue with mentions of users within the Inbox replies for Twitter and Facebook. Twitter: When you reply to a mention with the checkmark box ticked by default, replies are published as regular tweets and not replies. For now, the workaround is to manually mention the user(s) within your reply. This will publish a proper reply and not a regular tweet. Facebook: When you reply to a comment with the checkmark box ticked by default, your comment is published without the user’s mention. Our team is working on a fix and we’ll keep you updated.

This issue seems to be resolved by YouTube, and it is possible now to hide / mark as spam / approve pending comments and ban users again. Thank you for your patience while we waited for YouTube to fix this issue

Update: Unfortunately this issue is coming directly from YouTube and other 3rd party tools are also affected. We are sorry for this inconvenience and are waiting for more information from them on this issue https://stackoverflow.com/questions/70032610/youtube-api-setmoderationstatus-to-heldforreview-not-working

We are currently investigating an issue with YouTube inbox management, where it is impossible to hide / mark as spam / approve pending comments, or ban users at the moment. We are really sorry for the impact this may have on your workflow and our technical team is currently working on finding the issue as a top priority . We apologise for this inconvenience and will do our best to solve this issue as quickly as possible

We are delighted to share that everything has returned to normal. Thank you for your patience while Facebook and Instagram are experiencing downtime.

It appears that Instagram is having trouble with the inboxes of Business accounts. Natively, Business Account inboxes are not loading properly. This has led to DM reply failures here on Agorapulse, with the following error message: Received Facebook error response of type GraphMethodException: Unsupported get request. Object with ID 'xxxxx' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api (code 100, subcode 33) Instagram has also been up and down natively. We are keeping a close eye on the scenario and will update just as soon as we can. Thank you for your patience in this matter.

We are delighted to share that everything has returned to normal. Thank you for your patience while Facebook and Instagram are experiencing downtime.

Facebook and Instagram appear to be back up. We have noticed slow performance natively, which leads us to want to monitor the situation further before we give the all clear. For the moment, the inbox is behaving normally for both Facebook and Instagram, and scheduling is back as well. When we have confirmation that things are resolved and working smoothly, we'll update our status once more.

It seems that both Facebook and Instagram are experiencing downtime. Both natively and over the API. Our customers will not be able to log into Agorapulse using Facebook login. This will affect all aspects of publication and inbox items for both Facebook and Instagram. We are keeping an eye on the situation and will continue to update as we can. Thank you, in advance, for your patience.

This issue has been resolved and you should be able to renew your Facebook token again. We thank you for your patience while we worked on this issue.

The issue has now been identified and a fix is underway.

We are currently investigating an issue with Facebook Token renewals where some users are not able to renew the token, despite having the correct roles to do so. Our Technical team are in touch with Facebook and as soon as we have any further information we will update here. We are sorry for the inconvenience this may cause.

We are delighted to see that everything has returned to normal. Thank you for your patience while Instagram/Facebook was an issue.

Instagram is looking more stable at the moment. Natively, it seems to be behaving as it should. Due to the API being down, when replying to Instagram DMs or story mentions our customers have reported seeing an error message that states the item has been externally deleted. This causes Agorapulse to mark the item as deleted. Due to this false warning of deletion, our customers won’t be able to reply correctly to these items from Agorapulse until the API is fully restored. We are vigilantly monitoring the situation and thank you for your understanding.

It appears that Instagram is down once again - this affects Instgram natively as well as through the API. We are keeping a close eye on this, but our customers will likely experience all components of Instagram including publishing, inbox, listening and reports. We are continuing to monitor the situation closely and thank you for your patience.

Instagram's API seems slowly be coming back to full speed. We are continuing to keep an eye on the scenario.

Instagram is down at the moment, both natively and over their API. While it's down our customers may experience issues with all components of Instagram including publishing, inbox, listening and reports. Due to the API being down, when replying to Instagram DMs or story mentions our customers have reported seeing an error message that states the item has been externally deleted. This causes Agorapulse to mark the item as deleted. Due to this false warning of deletion, our customers won’t be able to reply correctly to these items from Agorapulse until the API is fully restored. We are continuing to monitor the situation and thank you for your patience.

We are very happy to update you that this issue has been resolved and everything is back to normal again. Thank you for your patience while we worked on this.

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

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

We are facing an issue with users not being able to reply to Facebook PMs' older than 24 hours with the error message (#100) Cannot tag messages with 'HUMAN_AGENT' without prior approval (code 100, subcode 2018276) And for Instagram DM's replying to them may fail with the error message: (#10) App doesn't have Human Agent Tag Access (code 10, subcode 2534044) We are working closely with Facebook to resolve this issue. We will update date this status with any further developments. We apologise for this inconvenience.

Twitter publishing is back to normal, and we are not seeing any further incidents with this error Status code: 503, reason phrase: Service Unavailable. Thank you for your patience while this issue was being investigated.

Some of our customers have reported seeing an error when trying to publish posts to Twitter with a video or image attached. You may see a warning that the post failed with the following error: Status code: 503, reason phrase: Service Unavailable We're currently investigating the error and will update as soon as we can.

We are happy to report that Facebook has marked this issue as resolved! (https://developers.facebook.com/status/issues/492652922187445/) Thank you for your patience while we waited on this fix and we apologise for any inconvenience this outage caused

It is now possible to log in to Agorapulse with Facebook and also add an Instagram account, we are still experiencing issues with adding a Facebook page. https://developers.facebook.com/status/dashboard/ We will keep monitoring this situation and will keep you updated on any resolution from Facebook. Thank you for your patience on this matter.

We are currently impacted by an issue with Facebook https://developers.facebook.com/status/dashboard/ This is prevent logging to Agorapulse with Facebook (but email/ password is working perfectly) and also connecting Facebook Pages and Instagram accounts. We are closely monitoring this and will update you as soon as we have more information. We apologise for this inconvenience.

We are happy to report that Facebook have resolved the issue https://developers.facebook.com/status/issues/303002637919542/ Thank you for your patience while this issue was being investigated

We are currently facing an issue with Instagram publishing due to what appears to be downtime on Instagram. You may see either of these errors Publishing : Facebook error: An unexpected error has occurred. Please retry your request later. (code 2, subcode null) 'null - null' (5 retries) Or when trying to reply: Error while publishing a comment on Instagram. Received Facebook error response of type OAuthException: This API call does not support the requested response format (code 20, subcode 1772107) 'Instagram Comment Not Added - Your Instagram comment was not added - please try again' We are sorry for this inconvenience and will update you when things return to normal

We are very happy to let you know this issue is fully resolved with Facebook now and we're no longer seeing any errors. Thank you for your understanding while we waited for the fix to be pushed out by Facebook.

Facebook has pushed a fix through for this issue and we are seeing a dramatic improvement. Please bear in mind it can take a few hours for everything to return to normal. https://developers.facebook.com/support/bugs/448867966487671/ https://developers.facebook.com/status/dashboard/

We are continuing to investigate this issue.

We are still waiting feedback from Facebook on this issue

We are aware of an issue with Facebook's network randomly affecting posts in the publisher and replies to comments within the inbox. They have this current bug open https://developers.facebook.com/support/bugs/448867966487671/ and have updated their status page here https://developers.facebook.com/status/dashboard/ with a degraded performance. During this time, you might see the following publishing error: "Facebook error: Please reduce the amount of data you're asking for, then retry your request (code 1, subcode null) 'null - null'" Please be aware that despite this error message, your content and reply may still be successfully published to Facebook. We will continue to update this incident when we have more information from Facebook

We are very happy to let you know that Facebook confirmed that the incident has been resolved: Replying to Private Messages is now working. ==> https://developers.facebook.com/support/bugs/484143269217803/ Please note that replying to people that got in touch for the first time during the incident (between approx 10:00 AM and 11:00 PM, December, 2nd) is still not possible. Users would have to start a message with your pages again before you are able to send them messages. Thank you for your patience while we waited for this to be resolved.

Issue seems to be partially resolved, we’re still monitoring the issue with Facebook, here: https://developers.facebook.com/support/bugs/484143269217803/ For now, you can : - Reply to people who send you a new message ==> for new conversations (people who send a new message to your page for the first time since 11 PM, December 2nd) ==> for previous conversations: even if the previous messages have been impacted by the bug, it’s possible to answer them since 11 PM, December 2nd But you still can’t : - Reply to people that got in touch for the first time during the incident yesterday (so between approx 10:00 AM and 11:00 PM, December, 2nd) We apologize for any inconvenience and will keep you updated on the status of this issue. Thanks for your patience.

Facebook are currently experiencing an issues with replying to Private messages, showing this error (#551) This person isn't available right now Facebook have a ticket on this issue here : https://developers.facebook.com/support/bugs/484143269217803/ We apologise for any inconvenience and will keep you updated on the status of this issue.

We are seeing an improvement and publishing has returned to normal. Thank you for your patience while we worked with Instagram on this issue

We are currently investigating an issue with Instagram publishing, as we are seeing a higher rate of failed posts with this error code : Facebook error: The requested resource does not exist (code 24, subcode 2207008) 'Media builder not found - The media builder with creation ID {ID goes here} does not exist or has expired. We will continue to investigate directly with Instagram. We are sorry for the inconvenience this may cause

This issue has been resolved and video publishing has returned to normal. Thank you for your patience on this matter

We've identified an issue pertaining to Facebook posts containing a video. Some our customers have reported that when they publish a Facebook post containing a video there will be a delay from the time of publication to the time the post is available on Facebook. This does not effect Facebook posts with text only, or Facebook posts with an image. We have a direct support ticket open with Facebook and will continue to monitor the situation closely. Thank you in advance for your patience.

Thank you for your patience while we resolved the Instagram hashtag listening searches.

Thank you for your patience while we wait for this issue to be resolved. Please note: we are currently not synchronising listening hashtag searches on Instagram as a direct impact from this bug. We apologise for this inconvenience and hope to see this issue resolved soon.

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

Some of our customers have reported an issue with Instagram involving their tokens dropping out. Facebook is aware of the issue and there is a direct ticket open with them about the issue: https://developers.facebook.com/support/bugs/342530583596558/ We're currently investigating the issue and thank you in advance for your patience.

We are no longer facing an issue to add or publish to groups. Thank you for your patience on this issue

We are currently investigating an issue preventing new groups to be added to Agorapulse and also there are issues with Group publishing. https://developers.facebook.com/support/bugs/297366018274304/ We are really for this inconvenience.

Linkedin publishing is back to normal. Thank you for your patience during this issue.

We are currently experiencing issues with LinkedIn publishing. You may experience a failed post to both LinkedIn Company & Personal pages for posts that contain video or Images with the following message: "Media upload status failed with status after 10 retries for asset..." Posts without video or images attached are not affected at this time. We are awaiting a fix from LinkedIn. Thank you for your patience.

This issue has been resolved

Facebook has reported an API issue which affects our ability to sync inbox items in real time. This affects the following: - Organic comments - Mentions - Story insights The status has been reported here: https://developers.facebook.com/status/issues/1556831074476310/ While real time syncs are affected, we can still synchronize comments and story insights hourly. We are currently monitoring the issue with Facebook and hope to see an update soon. We thank you for your patience.

We are no longer seeing any issues replying to comments. Thank you for your patience on this issue.

We're still monitoring the issue which seems to be resolved now. We're in touch with Facebook and we are awaiting their feedback on the scenario and their fix. Thanks for your patience.

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

We are continuing to investigate this issue.

Facebook is currently facing an issue with their API. As a result, replying to a comment returns an error message, even if the reply is correctly sent. You will receive the following error message: Facebook error: An unknown error occurred (code 1, subcode 99) 'null - null' This issue has been reported <a href="https://developers.facebook.com/support/bugs/2638226053100522/">here</a> We apologize for any inconvenience that may be caused by this issue and will keep you updated.

We are very happy to let you know that Facebook confirmed that the incident has been resolved. Replying to Private Messages is now working. Thank you for your patience while we waited for this to be resolved

We are continuing to investigate this issue.

We are currently experiencing an error when our customers try to respond to Facebook private messages. The error code looks like: Facebook error: (#33) This object does not exist or does not support this action (code 33, subcode null) Replying to comments and publishing does not seem to be affected at this time, only Facebook PM's. We are currently investigating the issue, and there is a direct ticket open with Facebook here: https://developers.facebook.com/support/bugs/733783060776081/ Thank you for your patience while we continue to monitor the situation.