Have some bad routes to Chicago. They have 2 more weeks to get it fixed.
So have fun killing me.
C:\Users\adl>ping 216.52.148.113
Pinging 216.52.148.113 with 32 bytes of data:
Reply from 216.52.148.113: bytes=32 time=68ms TTL=115
Reply from 216.52.148.113: bytes=32 time=69ms TTL=115
Reply from 216.52.148.113: bytes=32 time=68ms TTL=115
Reply from 216.52.148.113: bytes=32 time=68ms TTL=115
Ping statistics for 216.52.148.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 69ms, Average = 68ms
Ping looks good.
Trace Route Looks bad and in game looks bad 96 ping on net graph
C:\Users\adl>tracert 216.52.148.113
Tracing route to c-216-52-148-113.managed-vds.internap-chicago.nfoservers.com [2
16.52.148.113]
over a maximum of 30 hops:
1 7 ms 7 ms 6 ms tn-67-237-218-1.dhcp.embarqhsd.net [67.237.218.1
]
2 7 ms 7 ms 7 ms tn-76-5-159-241.sta.embarqhsd.net [76.5.159.241]
3 16 ms 17 ms 17 ms host.lightcore.net [208.110.248.245]
4 17 ms 17 ms 18 ms bb-rcmtncxa-jx9-02-ae0.core.centurytel.net [208.
110.248.66]
5 35 ms 35 ms 35 ms bb-wnpkflxe-jx9-01-xe-1-1-0.core.centurytel.net
[208.110.248.158]
6 36 ms 35 ms 35 ms bb-wnpkflxe-jx9-02-ae0.core.centurytel.net [208.
110.248.94]
7 41 ms 41 ms 41 ms bb-miauflws-jx9-02-xe-1-1-0.core.centurytel.net
[208.110.248.193]
8 51 ms 40 ms 55 ms bb-miauflws-jx9-01-ae0.core.centurytel.net [208.
110.248.101]
9 41 ms 41 ms 41 ms cr1-nota-peer.mia004.internap.net [198.32.124.12
9]
10 93 ms 92 ms 93 ms chg003-mia004-1029-cr1.chg003.pnap.internap.net
[66.79.147.149]
11 69 ms 69 ms 69 ms chg-chg003-42-core1.chg.internap.net [66.79.150.
130]
12 223 ms 226 ms 239 ms border6.po2-bbnet2.chg.pnap.net [64.94.32.75]
13 69 ms 69 ms 69 ms c-216-52-148-113.managed-vds.internap-chicago.nf
oservers.com [216.52.148.113]
Trace complete.