Facebook Suffers its Longest Outage

Facebook Suffers its Longest Outage

Facebook Suffers its Longest Outage

Last year, Telegram stated that it had crossed the 200 million monthly active users mark despite restrictions in markets such as Russia, China, and Iran.

Telegram CEO Pavel Durov said, "I see 3 million new users signed up for Telegram within the last 24 hours". Some Italian users are now seeing a new option within Facebook called "Pay with Facebook" on both Android and iOS apps.

Facebook acknowledged the outage previously via a tweet Wednesday, saying, "We're aware that some people are now having trouble accessing the Facebook family of apps".

The outage affected users for some 12 hours in most areas of the world, with the biggest impact in North America and Europe, according to the tracking website downdetector.com, which suggested that most Facebook users were back to normal.

Telegram benefited big-time from Facebook's massive 14-hour global outage. "Good. We have true privacy and unlimited space for everyone", Durov posted from his Telegram account. "As a result, many people had difficulty accessing our apps and services", a Facebook spokesperson said Thursday.

The company yesterday denied that a DDoS attack had taken down its services.

In some cases, the apps could be accessed but would not load posts or handle messages.

Ironically, the biggest social network of them all made a decision to announce the end of the outage on a rival social media platform, Twitter.

Now the question turns to whether Facebook should reimburse businesses for ads not delivered, or delivered on a semi-functional platform - as reported by Reuters, Facebook is considering whether to refund advertisers for lost exposure due to the problems, though that seems an unlikely outcome.

A Facebook spokesperson, Tom Parnell reportedly stated that the company is aware of the ongoing problems that the users are facing and that company engineers are now working on resolving the issues as soon as possible.

Related news

[an error occurred while processing the directive]