Google first alerted Workspace users on Thursday at 11:30 a.m. ET that some Gmail users might experience a delay in receiving emails. On
Fault detector, the number of reports regarding Gmail increased from 33 at 11:25 a.m. ET to 761 at 1:55 p.m. At 5:03 p.m. ET,
Google issued an update stating that “the email delay issue has been mitigated for the majority of users affected at 2:45 p.m.” and that “a few users may have experienced delays until full mitigation was completed at 2:45 p.m. 4:15 p.m. ET.”
70% of those who submit a report on DownDetector said the problem was receiving their email on time. 16% complain about sending emails on the platform and 14% say they cannot connect to the Gmail server. A Gmail user on DownDetector with the username “Elizabeth” wrote: “Ah, I’m glad to know it’s Gmail and it’s not me, I was scared and didn’t know why I couldn’t create one, so I guess I’ll wait whenever Gmail is available. back to work.”
The chart on DownDetector shows that Gmail was down Thursday morning and afternoon.
Another subscriber to the platform named Michael Hubert wrote: “My emails are not being delivered. It is said that they are sent but no one receives them. » As serious as this may seem, it appears that the problem is limited in scope. After all, 761 reports on DownDetector, while a decent jump from the 33 reports submitted two and a half hours before the peak number, indicates that most people were not concerned or unaware that Gmail was having problems.
Officially, Google says the incident started at 11:30 a.m. ET and ended at 4:15 p.m. ET. The problem lasted for 4 hours and 45 minutes. On the Google Workspace status dashboard, the company wrote: “Some Gmail users experienced a delay in sending emails worldwide for a duration of 4 hours and 45 minutes. Any emails delayed after entering our system were automatically retried and should have been delivered on time. a few hours after attenuation.
As for the cause of the problem, Google wrote: “Based on preliminary analysis, the root cause of the problem appears to be overload in Google Message Router (GMR). Google will write a full incident report in the following days that will provide a detailed root cause. “
