We are seeing mainnet gateway-name-proxy deployments fail to come up on all four foundation gateway nodes: node 1 (gent01), node 8 (gent02), node 13 (gent03), node 50 (gent04). The on-chain name and node contracts get created fine, but the gateway workload never reaches the ok state on the node, so no public URL ever becomes usable. We waited as long as 20 minutes on some attempts.
We saw two failure shapes, both pointing at the gateway node not picking up the deployment:
- the deployment push is never acknowledged on the node (the SDK reports
deployment <id> did not appear on node), and
- when the deployment is accepted, the workload never transitions to ready (
zos.deployment.changes / zos.deployment.get keep returning not found until we give up).
All four nodes report up and healthy on Grid Proxy, so this is not a liveness-flag issue, it is the actual deploy/RMB path to these gateway nodes.
For contrast, the exact same flow against QAnet gateway nodes (for example gent01.qa.grid.tf) works reliably and has for a long time, so our signing and tooling path are fine.
No urgency from our side. We have a workaround (we route public ingress through QAnet gateways for now). Flagging it so the team can take a look when there is time, since it makes mainnet public URLs hard to provision today.
Tested 2026-06-13, v3 grid.
We are seeing mainnet
gateway-name-proxydeployments fail to come up on all four foundation gateway nodes: node 1 (gent01), node 8 (gent02), node 13 (gent03), node 50 (gent04). The on-chain name and node contracts get created fine, but the gateway workload never reaches theokstate on the node, so no public URL ever becomes usable. We waited as long as 20 minutes on some attempts.We saw two failure shapes, both pointing at the gateway node not picking up the deployment:
deployment <id> did not appear on node), andzos.deployment.changes/zos.deployment.getkeep returning not found until we give up).All four nodes report
upandhealthyon Grid Proxy, so this is not a liveness-flag issue, it is the actual deploy/RMB path to these gateway nodes.For contrast, the exact same flow against QAnet gateway nodes (for example
gent01.qa.grid.tf) works reliably and has for a long time, so our signing and tooling path are fine.No urgency from our side. We have a workaround (we route public ingress through QAnet gateways for now). Flagging it so the team can take a look when there is time, since it makes mainnet public URLs hard to provision today.
Tested 2026-06-13, v3 grid.