UOGamers Community

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

  • To obtain new Razor updates, please reinstall Razor from our new website.

Unreliable Connection

Status
Not open for further replies.

Paracelsus

Sorceror
Unreliable Connection

I got unreliable connection recently. There were a few timeouts and then my connection was dead.

My tracert is like this:
Tracing route to login.uogamers.com [173.192.237.124]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 24 ms 21 ms 21 ms (intentionally removed)
3 23 ms 21 ms 23 ms n219076125194.netvigator.com [219.76.125.194]
4 20 ms 21 ms 19 ms pcd507254.netvigator.com [218.102.39.254]
5 28 ms 22 ms 22 ms tenge2-4.br02.hkg04.pccwbtn.net [63.218.252.173]
6 181 ms 179 ms 177 ms comcast.Tenge13-3.br02.sjo01.pccwbtn.net [63.218.179.26]
7 181 ms 175 ms 177 ms pos-2-4-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.87.9]
8 182 ms 179 ms 179 ms pos-0-9-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.85.186]
9 242 ms 241 ms 241 ms pos-0-12-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.86.118]
10 242 ms 240 ms 239 ms pos-0-11-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.222]
11 253 ms 247 ms 249 ms pos-0-13-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.234]

12 248 ms 250 ms 248 ms pos-0-2-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.70]
13 248 ms 243 ms 241 ms softlayer-pe01.ashburn.va.ibone.comcast.net [75.149.228.94]
14 247 ms 243 ms 243 ms po4.bbr01.sr01.wdc01.networklayer.com [173.192.18.197]

15 249 ms 251 ms 254 ms po1.cer02.sr01.wdc01.networklayer.com [173.192.18.189]
16 249 ms 255 ms 247 ms 208.43.118.151-static.reverse.networklayer.com [208.43.118.151]
17 247 ms 245 ms 243 ms 173.192.237.124-static.reverse.softlayer.com [173.192.237.124]

Trace complete.

I kept pinging on several IPs and found that whenever I got timeout to hybrid, I got timeout to 173.192.18.197.

Ping 68.86.86.70
Reply from 68.86.86.70: bytes=32 time=251ms TTL=246
Reply from 68.86.86.70: bytes=32 time=248ms TTL=246
Reply from 68.86.86.70: bytes=32 time=249ms TTL=246
Reply from 68.86.86.70: bytes=32 time=248ms TTL=246
Reply from 68.86.86.70: bytes=32 time=249ms TTL=246
Reply from 68.86.86.70: bytes=32 time=248ms TTL=246
Reply from 68.86.86.70: bytes=32 time=249ms TTL=246
Reply from 68.86.86.70: bytes=32 time=247ms TTL=246

Ping 173.192.18.197
Reply from 173.192.18.197: bytes=32 time=244ms TTL=244
Reply from 173.192.18.197: bytes=32 time=246ms TTL=244
Reply from 173.192.18.197: bytes=32 time=246ms TTL=244
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.192.18.197: bytes=32 time=248ms TTL=244
Reply from 173.192.18.197: bytes=32 time=248ms TTL=244
Reply from 173.192.18.197: bytes=32 time=312ms TTL=244

Ping 173.192.237.124
Reply from 173.192.237.124: bytes=32 time=245ms TTL=118
Reply from 173.192.237.124: bytes=32 time=246ms TTL=118
Reply from 173.192.237.124: bytes=32 time=247ms TTL=118
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.192.237.124: bytes=32 time=248ms TTL=118
Reply from 173.192.237.124: bytes=32 time=249ms TTL=118
Reply from 173.192.237.124: bytes=32 time=250ms TTL=118

Is there any cure?
 
Status
Not open for further replies.
Top