Thursday, May 2, 2013

Gmail down in some parts of the world? error 502

14th May 2013



TimeDescription
5/13/13 2:25 PM
The problem with Gmail should be resolved. We apologize for the inconvenience and thank you for your patience and continued support. Please rest assured that system reliability is a top priority at Google, and we are making continuous improvements to make our systems better.
5/13/13 1:50 PM
Our team is continuing to investigate this issue. We will provide an update by 5/13/13 2:50 PM with more information about this problem. Thank you for your patience.
The issue is affecting less than 0.75% of users. The affected users are located in India, Middle East and South East Asia. The errors may appear sporadic and could go away when the page is refreshed.
5/13/13 1:35 PM
We're investigating reports of an issue with Gmail. We will provide more information shortly.
Users are receiving an error with number 502.


13th May 2013 Gmail down 502 error

502.
That’s an error.
The server encountered a temporary error and could not complete your request.
Please try again in 30 seconds.
That’s all we know.
Still not reported on the google app dashboard
http://www.google.com/appsstatus#hl=en&v=status&ts=1368430147768


TimeDescription
5/2/13 1:13 PM
The problem with Google Mail should be resolved. We apologize for the inconvenience and thank you for your patience and continued support. Please rest assured that system reliability is a top priority at Google, and we are making continuous improvements to make our systems better.
Users were experiencing 502 errors and latency when accessing email.
5/2/13 12:32 PM
We're investigating reports of an issue with Google Mail. We will provide more information shortly.



Service update

Visit the Apps Status Dashboard for additional updates.

May 2, 2013 12:02:00 AM PDT

We're investigating reports of an issue with Google Mail. We will provide more information shortly.







Google

502. That’s an error.

The server encountered a temporary error and could not complete your request.

Please try again in 30 seconds. That’s all we know.




HTTP Error 502 Bad gateway
Introduction
A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request.
This usually does not mean that the upstream server is down (no response to the gateway/proxy), but rather that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data. Given that Internet protocols are quite clear, it often means that one or both machines have been incorrectly or incompletely programmed.
http://www.checkupdown.com/status/E502.html

No comments:

Post a Comment