The article has been updated to reflect the latest developments.
What you need to know
- Workspace customers experienced delays of several minutes when sending emails in Gmail.
- Google stated users could try to resend their emails if it's taking too long to reach the intended recipient.
- The company's engineers have fully addressed the problem and are working to complete an internal investigation.
Gmail experienced a severe problem for its Workspace customers as of Thursday morning. According to Google's Workspace status dashboard, customers were experiencing delays when trying to send emails, and Google's teams worked to address the issue, which should now be resolved.
Early Thursday morning, Google's engineers started "mitigation work" to stem the bleeding. However, the company didn't have an ETA for when users can expect such measures to be implemented.
Problems began on Thursday morning at 8:30 am PT, and Google provided an update at 11:15 am PT, saying that its engineers "have taken a few mitigation steps at the highest priority and are actively validating the results."
As the problem continued through the afternoon, Google noted that Workspace customers could try resending their emails if nothing had gone through or if they were taking too long.
As of 12:45 pm PT, Google has updated the status of its ongoing email problems in Gmail for Workspace users. The company stated its engineers have taken the appropriate procedures to mitigate the problem. Additionally, newly created emails should not have any problems moving forward.
The company added that "older emails will be auto retried and should be delivered within the next couple of hours."
Since then, the most recent update arrived with a green checkmark, indicating that Google had fully resolved the issue, with the company stating that email delays were mitigated for the majority of affected users.
"We will publish an analysis of this incident once we have completed our internal investigation," Google says in the status update. "We thank you for your patience while we worked on resolving the issue."