I have an open support case for this as well. It seems to be a known issue
they are working on for 1+ months. Not sure when it will be fixed.
Den fredag 23 mars 2018 kl. 20:24:30 UTC+1 skrev Anu V:
> Backends are healthy, I found this 502 errors across my few projects using
> All instances are able to access and work normally, I've tested using curl
> to send a request directly to instance's private ip and it works all the
> On Saturday, March 24, 2018 at 2:07:30 AM UTC+7, Navi Aujla (Google Cloud
> Support) wrote:
>> Hello Anu,
>> The "*failed_to_connect_to_backend" *error message indicates that load
>> balancer is failing to connect to backends. There could be many possible
>> reasons for it. For example: Unhealthy instance if reported by health
>> check, incorrect URL mapping
>> high backend utilization causing backend not to respond to the load
>> balancer requests. You can refer to this thread
>> more information and check instance system/error and access logs.
>> On Friday, March 23, 2018 at 9:06:00 AM UTC-4, Anu V wrote:
>>> I'am experiencing too many 502 errors from Load Balance and the
>>> instances are working fine. (
>>> @type: "
>>> statusDetails: "failed_to_connect_to_backend"
>>> I've also found that this happen on my few projects starting about 12
>>> hours ago, I've checked https://status.cloud.google.com/ and it said
>>> all working fine.
>>> I cannot upgrade support level to create the ticket, so I am posting it
>>> here to ask if anyone having the same problem as I am?
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.