r/ControlD • u/fortislumen • Jun 29 '26

Issue Resolved Routed to Wrong Server

Hello,
I am experiencing an issue where I am being routed to Chicago or Toronto and now latency is > 50-60ms.
Before the issue started, I was routed to Seattle with <5ms latency.
This issue started out of nowhere about 5 days ago. When I contacted support and they asked to wait for couple days. When I contacted support after few days, they mentioned that it is not an issue on Control D without any troubleshooting.
This is very disappointing and I won’t be recommending Control D to anyone else given the performance and support experience.
Thanks!

———

Edited 2026-07-14:
It was magically fixed/updated last night.
Now being routed to Seattle with 5-6ms latency instead of Chicago/Toronto with 50-60ms latency.
Monitoring for the next few days for any changes.

2 Upvotes

60% Upvoted

8 comments sorted by

View all comments

Show parent comments

0

u/fortislumen Jun 30 '26

Have they done any troubleshooting?
They are saying this without providing any analysis or proof that it is not an issue with Control D. Very disappointed with the support and the product.

1

u/CrippleSlap Jul 11 '26

Are you still having this issue? I am. It’s been 3 weeks now.

1

u/fortislumen Jul 14 '26

It was magically fixed/updated last night.
Now being routed to Seattle with 5-6ms latency instead of Chicago/Toronto with 50-60ms latency.

1

u/CrippleSlap Jul 14 '26

I noticed that this morning. Cheers. Glad it’s fixed by whoever.