Among the most used social networks. We obviously find facebook, instagram and whatsapp. These last two are part of the redemptions made by the first social network used. And which therefore share the same server. This is why the Nigeria WhatsApp Number List bug that occurred on july 3 impacted these 3 social networks at the same time. Your agency specializing in social networks looks back on what happened yesterday. The breakdown of facebook, instagram and whatsapp yesterday during the day. A bug occurred on the social networks belonging to the facebook group.
Internet Users Could No Longer Listen to the Audios Sent
This bug has impacted both individuals and professionals, and many people have been indignant on social networks. With the aim of making their dissatisfaction known to the american firm. Twitter being the Nigeria WhatsApp Number List only social network to function. It is above that facebook has decided to communicate with its users. In its tweet, the mark zuckerberg-owned network apologizes. For the inconvenience and notes that its teams are trying to resolve the issue as quickly as possible. It was in response to this tweet that, this morning around 2 a.M. (paris time). Facebook announced the resolution of the problem encountered, and that everything was operational again.
According to the Down Detector Website All Countries Were
It was in response to this tweet that, this morning around 2 a.m. (Paris time), Facebook announced the resolution of the problem encountered, and that everything was operational again . According to the Down Detector website , not all countries were affected by this bug. Only the countries of North and South America, as well as Europe are affected. Yesterday Nigeria WhatsApp Number List afternoon, the social networks Facebook, Messenger, Instagram and WhatsApp encountered problems. Indeed, Internet users could no longer see the photos and videos, nor listen to the audios on Messenger. This problem has affected European countries, but also those of North and South America. It was resolved this morning, a few hours after the bug started.