R
Ryan
Guest
Yes, we care - Hybrid Latency issues
Ok it has come to our attention that some people are indeed having latency issues. What I need from you is to take the time to complete this list in order to ensure that we get the proper data to troubleshoot this.
It looks at this time to be a routing issue of sorts. Right now it would appear that all of our clients coming in through Verio, one of our upstream providers is having an issue.
I would like, at this time you guys to do this checklist for me:
This should give us the information we need to troubleshoot the problem.
We only ask that you reply with the needed information in this format:
My Information:
IP:
1.1.1.1
Traceroute:
* 4 ms
* 4 ms
* 4 ms
Ping:
U:\>ping -l 8 login.uogamers.net
Pinging login.uogamers.net [67.15.20.52] with 8 bytes of data:
Reply from 67.15.20.52: bytes=8 time=37ms TTL=113
Reply from 67.15.20.52: bytes=8 time=37ms TTL=113
Reply from 67.15.20.52: bytes=8 time=37ms TTL=113
Reply from 67.15.20.52: bytes=8 time=36ms TTL=113
Ping statistics for 67.15.20.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 37ms, Average = 36ms
Thanks for your help, we hope to have this resolved today!
Ok it has come to our attention that some people are indeed having latency issues. What I need from you is to take the time to complete this list in order to ensure that we get the proper data to troubleshoot this.
It looks at this time to be a routing issue of sorts. Right now it would appear that all of our clients coming in through Verio, one of our upstream providers is having an issue.
I would like, at this time you guys to do this checklist for me:
- Your IP Address
- An inbound traceroute from you to our server in windows (start->run->cmd c:\> tracert login.uogamers.net )
- A diagnostic ping from you to our server ( start->run->cmd, c:\> pathping -n login.uogamers.net ) For WINDOWS XP (This coudl take up to 10 minutes to run but is necessary for us to fix the problem), or ping -l 8 -n 10 login.uogamers.net
This should give us the information we need to troubleshoot the problem.
We only ask that you reply with the needed information in this format:
My Information:
IP:
1.1.1.1
Traceroute:
* 4 ms
* 4 ms
* 4 ms
Ping:
U:\>ping -l 8 login.uogamers.net
Pinging login.uogamers.net [67.15.20.52] with 8 bytes of data:
Reply from 67.15.20.52: bytes=8 time=37ms TTL=113
Reply from 67.15.20.52: bytes=8 time=37ms TTL=113
Reply from 67.15.20.52: bytes=8 time=37ms TTL=113
Reply from 67.15.20.52: bytes=8 time=36ms TTL=113
Ping statistics for 67.15.20.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 37ms, Average = 36ms
Thanks for your help, we hope to have this resolved today!