New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
OVH Virginia DC test IP
147.135.1.31
Getting about 82 ms (!!), testing from a server in Chicago using InterNAP.
Traceroute
1 ix-xe-0-0-0-1-0.tcore1.CT8-Chicago.as6453.net (63.243.129.65) 0.564 ms 0.705 ms 0.705 ms
2 ae7.edge3.chicago3.level3.net (4.68.110.193) 0.540 ms 0.542 ms 0.542 ms
3 ae-1-3507.ear4.Chicago2.Level3.net (4.69.142.105) 16.452 ms 16.769 ms 17.021 ms
4 chi-1-a9.il.us (198.27.73.66) 60.966 ms 60.959 ms 60.948 ms
5 be100-1316.ash-5-a9.va.us (198.27.73.87) 81.289 ms 81.172 ms 81.269 ms
6 seabon.ash-1-6k.va.us (178.32.135.211) 81.927 ms 81.928 ms 81.926 ms
7 * * *
8 * * *
9 * * *
10 ns100005.ip-147-135-1.us (147.135.1.31) 81.812 ms 81.762 ms 81.755 ms
Maybe it is just my server, so please post your own traceroutes.
Comments
Well Latency is relative where you ping from, so I dont get why 82ms is so worse/special.
Please read before you post.
I still dont know if 82ms is bad or not, I have nothing in mind to compare it with.
Still relative for me.
That is from my home connection in Mid Michigan.
Steadfast CHI to OVH VA is only 25ms.
Still relative for me.
Normally it should only be between 15 and 30 ms to a server in that area. Testing a Linode IP in New York gives me 19 ms.
nsk ttk
Трассировка маршрута к ns100005.ip-147-135-1.us [147.135.1.31]
с максимальным числом прыжков 30:
kmr our mini dc
Not very good. From BHS.
Strange. BHS and the new DC should be connected directly via their own fiber.
Its always the same, when someone opens a new POP or DC, the routing is shit.
Does not matter if OVH or Online.net
lol I live in Virginia and really close and I'm getting 26ms, with Leaseweb I get around 10-12ms.
For me the route is going from VA...to NJ..back to VA.
Much better now.
Hostigation NC
Host Loss% Snt Last Avg Best Wrst StDev 1. 206.253.166.12 0.0% 74 0.1 0.0 0.0 0.1 0.0 2. 249-241-23-66.solidspace.com 0.0% 74 4.9 0.8 0.5 4.9 0.7 3. 33-255-23-66.solidspace.com 0.0% 74 0.3 0.8 0.3 11.8 1.7 4. 4.7.56.9 0.0% 74 3.3 3.7 3.1 25.7 2.7 5. ae-1-3501.ear3.NewYork1.Level3.n 98.6% 74 49635 49635 49635 49635 0.0 6. be100-104.nwk-1-a9.nj.us 0.0% 74 17.7 17.7 17.5 18.8 0.2 7. be100-1039.ash-5-a9.va.us 0.0% 74 22.7 23.1 22.7 34.2 1.4 8. seabon.ash-1-6k.va.us 0.0% 74 23.6 23.8 23.4 38.6 1.8 9. ??? 10. ??? 11. ??? 12. ns100005.ip-147-135-1.us 0.0% 73 23.5 23.5 23.4 27.2 0.5Hostigation LA
Host Loss% Snt Last Avg Best Wrst StDev 1. e5la20.hostigation.com 0.0% 74 0.1 0.1 0.1 0.1 0.0 2. 38.142.35.33 0.0% 74 0.9 1.3 0.8 21.0 2.3 3. te0-0-2-3.agr12.lax04.atlas.cogentco.com 0.0% 74 1.0 1.4 0.8 23.8 2.7 4. te0-9-0-30.ccr41.lax04.atlas.cogentco.com 0.0% 74 1.0 1.2 0.8 17.6 1.9 5. be2965.ccr22.lax01.atlas.cogentco.com 0.0% 74 2.2 1.4 1.0 8.1 0.9 6. be2932.ccr22.phx02.atlas.cogentco.com 0.0% 74 12.7 12.7 12.2 18.3 1.0 7. be2930.ccr21.elp01.atlas.cogentco.com 0.0% 74 20.5 20.5 20.2 23.9 0.4 8. be3046.ccr21.den01.atlas.cogentco.com 0.0% 74 33.4 33.5 33.2 34.0 0.2 9. be3035.ccr21.mci01.atlas.cogentco.com 0.0% 74 44.9 45.1 44.8 46.3 0.2 10. be2831.ccr41.ord01.atlas.cogentco.com 0.0% 73 56.8 57.1 56.6 61.9 0.8 11. be2765.ccr41.ord03.atlas.cogentco.com 0.0% 73 57.0 57.2 56.7 64.3 1.1 12. be100-102.chi-1-a9.il.us 0.0% 73 57.0 57.1 56.9 58.1 0.2 13. be100-1316.ash-5-a9.va.us 0.0% 73 75.5 75.5 75.4 76.8 0.2 14. seabon.ash-1-6k.va.us 0.0% 73 76.1 76.6 76.1 93.5 2.2 15. ??? 16. ??? 17. ??? 18. ns100005.ip-147-135-1.us 0.0% 73 69.5 69.8 69.5 87.5 2.1One of my anycast hubs in Detroit, MI
Host Loss% Snt Last Avg Best Wrst StDev 1. vlan600.sfldmi-1.us.as62588.net 0.0% 93 0.4 0.4 0.3 3.4 0.3 2. te0-5.edge1.sfldmi-1.us.as62588.net 0.0% 93 0.5 0.5 0.3 1.8 0.2 3. te0-6-1-5.rcr21.dtw04.atlas.cogentco.com 0.0% 93 1.2 1.1 0.9 2.3 0.2 4. be2103.ccr42.ord01.atlas.cogentco.com 0.0% 93 8.3 8.3 7.9 9.6 0.3 5. be2766.ccr41.ord03.atlas.cogentco.com 0.0% 93 8.3 8.4 8.0 9.3 0.2 6. be100-102.chi-1-a9.il.us 0.0% 93 20.5 20.2 19.9 20.6 0.2 7. be100-1316.ash-5-a9.va.us 0.0% 92 20.1 20.1 19.9 20.9 0.2 8. seabon.ash-1-6k.va.us 0.0% 92 20.9 20.8 20.6 21.9 0.1 9. ??? 10. ??? 11. ??? 12. ns100005.ip-147-135-1.us 0.0% 92 20.8 20.7 20.4 21.0 0.1Still needs some work for sure.
113ms from Peru, not bad.
I'm getting 22ms from Chicago.
Hmmm you sell out of Detroit? Looking to throw up a VPN and I am in Michigan.
interesting put the ip through https://tools.keycdn.com/traceroute
I can hit Washington, DC at around 20ms. That IP averaging 65ms
Rockville Centre, NY 17ms
Fremont, CA 97ms
180ms AVG from Brazil
91ms AVG Parma, Northern Italy
I'm actually seeing good ping times from all over the US (and from BHS, too). I guess they're shaking the bugs out already.
Well, they were already in the region, I would hope.
Maybe. But I lived through the BHS fiber cuts and all I got was this t-shirt.
I want a shirt,
Happy to see them not taking the online.net route and just backhauling through BHS.
online.net doesn't do that if you ask their staff
lol
The route from my Leaseweb Manassas, VA dedis are much better now (7ms) but from my home Manassas, VA Verizon FIOS connection it's still around 27-30ms and going to NJ back to VA.
Home to OVH VA:
Home to Leaseweb:
how about tagging the guy from ovh ?
We an also ask for a LET exclusive deal like the atoms with 1tb or the i7 920s
(Off topic :seems someone in the bus had the idea of stealing me this silly iPhone while I was posting )