dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
685
sam0478
join:2008-03-19
Oxford, MS

sam0478

Member

MetroCast Service in Mississippi to WoW servers

My ISP (Vista3Media) in Mississippi was recently acquired by MetroCast.

I am an avid World of Warcraft player on the Deathwing server and I have recently noticed a severe degradation in performance to the Deathwing server with random disconnects and periods of extremely high latency. I am wondering a few things...

1) I know it's a long shot, but have any other WoW players in the Northern MS area with MetroCast happened to notice this performance drop to Deathwing or your respective server?

2) Who should I contact at MetroCast about this problem and will it solve anything? I'd prefer to talk to someone with the knowledge and ability to find the problem and get the ball rolling to fix it.. not just some generic tech support person who wants me to clear my IE cache/cookies.

3) Does the following traceroute/ping report help at all? Any ideas? The request timeouts after the last known hop of the trace are expected, and I'm pretty sure the request timeouts of the ping are expected as well. This probably won't reveal the problem at the moment, because (un)fortunately the problem disappears after primetime. I think there may just be too many people in my area (a college town) flooding the pipes and causing me problems. Most other people I talk to on the server have absolutely no connection problems from their locations, so I doubt it is the server itself. I'll try to remember to get a traceroute while the problem is occurring tomorrow night.

> tracert 206.17.111.74

Tracing route to 206.17.111.74 over a maximum of 30 hops

1 26 ms 22 ms 20 ms 10.200.24.1
2 23 ms 23 ms 33 ms 10.70.1.1
3 * 46 ms 37 ms telapexnode-042-a.telapex.com [66.175.143.42]
4 33 ms 39 ms 33 ms 65.89.119.5
5 37 ms 23 ms 29 ms so-7-0-2.edge1.Atlanta2.Level3.net [4.68.63.29]

6 45 ms 38 ms 42 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
7 43 ms 41 ms 52 ms 192.205.34.57
8 62 ms 74 ms 71 ms tbr2.attga.ip.att.net [12.122.96.70]
9 68 ms 60 ms 59 ms cr1.attga.ip.att.net [12.122.17.113]
10 66 ms 75 ms 65 ms cr2.wswdc.ip.att.net [12.122.1.174]
11 77 ms 82 ms 69 ms tbr2.wswdc.ip.att.net [12.122.16.70]
12 77 ms 59 ms 57 ms tbr2.n54ny.ip.att.net [12.122.10.53]
13 72 ms 77 ms 61 ms tbr1.cb1ma.ip.att.net [12.122.10.21]
14 68 ms 68 ms 66 ms 12.127.5.109
15 76 ms 68 ms 68 ms 12-122-254-14.attens.net [12.122.254.14]
16 71 ms 84 ms 75 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.13
0.0.174]
17 * * * Request timed out.
18 * * * Request timed out.

> ping 206.17.111.83

Pinging 206.17.111.83 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

Thanks.
rkrenicki
join:2002-04-10
Quaker Hill, CT

rkrenicki

Member

as far as I know, there have been no engineering changes to the Mississippi system at this time. Nothing should have changed.

The World of Warcraft systems have always rejected ICMP at their edge router, so it is perfectly normal to not be able to ping your (or any of their) servers, or even trace past their AT&T peering point.

A quick google search shows that your server is Central time, and from your trace, it appears to be located in/near Boston. Perhaps there is an issue in this datacenter, or some congestion between you and there.

odog
Minister of internet doohickies
Premium Member
join:2001-08-05
Atlanta, GA
Nokia BGW320-505

odog to sam0478

Premium Member

to sam0478
We are definitely going to be doing work in MS. I'm scheduled to go down and work for probably at least a week helping the local guys out. It might take a little time, but we are definitely committed to make it work up to and past the customers expectations.