|
|
Rank: Member
Groups: Member
Joined: 2/22/2010
Posts: 15
Points: 45
Location: Davao City
|
oops, sorry sa first tracert ko, sa kapitbahay naming wireless connection. Not sure kung ano ISP nila. parang PLDT.
This is one is mine now, winired ko na para sigurado then turn off ko na wireless ko. Mine is BayanDSL 1.5mbps.
1 12 ms 12 ms 12 ms 210.4.58.2
2 35 ms 34 ms 34 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
3 35 ms 34 ms 36 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
4 33 ms 34 ms 33 ms 202.78.119.1
5 386 ms 388 ms 382 ms 12.119.139.13
6 429 ms 432 ms 436 ms cr2.sffca.ip.att.net [12.122.136.66]
7 432 ms 428 ms 433 ms cr2.la2ca.ip.att.net [12.122.31.133]
8 430 ms 431 ms 428 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 420 ms 428 ms 424 ms gar23.dlstx.ip.att.net [12.122.138.153]
10 423 ms 434 ms 428 ms 12-122-254-154.attens.net [12.122.254.154]
11 425 ms 426 ms 432 ms mdf002c7613r0001-tge-12-1.dal1.attens.net [63.24.193.150]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * *
Just posting baka makatulong sa info ... Too busy para makapagreklamo pa. Baka pag-uwi ko nalang or Friday. hehe ..
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
gumising ako knina 4am para mag tracert kasi tuwing 4am lang tlga 200+ms, ok naman siya pag hindi peak hours saten.
Tracing route to 12.129.233.63 over a maximum of 16 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 10 ms 121.96.128.1.BTI.NET.PH [121.96.128.1]
3 10 ms 10 ms 10 ms 121.96.0.138.bti.net.ph [121.96.0.138]
4 10 ms 11 ms 10 ms 121.96.0.138.bti.net.ph [121.96.0.138]
5 12 ms 11 ms 11 ms 121.96.0.173.BTI.NET.PH [121.96.0.173]
6 11 ms 11 ms 12 ms 121.96.0.125.BTI.NET.PH [121.96.0.125]
7 11 ms 11 ms 11 ms 202.78.96.222
8 11 ms 11 ms 12 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
9 12 ms 30 ms 27 ms 202.78.119.1
10 171 ms 170 ms 170 ms 12.119.139.13
11 183 ms 183 ms 183 ms cr1.sffca.ip.att.net [12.122.137.66]
12 182 ms 183 ms 183 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 182 ms 182 ms 182 ms cr83.la2ca.ip.att.net [12.123.30.109]
14 181 ms 181 ms 181 ms gar5.la2ca.ip.att.net [12.122.128.25]
15 183 ms 210 ms 187 ms 12.122.255.74
16 182 ms 183 ms 182 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
Trace complete.
Hay sana maayos na para hindi na kelangan pumunta ng shop para lang mag raid/daily random heroics.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/20/2010
Posts: 75
Points: 225
|
That's more like the old tracerts of last week (before Tue.) and beyond. Pero it didn't matter what time of the day it was.
Common factor of the problem is still that particular connection between hop 4 and 5.
|
|
Rank: Newbie
Groups: Member
Joined: 2/24/2010
Posts: 6
Points: 18
Location: Quezon City
|
Another WoW player here. My problems started at the same date as others, and all the bayantel subscribers I know in WoW is experiencing the same problem. I did this tracert on friday:
Tracing route to 12-129-225-2.attens.net [12.129.225.2]
over a maximum of 30 hops:
1 8 ms 10 ms 7 ms 121.96.128.1.BTI.NET.PH [121.96.128.1]
2 187 ms 8 ms 268 ms 121.96.0.138.bti.net.ph [121.96.0.138]
3 60 ms 12 ms 235 ms 121.96.0.138.bti.net.ph [121.96.0.138]
4 9 ms 11 ms 9 ms 121.96.0.173.bti.net.ph [121.96.0.173]
5 10 ms 11 ms 9 ms 121.96.0.133.bti.net.ph [121.96.0.133]
6 10 ms 10 ms 11 ms 202.78.96.222
7 31 ms 95 ms 9 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
8 93 ms 207 ms 210 ms 202.78.119.1
9 * 333 ms 340 ms 12.119.139.13
10 351 ms 348 ms * cr1.sffca.ip.att.net [12.122.137.66]
11 350 ms 346 ms 346 ms cr1.la2ca.ip.att.net [12.122.3.122]
12 344 ms 347 ms 347 ms cr83.la2ca.ip.att.net [12.123.30.109]
13 346 ms 344 ms 346 ms gar5.la2ca.ip.att.net [12.122.128.25]
14 349 ms 344 ms 345 ms 12.122.255.74
15 345 ms 345 ms 345 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
And I repeated the tracert today:
Tracing route to 12-129-225-2.attens.net [12.129.225.2]
over a maximum of 30 hops:
1 8 ms 8 ms 7 ms 121.96.128.1.BTI.NET.PH [121.96.128.1]
2 8 ms 9 ms 7 ms 121.96.0.138.bti.net.ph [121.96.0.138]
3 9 ms 7 ms 8 ms 121.96.0.138.bti.net.ph [121.96.0.138]
4 9 ms 9 ms 10 ms 121.96.0.114.bti.net.ph [121.96.0.114]
5 9 ms 9 ms 8 ms 202.78.96.222
6 9 ms 10 ms 11 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
7 9 ms 11 ms 8 ms 202.78.119.1
8 322 ms 324 ms 337 ms 12.119.139.13
9 368 ms 368 ms 367 ms cr1.sffca.ip.att.net [12.122.137.66]
10 368 ms 369 ms 363 ms cr1.la2ca.ip.att.net [12.122.3.122]
11 337 ms 343 ms 349 ms cr83.la2ca.ip.att.net [12.123.30.109]
12 355 ms 358 ms 357 ms gar5.la2ca.ip.att.net [12.122.128.25]
13 371 ms 368 ms * 12.122.255.74
14 536 ms 423 ms 359 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2008
Posts: 42
Points: 126
Location: QC
|
It seems this thread was able to reach more Bayan subscribers who plays WoW who were recently had an unusual latency problem. I believe its a good thing to post such details here. But, as previously requested by Mikos, please include account numbers.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
still sucky latency even after the maintenance....
i can only do 5mans and sit around towns. sigh
guess no 10/25mans until bayan patches things up.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/6/2008
Posts: 46
Points: 138
Location: manila
|
WOW player here
acct # 32329943
if everythings fine at 4am = which is pretty much 12 noon? at the US (west coast) then the problem is probably within bayantel or their peering network
im also getting a lot of timeouts when trace routing
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
Sana may taga bayan na mag reply, hindi yung nanghuhula tayo.
Pero feeling ko sa bayan side ang prob, either sobrang congested na yung network na hindi na kaya
o talagang sobrang fail na ngayun ang bayantel sa sobrang daming subscribers.
last 2 weeks sobrang smooth mag laro. biglaan nalang.
sayang frost badges, lalo na sa raider, at ang galing ng timing kung kelan nasa lich king na
. guess hindi naman nila maiintindihan yun
kaya wala ren tayong magagawa.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/6/2008
Posts: 46
Points: 138
Location: manila
|
ive confirmed with my fellow pinoy guildies.. pldt has it ok..
hula ko lang to a.. ive been trying to reconnect these past few hours
puro 121.96 lang napupuntahan kong mga IP
if this is the case then almost lahat tayo pare parehas na server = congested
they should up the 121.97 server [and the 125.xx aswell]
baka sira lang server nila or something
or dinedicate nila to business plans? dunno
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
^^
yah 121.97.xx.xx pag dyan ka naka connect based on my experience
kahit may nag youtube pa or nag DL ng torrent, asa ka pa mag lag.
hindi ko alam kung bakit hindi na nakaka connect sa address na yan.
wala eh, ganon tlga
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/20/2010
Posts: 75
Points: 225
|
loltron wrote:still sucky latency even after the maintenance....
i can only do 5mans and sit around towns. sigh
guess no 10/25mans until bayan patches things up. That's what I've been doing recently. Waking up early (6AM-7AM) do daily heroic. Main and alt. Then log off. When I come back from work. I just craft in cities. :/ And go to a trusted cafe for icc once a week. On another note, I've also noted having the same ip "121.97.xx.xx" which ultimately leads to 202.78.119.1 and confirmed lag at the next hop "12.119.139.13 ". It seems we are all on the same route.
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2008
Posts: 42
Points: 126
Location: QC
|
Agreed. It was a sudden issue started sometime last week.. I believe we do not have the latency problem 2 weeks ago and in my case, 1 year akong nag raid without issues.
BayanDSL, assistance on this matter is highly appreciated especially for your loyal customers who happens to play WoW. =)
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
Well wala tayong magagawa kundi mag daily random heroics nalang for frost badges.
dahil sa latency naten eh sure dc sa 25s.
Bayan Reply naman dyan.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/20/2010
Posts: 75
Points: 225
|
Alt leveling time. :p
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/6/2008
Posts: 46
Points: 138
Location: manila
|
honestly all they have to do is just config and allow us to connect to the other bayantel servers
baka kasi isolated lang case naten since most of us are in QC and near ABS-CBN
i have friends na taga manila who arent experiencing the same problem meron din ako kilala taga baranggay pag-asa near SM north
same lang mabilis sa kanila kagaya ng dati..
i hope bayantel IT can look into this
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/25/2010
Posts: 64
Points: -2
Location: QC
|
Im also suffering this problem, sa Call of Duty: MW2. 3 days ago nag start. nabigyan na ako Ticket number at may tumawag na din, ang sabi NORMAL DAW yoon at wala sila magagawa!!!huuhhuhu need some advice. Nag red ping na ako naun kahit may SOD 1.5MBPS
|
|
Rank: Newbie
Groups: Member
Joined: 2/26/2010
Posts: 1
Points: 3
Location: Manresa, Q.C.
|
same here di lang pala ako nag iisa na naka experience n2 buti nakita ko ang thread na to. 1 year mahigit na po ako na customer i never experienced this until last week. I'm one of your loyal customers, paki tingnan naman po ang problema. sa Q.C. Manresa area po ako. maraming salamat.
|
|
Rank: Member
Groups: Member
Joined: 2/22/2010
Posts: 15
Points: 45
Location: Davao City
|
I used. Smoothping para ma-lower lang ping ko for the sake magawa ko lang ung Red Glare Achievement sa Lunar Festival.
From 700~1000 ms, naging 287~396 ms. hohoho. The bad part nadidisconnect every 20mins, trial lang kasi. Di ko na ginamit. Pede ba ma-crack? hehe...
1 14 ms 11 ms 11 ms 210.4.58.2
2 33 ms 32 ms 32 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
3 32 ms 31 ms 33 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
4 36 ms 31 ms 31 ms 202.78.119.1 <<<<<< Bayantel
5 399 ms 392 ms 393 ms 12.119.139.13 <<<<<<<<<<<<< AT&T
6 407 ms 412 ms 424 ms cr2.sffca.ip.att.net [12.122.136.66]
7 445 ms 429 ms 427 ms cr2.la2ca.ip.att.net [12.122.31.133]
8 436 ms 426 ms 423 ms cr2.dlstx.ip.att.net [12.122.28.177]
9 441 ms 439 ms 437 ms gar23.dlstx.ip.att.net [12.122.138.153]
10 425 ms 431 ms 435 ms 12-122-254-154.attens.net [12.122.254.154]
11 565 ms 449 ms 428 ms mdf002c7613r0001-tge-12-1.dal1.attens.net [63.241.193.150]
try tracert yahoo and worldofwarcraft website. halos pareho lang ...
The WoW technicals said its normal kung papatak ng 400ms sympre tatawid pa ung cable overseas. Im wondering wala na ung loss packets * kaso pumapatak parin ng 700~1k ms ung latency ko.
Someone said sa WoW Forums i-reroute ng Bayantel ung traffic from LA to Seattle nalang so (Bayantel > seattle > WoW). Kasi daw nagkakaproblema ung mga servers sa LA. Nabasa ko lang yan sa WoW Forums.
Bukas na bukas, try ko ibang ISP maglaro ng WoW.
Btw, nakakaramdam ako ng slow-down ng internet when browsing the net.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
Freezerburn wrote:I used. Smoothping para ma-lower lang ping ko for the sake magawa ko lang ung Red Glare Achievement sa Lunar Festival.
Bukas na bukas, try ko ibang ISP maglaro ng WoW.
pldt and globe are working just fine. halata naman sa bayan na ang problema kasi bakit pag wee hours in the morning up to 9am, hindi na mataas ang latency. same here QC Filinvest II Area.
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/7/2009
Posts: 31
Points: 93
Location: Philippines
|
WTB Green Ping kahit yellow na !
|
|
|
Guest |
