Hi RS team, we’ve started seeing timeouts when sen...
# support
i
Hi RS team, we’ve started seeing timeouts when sending events to rudderstack in the last 1-2 hours
q
Are you seeing it with any specific source or all sources?
i
We’re only seeing this from Google Cloud, using the node source Our browser sources are not timing out. Example IP’s which are timing out: ETIMEDOUT 52.86.157.16:443 ETIMEDOUT 23.22.135.239:443
q
can you share the full log for these timeouts?
i
Lot’s of [Rudder] error: Response error code: ETIMEDOUT [Rudder] error: Response error code: ETIMEDOUT [Rudder] error: Response error code: ETIMEDOUT
q
which version of node SDK you are using?
i
“rudder-sdk-js”: “^2.33.1"
This was working fine until 5.30 BST, and since then all requests are timing out
q
issue is with node sdk, right? version you shared is for JS SDK
i
Apologies “@rudderstack/rudder-sdk-node”: “^2.0.2",
Any issues you can see on your side @quiet-wolf-72320? I just found this GCP networking issue, but it only mentions azure. Are you using Azure? https://status.cloud.google.com/incidents/sZVuKPuYgMQiB7AzmAnL
h
Hi @incalculable-winter-14072, Can you provide the data plane url you are using?
i
👍, dm’d you
Ok got a workaround - pointed the node client at our GCP load balancer proxy, rather than XXX.dataplane.rudderstack.com directly. Events are flowing again without timeouts. This makes me think this is the same issue as that ongoing azure google cloud networking issue, and it’s wider spread than just Azure. So probably nothing for your team to resolve.
🙌 1
h
Thank you.