Mongodb connection timeout issues

Hi Garett Matsilele

I understand that you are experiencing connectivity issues to your MongoDB vCore account.

To proceed with a detailed investigation, could you please help us with the below information and test results?

Issue Behavior

Is the issue consistent or transient?

Please share the exact error message/exception you are seeing (including stack trace if available).

If possible, provide the Activity IDs or timestamps when the issue occurred.

Any application logs, diagnostic logs or connection trace logs captured during the failure would be very helpful.  

Please provide the results of Network & Connectivity Checks in Private Message

Kindly run the following command from one of the affected client machines and share the output:  

PowerShell
Test-NetConnection <server-hostname | ip-address> 10260  

Connection with Mongosh:
mongosh mongodb+srv://<user>:<password>@<accountName>.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retrywrites=false&maxIdleTimeMS=120000 

check if DNS resolves to expected IPs
$ nslookup -type=SRV _mongodb.tcp.<cluster-name>.<domain>

Once we receive these details, we will review the logs, validate the network reachability, and proceed with the next steps.

Hi Manoj,

Thank you for the response.

Please find the requested diagnostics below.

Issue Behavior:

• The issue is consistent and reproducible.

The application was previously working correctly before infrastructure/network updates.

After updates, the application can no longer establish MongoDB connectivity over the private endpoint.

Kudu DNS Test:

kudu_ssh_user@ffb429f27dbd:/$ nslookup fc-ce88da977caf-000.global.mongocluster.cosmos.azure.com

Server:         127.0.0.11
Address:        127.0.0.11#53

Non-authoritative answer:
fc-ce88da977caf-000.global.mongocluster.cosmos.azure.com canonical name =
fc-ce88da977caf-000.global.privatelink.mongocluster.cosmos.azure.com.

Name:
fc-ce88da977caf-000.global.privatelink.mongocluster.cosmos.azure.com

Address: 10.0.4.4

Kudu TCP Connectivity Test:

kudu_ssh_user@ffb429f27dbd:/$ tcpping fc-ce88da977caf-000.global.mongocluster.cosmos.azure.com 10260

seq 0: no response (timeout)
seq 1: no response (timeout)
seq 2: no response (timeout)
seq 3: no response (timeout)
seq 4: no response (timeout)
seq 5: no response (timeout)
seq 6: no response (timeout)
seq 7: no response (timeout)

mongosh Connectivity Test:

mongosh "mongodb+srv://<username>:<password>@xhihangule-api.mongocluster.cosmos.azure.com/?tls=true&authMechanism=SCRAM-SHA-256&retryWrites=false&maxIdleTimeMS=120000"

MongoServerSelectionError:
connect ETIMEDOUT 4.205.247.145:10260

PowerShell Test-NetConnection:

PS C:\Users\garet> Test-NetConnection fc-ce88da977caf-000.global.mongocluster.cosmos.azure.com -Port 10260

WARNING: TCP connect to (4.205.247.145 : 10260) failed

ComputerName           :
fc-ce88da977caf-000.global.mongocluster.cosmos.azure.com

RemoteAddress          : 4.205.247.145
RemotePort             : 10260
PingSucceeded          : True
TcpTestSucceeded       : False

SRV DNS Lookup:

nslookup -type=SRV _mongodb._tcp.xhihangule-api.mongocluster.cosmos.azure.com

Non-authoritative answer:

_mongodb._tcp.xhihangule-api.mongocluster.cosmos.azure.com
SRV service location:

priority       = 0
weight         = 0
port           = 10260
svr hostname   =
fc-ce88da977caf-000.mongocluster.cosmos.azure.com

Additional Notes:

Private endpoint status is Approved.

DNS resolves correctly to the private IP (10.0.4.4) inside the App Service Kudu console.

App Service is integrated with the VNet.

Private DNS zone integration is configured.

Dedicated subnet for private endpoints has been created.

Connectivity issue appears specifically related to TCP reachability on port 10260.

Please let me know if there are additional diagnostics or backend checks that can be performed.

Hi Garett Matsilele

I kindly request you to please share the details requested in the private message for further investigation.

Hi Manoj

I sent the requested details.