502 errors with Custom Google Workspace service URLs?

[icrew]

Hello:

Here at UC Berkeley, we've got custom URLs set up for the Google Workspace mail, calendar, and drive, as described at https://support.google.com/a/answer/53340?hl=en

Recently, for me and a colleague, we've been seeing occasional 502 errors when we try to access those custom URLs. For example, going to https://bcal.berkeley.edu will give a 502 error, while going to https://calendar.google.com is working just fine. It doesn't seem to be widespread (or, at least, we're not seeing many tickets from our users about it), but it's certainly annoying.

Here's the error we're seeing (which isn't helpful, really):

When it's happening, it seems to happen regardless of the browser: in both Chrome and Safari on the same machine, but it doesn't happen on a different machine sitting next to the one I'm using (and that's on the same Xfinity internet connection. And my colleague who's reporting it is in a completely different location than I am.

My Google search mojo is also failing me: I'm not having any luck finding anyone else mentioning this.

Any ideas would be most appreciated--it's like a repeated speed bump in my day!

Thanks!

Ian

[juanmo]

502 errors can be related to temporary network or DNS issues. If it works using the calendar URL but not the custom one, it might be a temporary error in the internal Google DNS servers. If it happens very often, I'd recommend collecting HAR files and creating a ticket with Cloud support so they can investigate further.

[KAM]

@icrew Google changed the cname from to ghs.google.com to ghs.googlehosted.com but it looks like you are using googlehosted.

502 is a bad gateway and looks to me like an error on Google's side of things though.  -KAM

[icrew]

Thanks @juanmo and @KAM :

I've captured a HAR file and opened a support ticket with Google on this and am busy trying to get past tier 1 at the moment. 

I'd also be very interested to hear from anyone else that's experienced the same thing, so I can try to convince Google that it's not just us.

Cheers,

Ian

[KAM]

@icrew I typically found two issues with these not working:

DNS issues where the entries weren't done or they used the old ones (before Google used googlehosted CNAMES). 

Make sure your DNS entries match what is listed in your admin section.  Also make sure you don't have DNS replication issues and all your DNS servers for your domain are serving the names correctly.

No other experience of issues.

Regards,

KAM

[login]

 https://support.google.com/a/answer/53340?hl=en 

problen in your dns.

[CloudGuardians]

The issue does not necessarily have to be on Google' side. It can be an issue on your domain's DNS zone. If the CNAME is not being read (let's say 1% of the time, because your domain host or local server is failing 1% of the time) then the mapped URL would not work.
In any case the HAR file should provide some more insights.
Regarding being stuck with the Tier 1 support I can only suggest that you push back on empty replies.