Time: Dec. 4, 2020, 8:29 a.m.

Status: Resolved

Update: 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.

Time: Dec. 3, 2020, 8:33 a.m.

Status: Monitoring

Update: 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.

Time: Dec. 2, 2020, 1:22 p.m.

Status: Identified

Update: 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.

Time: Dec. 4, 2020, 8:29 a.m.

Status: Resolved

Update: 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.

Time: Dec. 3, 2020, 8:33 a.m.

Status: Monitoring

Update: 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.

Time: Dec. 2, 2020, 1:22 p.m.

Status: Identified

Update: 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.

Time: Oct. 31, 2020, 9:41 a.m.

Status: Resolved

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

Time: Oct. 31, 2020, 8:47 a.m.

Status: Investigating

Update: 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

Time: Oct. 31, 2020, 9:41 a.m.

Status: Resolved

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

Time: Oct. 31, 2020, 8:47 a.m.

Status: Investigating

Update: 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

Time: Oct. 27, 2020, 8:14 a.m.

Status: Resolved

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

Time: Oct. 26, 2020, 7:42 p.m.

Status: Investigating

Update: 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.