Tracing route to host.colocrossing.com [206.217.142.165] over a maximum of 30 hops:
1 tracert 173.248.149.194
Tracing route to 173.248.149.194 over a maximum of 30 hops
1 tracert 69.31.134.194
Tracing route to host.colocrossing.com [69.31.134.194] over a maximum of 30 hops:
1 tracert 198.144.179.101
Tracing route to host.colocrossing.com [198.144.179.101] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 17 ms 10 ms 10 ms cab1-1.1scom.net [66.182.192.1] 3 17 ms 32 ms 15 ms DSL2-25.1scom.net [66.182.213.25] 4 58 ms 18 ms 19 ms ip65-47-204-181.z204-47-65.customer.algx.net [65 .47.204.181] 5 36 ms 24 ms 14 ms 206.111.5.138.ptr.us.xo.net [206.111.5.138] 6 36 ms 38 ms 39 ms xe-1-2-0.cr2.ord6.us.scnet.net [204.93.144.29] 7 39 ms 39 ms 39 ms ae4.ar5.ord6.us.scnet.net [204.93.204.65] 8 40 ms 59 ms 36 ms as36352.xe-2-0-2.ar5.ord6.us.scnet.net [50.31.15 1.170] 9 44 ms 37 ms 37 ms 10ge-1-3-2.fz146.cr2.chi.colocrossing.com [206.2 17.137.254] 10 37 ms 36 ms 35 ms host.colocrossing.com [205.234.152.250] 11 37 ms 37 ms 65 ms host.colocrossing.com [198.144.179.101]
Trace complete.
Now they say everything is running fine and there is nothing they can do. But why is it one day everything was working fine untill they fixed some errors and packet lost and now im pinging high to a server that is 20 miles from me and ping better to a server that is 200+ miles away from me?
Hard to tell since you only posted a single traceroute.
Distance and hop count affect latency. Distance is cable miles not as the bird flies, so can change moment by moment and is also affected by where and how your ISP and the remote server peers.
Given that latency through your ISP edge router is 10-15 ms another 20-30 to the remote host does not appear out of the ordinary.
·
·