Hey there! We've found the following might help you get unblocked faster:

• 🧵 Connecting to service via internal network doesn't work

• 🧵 Internal network connection issue - App cannot reach PostgreSQL via internal address

• 🧵 Critical: Internal Network Issue?

• 🧵 Inconsistent latency on Metal (service to service communication over the private network)

If you find the answer from one of these, please let us know by solving the thread!

We're experiencing the same issue.

If set to public, it works, but nothing can go through the private network.

All deployments with only IPv6 are working, but new ones with both IPv6 and IPv4 cannot be used with the private network.

Thanks for jumping in and confirming you're seeing the same issue. For better tracking and to make sure we can help you directly, could you please open a new thread with your specific details? This helps us keep things organized and provide more targeted support.

Can we get a bit more info on what you mean by "The internal network doesn't work"? Do you have any errors or logs for this?

Sorry,My internal services can’t reach each other and are timing out. However, when I switch the communication mode from internal to public, everything works normally again.

Hey, we rolled out a fix for this, please try switching back to the private network.

Thank you. It worked yesterday, but today the issue re-occurred between my services. [cause]: [AggregateError: ] { code: 'ETIMEDOUT' }.

I'm seeing alot of deployments so I'm not able to track down where your service is failing efficiently, can you please link me directly to the failure so we can investigate further?