since meteor support does not want to answer me the reason, i have to ask might anyone of you faced issue where your app does not respond on primary domain? My domain a.foo.com has cname to iirokak.eu.ingress.galaxycloud.app and app does not response on that primary domain in few minutes. Then it comes back up again after few minutes. The domain that meteor metal cloud gives works all the time.
I have several app in different organizations and many of them have this problem. This never happened in old galaxy cloud.
I’m sorry this has continued, and that our responses have not given you the clear resolution you need. Galaxy’s priority is to address problems affecting our customers, and in this case we have not resolved yours definitively yet.
We know this is affecting a subset of customers in our Europe region. The affected applications can remain healthy while requests intermittently fail in the routing and proxy layer used by some custom domains, which is why the Galaxy-provided domain may remain available while a primary domain briefly does not respond.
We are treating this seriously and are working directly with our underlying infrastructure providers to identify and correct the cause permanently. We have applied mitigations and are moving affected traffic to a more resilient proxy configuration, but I want to be clear: we are not considering this resolved until the intermittent failures have stopped.
Our earlier updates said we were investigating and would share more information. That was accurate, but it did not provide the definitive resolution you need, and we should have communicated that more clearly.
We will post here again when we have a confirmed update on the permanent fix.