All Systems Operational
Manager ? Operational
Facebook Publishing & Data Processing ? Operational
Twitter Publishing & Data Processing ? Operational
Instagram Publishing & Data Processing ? Operational
Linkedin Publishing & Data Processing Operational
Youtube Data Processing Operational
Facebook Timeline Contest ? Operational
Facebook Page Barometer ? Operational
Web site ? Operational
Cloud Provider ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Agorapulse Main API - Response time
Fetching
Facebook Barometer - Response time
Fetching
Facebook Timeline Contest - Response time
Fetching
Twitter Analytics - Response time
Fetching
Past Incidents
Aug 12, 2020

No incidents reported today.

Aug 11, 2020

No incidents reported.

Aug 10, 2020
Resolved - We are no longer seeing any issues replying to comments. Thank you for your patience on this issue.
Aug 10, 09:42 CEST
Monitoring - 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.
Aug 3, 18:55 CEST
Identified - The issue has been identified and a fix is being implemented.
Aug 3, 11:58 CEST
Update - We are continuing to investigate this issue.
Aug 3, 11:58 CEST
Investigating - 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 here

We apologize for any inconvenience that may be caused by this issue and will keep you updated.
Aug 3, 11:58 CEST
Aug 9, 2020

No incidents reported.

Aug 8, 2020

No incidents reported.

Aug 7, 2020
Resolved - 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
Aug 7, 08:13 CEST
Update - We are continuing to investigate this issue.
Aug 6, 22:44 CEST
Investigating - 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.
Aug 6, 22:41 CEST
Aug 6, 2020
Aug 5, 2020
Resolved - We are very happy to let you know that Facebook confirmed that the incident has been resolved. Posts containing mentions are now correctly published from Agorapulse.

Thank you for your patience while we waited for this to be resolved
Aug 5, 09:47 CEST
Monitoring - The incident seems to be resolved as the error hasn't been reproduced today. We're still waiting for a confirmation from Facebook to close this issue.
Thank you for your patience.
Jul 31, 15:30 CEST
Identified - Facebook is currently facing an issue with their API. As a result, posts containing mentions are currently not published from Agorapulse.
You will receive the following error message: Facebook error: (#2) Service temporarily unavailable (code 2, subcode null) 'null - null'

This issue has been reported here

We apologize for any inconvenience that may be caused by this interruption
Jul 30, 14:39 CEST
Aug 4, 2020
Resolved - Thank you for your patience while we monitored this situation. The issue looks to have been resolved by Linkedin who confirmed the site-wide bug over the weekend.
Aug 4, 11:33 CEST
Update - We're still monitoring the issue which seems to be resolved now. We're in touch with LinkedIn and we are awaiting their feedback on the scenario and their fix. Thanks for your patience.
Aug 4, 11:24 CEST
Monitoring - Some of our customers have reported failed posts when trying to publish to LinkedIn profiles and pages. The failed posts are accompanied by the following error code:

"Publishing failed: com.linkedin.restli.client.RestLiResponseException: Response status 409, serviceErrorMessage: com.linkedin.content.common.ResponseException: Content is a duplicate of urn:li:share:6696084791676276736"


We've opened a direct ticket with Linkedin and we are currently working with them towards a solution. We thank you for your patience.
Aug 3, 21:26 CEST
Aug 3, 2020
Aug 2, 2020

No incidents reported.

Aug 1, 2020

No incidents reported.

Jul 31, 2020
Jul 30, 2020
Jul 29, 2020

No incidents reported.