Problem with the US server

Mar 23, 2010
1,872
1,696
I cannot connect - says "Connection Failed After 4 Retries"
says server is not responding when viewing game info
cannot add server to favorites - does absolutely nothing to my favs

I've messaged grazr on steam with no response, and I believe Snacks said something about a superban (banning for -1 time) from it. If ya know anything, please do tell.
 
Last edited:

drp

aa
Oct 25, 2007
2,273
2,628
a ban will not give you time out errors.

can you run a trace and ping and post the results here please?
 
Mar 23, 2010
1,872
1,696
Tracing route to 174.34.133.100.rdns.ubiquityservers.com [174.34.133.100]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 239 ms 395 ms 395 ms cpe-174-097-184-001.nc.res.rr.com [174.97.184.1]

3 330 ms 347 ms 208 ms ten13-0-0-239.rlghnca-rtr2.nc.rr.com [66.26.32.2
46]
4 350 ms 401 ms 143 ms ge-2-3-0.chrlncpop-rtr1.southeast.rr.com [24.93.
64.176]
5 103 ms 84 ms 38 ms ae-3-0.cr0.atl20.tbone.rr.com [66.109.6.82]
6 257 ms 707 ms 666 ms ae-0-0.pr0.atl20.tbone.rr.com [66.109.6.171]
7 36 ms 40 ms 57 ms xe-7-1-0.edge4.Atlanta2.Level3.net [4.59.12.29]

8 78 ms 350 ms 153 ms vlan52.csw2.Atlanta2.Level3.net [4.69.150.126]
9 676 ms 473 ms 734 ms ae-72-72.ebr2.Atlanta2.Level3.net [4.69.148.249]

10 616 ms 934 ms 823 ms ae-3-3.ebr2.Chicago1.Level3.net [4.69.132.73]
11 1201 ms 563 ms 716 ms ae-2-52.edge3.Chicago3.Level3.net [4.69.138.42]

12 797 ms 986 ms 733 ms MZIMA-NETWO.edge3.Chicago3.Level3.net [4.53.96.2
6]
13 1463 ms 1665 ms 1743 ms te0-0.cr1.dal1.us.packetexchange.net [69.174.120
.14]
14 1164 ms 897 ms 1599 ms edge1.dal.ubiquityservers.com [72.37.178.34]
15 829 ms 682 ms 636 ms 174.34.133.100.rdns.ubiquityservers.com [174.34.
133.100]

Trace complete.

Ping statistics for 174.133.0.100:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\THECOMP>ping 174.34.133.100

Pinging 174.34.133.100 with 32 bytes of data:
Reply from 174.34.133.100: bytes=32 time=466ms TTL=117
Reply from 174.34.133.100: bytes=32 time=309ms TTL=117
Reply from 174.34.133.100: bytes=32 time=482ms TTL=117
Reply from 174.34.133.100: bytes=32 time=220ms TTL=117

Ping statistics for 174.34.133.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 482ms, Average = 369ms

Ignore high pings, people were downloading.
 
Last edited:
Mar 23, 2010
1,872
1,696
nevermind, fixed. apparently turning off comp and leaving for 3 days fixed it.
 
Last edited: