If you were not able to receive or download images on Facebook, Instagram, WhatsApp or Messenger yesterday then it was not your fault. Neither was it the fault of your telecom operators. The fault was on the part of Facebook which owns WhatsApp, Instagram and Messenger too. Therefore, all the services run on the same infrastructure. Yesterday, Facebook’s servers suffered an outage which caused all these services to not work properly.
However, it is worth mentioning that the outage was not as severe as we have seen previously. We tried using the services and the comments on Facebook, Instagram as well as messages on Messenger, WhatsApp were going and coming normally. The problem was in receiving and downloading images that were sent. We have now found out that the problem was in Facebook’s CND or Content Delivery Network. This is where all the media such as Images, Videos and other such files sent across Facebook’s services are stored.
Facebook image CDN is down, affecting Facebook, Instagram and WhatsApp
“x-fb-response-reason: No server is available for the request” pic.twitter.com/2WtNiJd6jS
— Jane Manchun Wong (@wongmjane) July 3, 2019
According to Facebook, there was a routine maintenance operation scheduled for its services. However, there was a bug which got triggered in this maintenance check and caused the services to stop working. The company also says that its services have been restored back to normal now. A Facebook spokesperson said that “Earlier today, some people and businesses experienced trouble uploading or sending images, videos and other files on our apps and platforms. The issue has since been resolved and we should be back at 100% for everyone. We’re sorry for any inconvenience,” referring to the outage.
Although Facebook says that the bug caused problems in uploading images, we were able to upload images on WhatsApp and Facebook while we cannot say the same for Instagram and Messenger as we did not try it. However, we can also confirm that no one was able to download images on any of the platforms as an error was shown.