The California based American multinational company Google has finally updated all the issues that are associated with Gmail outage. The services of Gmail were down for a short period, and services came back to normal. The users of Gmail email services suffered an outrage issue which the company resolved.
Due to this, a lot of users of Gmail users took to social media to complain about the issue, and even posted several memes about the outage in the service, along with the trending hashtags like #Gmail and #GmailDown on Twitter. To all these tweets the Gmail’s social media account also responded to its users.
The Gmail email service provider said in a reply to a Twitter user that “Thanks for reporting. We are aware of the issue and are working on a fix. Appreciate your patience,” The provider said.
Even some of the users of Gmail also complained that the problem was precise to some internet service provider services. But Twitter was flooded with a different type of jokes and memes and jokes about the outage using #Gmail and #GmailDown trends to express their disappointment.
Read more: Software giant Oracle joins bid for TikTok’s U.S. operations
Gmail was down for a bit but the fault in the medium was noteworthy as tracked by the DownDetector portal. As per tracking reports, about 62% of users couldn’t send emails and attachments via their Gmail accounts while 25% faced problems in logging. For this disturbance, Google also issued an explanation and guaranteed people that they are trying their best to resolve the hassle. The justification statement released was that “We are investigating reports of an issue with Gmail. We will provide more information shortly.”
According to the rumors, users also reported that Gmail or Google Drive, and Google Meet, Docs are experiencing downtime issues around the globe. Meanwhile, all the issues are resolved now. As we know, Gmail is by far the most liked email service that offers a range of free services to its users. The outage affects millions of users’ tasks, but the issue is resolved now.
