New Delhi: Popular social media application Instagram crashed on July 3, in the US and UK and soon its parent company Facebook and sister company Whatsapp started to face serious technical difficulties. Also Read - Bollywood Drug Scandal: WhatsApp Gives Clarification on Security After NCB Retrieves Chats

Users facing trouble with any of the three applications are advised to remain calm and report it to respective apps. Also Read - Facebook, Twitter, YouTube Ink Pact With Advertisers For 'Common Definition' on Hate Speech

According to tracking website Down Detector, the issues started at around 2:49 PM BST. The outrage monitor also stated technical difficulties were particularly faced on the eastern side of the United States and have also seemed to have occurred in Europe, South America and East Asia. Also Read - No Coercive Action Against Facebook Chief in Delhi Riots Case Till Oct 15: Supreme Court to Delhi Assembly

Users have taken Twitter, which continues to stand tall, to rant about the worldwide app crash.

Not really the best day for Instagram and Facebook to crash, I wanna post my pics 😭😂 — Ryan (@rybrow1) July 3, 2019

I would prefer if you could fix all your crash — Sylvainlazureen (@Sylvainlazureen) July 3, 2019

“Use Facebook and Instagram to help with your business!” “You can’t promote on Instagram without a Facebook account!”

Ok fine..

*reactivates Facebook to make promos on Instagram*

*Both crash on the same day*

Me: pic.twitter.com/F0gqBJiHjS — Vanillak1tty (@Vanillak1tty) July 3, 2019

On Instagram, over 2,100 users have reported trouble in updating their feed as they are unable to post anything new. On the other hand, Facebook is mainly facing trouble in displaying photos.

Meanwhile in India, while Whatsapp chat interface and Instagram posts are working fine, sharing any form of media appears to be frozen. Facebook users also seem to be facing the same issue in India.

All three social media platforms are owned by Facebook. In a previous incident of a major crash, the parent company had blamed the problem on a server issue that lasted for hours.