That is a HUGE change from 0.024% this has been changed from a "Service disruption" to a "Service outage".
Also, not sure if it is dependent on your Google login, but mine are all in EST.
11–20 of 55 posts
That is a HUGE change from 0.024% this has been changed from a "Service disruption" to a "Service outage".
Also, not sure if it is dependent on your Google login, but mine are all in EST.
TIMEZONE! I wish they (and others) would include timezone information. I always have to second-guess if its PST, EST, GMT or something else.
TIMEZONE! I wish they (and others) would include timezone information. I always have to second-guess if its PST, EST, GMT or something else.
"The email delays are affecting less than 50% of Gmail users." That is a HUGE change from 0.024% this has been changed from a "Service disruption" to a "Service outage". Also, not sure if it is dependent on your Google login, but mine are all in EST.
Earlier quoted context omitted.
500 million * 0.00024 = 120,000
It's been updated to say "less than 50% of Gmail users" now. We're seeing it across most/all of our accounts.
"The email delays are affecting less than 50% of Gmail users." That is a HUGE change from 0.024% this has been changed from a "Service disruption" to a "Service outage". Also, not sure if it is dependent on your Google login, but mine are all in EST.
PST is broken too - all my clients are PST and most are effected. About half are paid, others are grandfathered free accounts and I see no appreciable difference.
"Thanks for your patience.
Please read below for updates on the status of your issue:
Updates since last message:
This issue has been partially resolved for some users. We expect it to be fully resolved within the next hour. The issue caused severe delays sending emails, especially emails with large attachments. It also caused delays in loading Drive files with large images.
The delays were caused because of a problem with an undersea cable. All parties involved are actively working to: 1) Redirect traffic and add additional capacity to resolve the immediate issue. 2) Fix the problem with the faulty undersea cable. "
Here I was blaming iOS 7.