What in the world??
Glide uses Cloudflare CDN. It’s most likely a transient network issue. As it suggests, try again after a few minutes. If the issue persists, then you might need to log a support ticket.
For what it’s worth, that host is reachable from where I am.
$ ping edge.prod.internal.glideapps.com
PING edge.prod.internal.glideapps.com (35.193.40.239): 56 data bytes
64 bytes from 35.193.40.239: icmp_seq=0 ttl=99 time=217.893 ms
64 bytes from 35.193.40.239: icmp_seq=1 ttl=99 time=217.480 ms
64 bytes from 35.193.40.239: icmp_seq=2 ttl=99 time=217.363 ms
64 bytes from 35.193.40.239: icmp_seq=3 ttl=99 time=217.827 ms
64 bytes from 35.193.40.239: icmp_seq=4 ttl=99 time=220.142 ms
ah thanks, it’s working again. So if that happens, it doesn’t have anything to do with me, it’s just a glitch?
Yes, it’s to do with the Glide infrastructure.
These sorts of things probably set off alarms when they happen, so I’d imagine that the Glide DevOps team would be on top of them pretty quickly.
1 Like
oh good. I thought i forgot to pay a bill 
1 Like