Give it some time. DNS changes can take a while to propagate.
I can see that it is already resolving from here, although there is an SSL error. That is normal, SSL takes a little longer.
If you change it, then the whole DNS propagation process starts again.
But yes, I noticed last night that something isn’t right. The error suggests something wrong on the hosting provider side. I would suggest reaching out to their support.
Everything is correctly configured in Glide, based on the screen shots you shared.
That just means you should use https://product.cultosglobal.io/
Right now, it is resolving correctly:
$ host product.cultosglobal.io
product.cultosglobal.io is an alias for custom.glideapps.com.
custom.glideapps.com is an alias for edge-proxy.glideapp.io.cdn.cloudflare.net.
edge-proxy.glideapp.io.cdn.cloudflare.net has address 104.16.218.83
edge-proxy.glideapp.io.cdn.cloudflare.net has address 104.16.219.83
edge-proxy.glideapp.io.cdn.cloudflare.net has IPv6 address 2606:4700::6810:da53
edge-proxy.glideapp.io.cdn.cloudflare.net has IPv6 address 2606:4700::6810:db53
But it is giving an SSL error, which again is normal if it was recently changed.
Normally you would see the above error for a short while and then it would start working.
If it doesn’t in this case, I really have nothing more to suggest, sorry.
I have checked it with my team as well, the destination “custom.glideapps.com” itself is showing the error, so the error is on the service provider’s end.