The official WoW connection rant thread, 2k pings? Insane lag? Come in here!
The official WoW connection rant thread, 2k pings? Insane lag? Come in here!
|
|
Mar 16 2005, 05:58 PM
Return to original view | Post
#1
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
Anyone has a list of IP addresses of all the servers? I could set up some monitoring system .. and latency checks..
|
|
|
|
|
|
Mar 21 2005, 04:06 PM
Return to original view | Post
#2
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
I was getting about 1.5k ms latency yesterday on both the 219.95 and 219.94 even nowadays. The only solution is to get that elusive 218.210 range or IP.. i think it's 218.210 or 210.218.. can't remember the exact ones but it's not the 219.x series.
Anyhow your trace would not reach their network as they have probably filtered trace packets. |
|
|
Mar 24 2005, 09:41 AM
Return to original view | Post
#3
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
Sigh. Did you guys checked what IPs you were getting when you got those high latencies..?????
|
|
|
Mar 30 2005, 01:27 AM
Return to original view | Post
#4
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
The high jump in latency between hop 6 and 7 .. is probably due to high congestion
|
|
|
Apr 4 2005, 11:15 AM
Return to original view | Post
#5
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
QUOTE(Xeoalpha @ Apr 4 2005, 10:01 AM) The person I spoke did mention that it's only the 219 IP range having issues because, it's being filtered or blocked by AT&T. Xeo - I think the person you spoke to was referring to the filtering of *only* your trace route results and icmp ping packets. It isn't a total complete block of everything. I don't think AT&T implemented a total complete blocking from tmnet IP block. That is not likely the case. Filtering of icmp/trace route packets is quite common nowadays. |
|
|
Apr 5 2005, 10:41 AM
Return to original view | Post
#6
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
If you guys can do it, do a tcp ping port 3724 instead..
Here's a sample done from my office network... I know where i'll be playing my WoW tonight Reply from us.logon.worldofwarcraft.com:3724 time=219ms Reply from us.logon.worldofwarcraft.com:3724 time=203ms Reply from us.logon.worldofwarcraft.com:3724 time=219ms Reply from us.logon.worldofwarcraft.com:3724 time=203ms Reply from us.logon.worldofwarcraft.com:3724 time=219ms Reply from us.logon.worldofwarcraft.com:3724 time=203ms Reply from us.logon.worldofwarcraft.com:3724 time=218ms Reply from us.logon.worldofwarcraft.com:3724 time=204ms |
|
|
|
|
|
Apr 5 2005, 11:08 AM
Return to original view | Post
#7
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
|
|
|
Apr 5 2005, 11:18 AM
Return to original view | Post
#8
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
O_o
WoW automatically uses that port for logon and server.. That's the only port that is responsive to the ping and not the other ports. I didn't change anything... I was just pinging that port to see what's the response time like from my office network. It's more accurate than doing a trace route that gets stuck somewhere in the middle This post has been edited by tarpaucase: Apr 5 2005, 11:22 AM |
|
|
Apr 5 2005, 12:34 PM
Return to original view | Post
#9
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
There's no solution to you guys having the 219.95 IP range at this moment.
I haven't given up playing at home because I can get 219.94 IP range and get about 600-700ms latency (playable in my sense It's most likely the problem you're facing is attributed to TMNet 'cock-up' but it is also very possible that AT&T leased two types of services to Tmnet as their upstream. One could be a 'gold class' service recognising the 60.x ip range and 219.94.. while the other is a 'cheap skate' service. 219.95.x.x -- these different class of service is to give priority to people paying more money. Seeing as both range of IPs go through the same gateway, this is a possible case.. (it couldn't be a router cpu load problem, that will result in high latency everywhere)...unless of course one of the IP range goes through some hidden routes maybe 2 round trip around the globe before coming back.. just some wild theory... This post has been edited by tarpaucase: Apr 5 2005, 12:36 PM |
|
|
Apr 5 2005, 05:47 PM
Return to original view | Post
#10
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
QUOTE(wildside @ Apr 5 2005, 03:18 PM) I'd believe it if he actually gave you a specific date on which the problem would be fixed... INSTEAD OF giving you the usual 'I don't know' answer. Usually..I'd believe it if he gave you a plausible reason why it's taking so long to fix... INSTEAD OF giving you the usual 'Technical problem our personnel looking into it' answer I'd believe it if he gave you his name... INSTEAD OF trying to avoid answering. I'd believe it if he calls you at some point to update you on the status... INSTEAD OF you never hearing from him again. 1. These kind of problem that transcends our borders are hard to fix. They can't give you any date because, if they can't meet the deadline they given out it would only amount to disappointment. It's very hard to give a 'date' when it would be fixed specifically. The problem could be hardware related, vendor would need to know the date of delivery, what about factory.. do they have stock? if it's undersea cable, which ship would carry them to sea to fix it.. when does the ship dock?.. it's *very* hard to give exact dates as you can see 2. It's hard to give you a reason because these are call center people, they themselves are usually not the technical person but they are there to lodge your complaints and reports. No IT company would hire superior technically knowledge-able people to man the call center. No professional IT guy would want to do that also 3. There's no reason for him to give you his name, but he should have anyhow. It doesn't hurt him anyhow, maybe you scared him? Why don't you guys try to get a 'trouble ticket number' from them? they usually have some form of troubleshooting follow up to do via a ticketing system... i hope.. and torrent is not a good way to estimate speed, and broadband.. well, you're not guaranteed a speed you subscribed to anyways This post has been edited by tarpaucase: Apr 5 2005, 05:49 PM |
|
|
Apr 5 2005, 10:31 PM
Return to original view | Post
#11
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
QUOTE(wildside @ Apr 5 2005, 06:41 PM) Ah see... this is where we don't agree... If they were a focused organisation, they should have had plenty of time to have analysed the problem, set a deadline to fix it and commit to it. Not having a deadline is just asking for procrastination to creep in. Well, they(tmnet/AT&T) could be a focused organisation but they too rely on other parties to help them do such thing.. Following on my first answer above, I place a very high emphasis on the need for the backroom technical staff to be constantly in contact with the front-line staff to keep them abreast of developments. It's called professionalism and customer focus. Otherwise, why have a support staff manning 1-300-88-9515 anyway? Again, it's customer focus to show that they are approachable and taking a personal interest in your problem. Not willing to do so even when asked tells me they have something to hide. And yes, you're right in the sense that the technical staff should constantly be in contact with the front-line staff but there's some things that the front line staff can't explain that well to the customer, no matter how well the technical staff try to explain it. Otherwise if the front line is so good he/she might as well go to the back end and be a technical staff too right? Customer support staff is there to entertain you while the back-end people do their job Anyway, good latency doesn't improve my gameplay.. as shown here ![]() This post has been edited by tarpaucase: Apr 5 2005, 10:32 PM |
|
|
Apr 5 2005, 11:17 PM
Return to original view | Post
#12
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
I don't think you guys will get any response from tmnet - with us just minority WoW gamers pestering them, i doubt they even care...
Did you guys get a trouble ticket number even??? but yeah. they should at least explain .. on a website that their international site is having issues.. or something somewhat.. unless it's something that could impact their services - what if traffic shaping is turned off for all customers.. and because of this all 219.95 ip are congested to the max...? Oh well best course of action here I think now is for you guys to complain collectively - get a trouble ticket and pour in all the information and repeatedly call them and ask them to refer to this particular problem or speak to their supervisor and all that... magic word : trouble ticket (i was screwing around when i meant my gameplay sucked even with the latency.. it was a joke.. sorta.. but..oh nvm) |
|
|
Apr 6 2005, 10:53 AM
Return to original view | Post
#13
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
|
|
|
|
|
|
Apr 7 2005, 02:23 PM
Return to original view | Post
#14
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
I believe it's a new problem - and it just happens to make the old problem even worse, that's all.
I'm betting it's a submarine cable fault, in which will take days to resolve, if we're lucky... re-routing would not be simple as that. Don't hold your breath guys.. |
|
|
Apr 7 2005, 05:17 PM
Return to original view | Post
#15
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
I'm almost sure of one thing though.. they aren't using all their backup.
Myloca.. part of telekom, has an entirely different gateway altogether I believe.. if you go to http://mips.myloca.com/trace/ and do a trace to us.logon.worldofwarcraft.com.. it uses UUNet(alterNET) as its main link to the US(WoW US servers specifically - they might have other links) and it gets about 200ms to at&t before getting filtered off They could, I believe, do quite a bit of work to reroute some traffic through that gateway.. but somehow they aren't doing it(too much red tape or bureaucracy??) .. probably because myloca customers pay a heck lot more than us peanuts stimyx customers This post has been edited by tarpaucase: Apr 7 2005, 05:20 PM |
|
|
Apr 8 2005, 09:38 AM
Return to original view | Post
#16
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
Singtel says it will be fixed today.
My other sources tells me it will be fixed on Saturday 0100 UTC 10 gp I say its next week.. |
|
|
Apr 8 2005, 12:39 PM
Return to original view | Post
#17
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
you guys don't even have to launch streamyx to test.. just do a simple ping to www.yahoo.com
if you get 200-300ms.. it means it's *probably* been fixed. it's a pretty okay indicator I would say.. At the moment you should all be getting close to 3000ms to good ol' yahoo.com yahooooooo!!! edit : i'm doing this to test general streamyx internet connectivity.. not just to wow.. This post has been edited by tarpaucase: Apr 8 2005, 12:40 PM |
|
|
Apr 9 2005, 08:24 AM
Return to original view | Post
#18
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
Well from my end.. Timenet.. I am getting about 250ms to WoW now
From home, I am getting around 250ms to yahoo... but there's some pretty severe packet drop.. i think they are still working on it... |
|
|
Apr 9 2005, 04:31 PM
Return to original view | Post
#19
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
Wasn't it supposed to have been fixed this morning? O_o
0100UTC is supposed to be 8-9am today isn't it ? Office pc can play.. but it takes me like 25 minutes to get out of IF... stupid old pc!!!!.... (if not mistaken, alternet/uunet is going through apcn2 also... i *think*) It's probably been fixed but there's some routing issues on the ISP side that needs to be fixed as well probably... static diversion of traffic and all that.. but since it's the weeeeekeeeeendd...... This post has been edited by tarpaucase: Apr 9 2005, 04:32 PM |
|
|
Apr 9 2005, 10:51 PM
Return to original view | Post
#20
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
3,469 posts Joined: Jan 2003 From: ...Frying Pan... |
QUOTE(eikan @ Apr 9 2005, 10:18 PM) QUOTE(TaufanX @ Apr 9 2005, 10:20 PM) AIYOH.. LOL this made me laugh until stomach ache... LOLOLOLOLOLOL...first sign of WoW withdrawal madness syndrome You know what would help ? You guys need to get the tmnet network people to get hooked.. AHHH.. THEN they will care... in fact, you no need to complain, they sure fix it ASAP one |
| Change to: | 0.0391sec
0.74
7 queries
GZIP Disabled
Time is now: 29th November 2025 - 02:54 PM |