Facebook outages have bee reported across the world on July 3. (Google Maps)

Facebook, Instagram Outages Reported Across the World

A number of Facebook and Instagram users have reported outages and service problems on July 3.

According to Downdetector.com, problems have been reported across the United States and Europe.

A number of people said they can’t see pictures on Facebook.

“Photos not showing on Facebook. When is this going to get resolved??” wrote one person.

Some people, however, said Instagram and Facebook are down entirely.

instagram is down. facebook is down. twitter DMs are down. WhatsApp is down. the end times are upon us. #instagramdown pic.twitter.com/HKXyRIUUaw — Alex Phillips (@Alexpofficial_) July 3, 2019

who else come here just to confirm whatsapp facebook and instagram is down 😅 #whatsappdown — Zeeshan Dogar (@realzeshandogar) July 3, 2019

Retweet if Facebook is down — FacebookDown (@UghFacebookDown) July 3, 2019

Yung instagram down at facebook down din pati ba twitter down din?#ALDUB207thWeeksary — Mac Manalo MCN🌞 (@ManaloMac) July 3, 2019

So… WhatsApp having problems, #instagramdown #facebookdown.. I guess Twitter is the last one standing then..? XDD pic.twitter.com/VU8ddpDve9 — 제스, 그리고 첸 | ∀Σ ♥ ∀ΔΣ (@b2utifulife) July 3, 2019

In April, Facebook went down for tens of millions of people for at least 12 hours.

At the time, the company blamed a “server configuration change,” and apologized for the outages.

Oh WhatsApp, Facebook and Instagram are down

and I don’t know how to use twitter Me:#whatsappdown pic.twitter.com/fiDGO4Yr21 — Made In Benin 052🕊 🇳🇬 (@Sobsoil) July 3, 2019

Last August, Facebook went down for about 45 minutes, which was described as a relatively lengthy outage for the firm.

Earlier, in 2010, Facebook experienced a 2.5-hour outage that at the time the company called its “worst outage we’ve had in over four years.”

“The key flaw that caused this outage to be so severe was an unfortunate handling of an error condition,” the company announced. “An automated system for verifying configuration values ended up causing much more damage than it fixed.”