|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
shemai wrote:ok i found a temporary remedy to our situation. i signed up for wowtunnels and used their client but do not use WEST servers, use the singapore server. i get 200-300ms but i get dc's every 40mins. i dont know how to pay for wowtunnels because apparently it is a prepaid service. hope this helps :) thx! EDIT: i tried shemai's wowtunnel and i got dc'ed after 40mins. and then i tried login back on WITHOUT WOW TUNNELS and WTFOMGLAZORZ...i got a normal 240ms. i think this one posted on wowtunnels did the trick: Open C:\Windows\System32\Drivers\Etc Now there should be a hosts file, right click the file and go to properties, now uncheck the "Read Only" property and click Ok. Then open the hosts file with Notepad. Add this to the end of the file: 12.129.206.130 us.logon.battle.net (or 213.248.127.130 eu.logon.battle.net) for EU sers. Now save the hosts file and the error should be fixed. Not saying its a fix, just saying it worked for me. EDIT#2: Akala ko naayos nyan yung latency haha. pag patak ng 2am balik 400ms un tracert haha
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/27/2010
Posts: 42
Points: 126
Location: QC
|
its normal to get dc'd coz its we aint subscribing yet to wowtunnels and its kinda like their 'trial' promo. but if that fixes it, then haha, arent we resourceful. gonna try it later xD
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2008
Posts: 42
Points: 126
Location: QC
|
sigh, unusual high latency is back.. unusual may become usual? =(
Contrary to what has been said, undersea repair cables are usually announced in the news or in public.
Also, I do not get it. Think about it:
1. around 3 weeks high latency
2. then 10-15mins RTO on all website (this mean something was re-routed/re-configured)
3. then all latency was FINE and became the USUAL.
4. after a day, back to high latency again. (means something was re-configured again back to the Number 1 state)
5. then the repair announcement
Something is wrong between the lines.. It really doesn't make sense. =)
|
|
Rank: Moderator
Groups: Member
, Moderator
Joined: 3/27/2009
Posts: 7,937
Points: 15,729
Location: Sa Web (aka Cyberspace)
|
errolski wrote:sigh, unusual latency is back.. unusual may become usual? =(
Contrary to what has been said, undersea repair cables are usually announced in the news or in public. That is a misconception. Not all are announced. Further, this is not a major problem nor is generally impacting on the users of the internet. The only consequence is the increase in the latency in some applications or to some websites. I will give you an very good example. In the last APCN 2 cable problem, only 3 segments were made public. That was made public since those were impacting on all internet users. The rest were not. While the APCN2 cable was undergoing repair, another cable went down, yet that was not made public since it only affected certain group of internet users.errolski wrote:
Also, I do not get it. Think about it:
1. around 3 weeks high latency
The latency is the consequence of the problem. I will understand why it took them so long to find where the problem is as this was outside their network.errolski wrote:
2. then 10-15mins RTO on all website (this mean something was re-routed/re-configured)
As indicated, some connections will be re-routed. By the way, I will beg to disagree with you about RTOs on all websites. You cannot generalize since there was no internet down time. If you say that there is an RTO on all websites, that is almost the same as an internet downtime since no site is accessible. In this case you already have a problem with the line itself or with the connection. While everyone is having problems with Facebook, Yahoo and other sites, I was online in the browser game that I am currently addicted to (Ogame.US, which I cannot afford not to monitor on occasions considering I am in command of a group of players... Kala niyo kayo lang mahilig sa games... Hehehehe... Di nga lang ganun ka high tech yung akin) and that is located in the USA. Popperian Falsification theory will tell you that general statements are very dangerous as they can be easily overturned by a single instance contrary to the general statement. errolski wrote:
3. then all latency was FINE and became the USUAL.
4. after a day, back to high latency again. (means something was re-configured again back to the Number 1 state)
As stated, some will continue to experience the problem. In a repair being done, it is usual that things get re-routed randomly. This is a consequence of the re-routing being done on occasions. So there are times when the latencies to some sites will go down, there are times that it goes up. And not everyone is affected.errolski wrote:5. then the repair announcement I do not appreciate your insinuations in this statement. Honestly, I got the info just this morning and the explanation. If you noticed, my update was very plain and simple. Have you considered that the information shared to me is strictly confidential? Yet because everyone here is asking for updates, and since I want to extend a helping hand in somehow understanding what is going on, I made a very plain and basic update. To many, this was sufficient. You have to consider that there are some information only relegated to moderators and not for the general public as the details will not benefit them.
I do not release updates just to make an alibi. If I don't have any updates at hand, then I remain quiet. Plain and simple. I believe I deserve more credit than that. We are both subscribers. It will not benefit me if I will cover up for BayanDSL since what affects you guys, also affects me.errolski wrote:Something is wrong between the lines.. It really doesn't make sense. =)
As far as I am concerned from a technical perspective, the circumstances all jive and match. If you are not satisfied with the explanation, then I cannot do anything about that. I am not here to convince people. I am merely here to help. In the end, I can only have this mind set: Either I am a part of the solution or I am a part of the problem. I chose to be a part of the solution. Whether I succeed or not, in the end, I know I have done my part.
 The Forum is NOT an Online Technical Support.
For your DSL/Phone concerns please call the hot lines FIRST before posting it in the Forum.
This includes requests for port resets, DSL connection footprints (ATT and SNRs), requests for technicians and repairs.
Please read the Bayan Forum Rules. Bayan Forum Rules
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2008
Posts: 42
Points: 126
Location: QC
|
Mikos, do not worry as I do not blame you or any person in this matter. I am just stating what I observed. relax there. =) No insinuation intended too. Its the facts i am talking about and not the person. Any of my post did not mean to discredit you or anyone. In fact, i highly appreciate your concern about this specific thread and thank you.
I think I am misunderstood, I did not intend to make a list of rants or whining. The list is meant to be in chronological order which I believe does not make sense if you look at it in that manner.
Anyway, as for my technical point of view, it doesn't jive or match. It would make more sense if the facts in chronoligical order was something like the following:
1. around 3 weeks high latency
2. then 10-15mins RTO on all website (this mean something was re-routed/re-configured)
3. then all latency was FINE and became the USUAL. (IF THIS FACT/EVENT DID NOT HAPPENED HERE)
4. after a day, back to high latency again. (means something was re-configured again back to the Number 1 state)
5. then the repair announcement
6. then all latency was FINE and bacame the USUAL. <<--this event should've been here hehe...
Hope I made sense.. can anyone see my point? hehe!
By the way, I am sorry about the hasty generalization of saying "RTO on all website". Should've been "on most common website". I did generalized because I saved a few tracerts(see below) during that time that can support my statement. I did not tried every website. hehe. I only tried most common sites. Maybe in the future, i would.. =)
Tracert to support my statement as a fact. =)
tracert yahoo.com
Tracing route to yahoo.com [209.131.36.159]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.2.1
2 13 ms 14 ms 13 ms 121.96.128.1.bti.net.ph [121.96.128.1]
3 15 ms 13 ms 14 ms 121.96.0.138.bti.net.ph [121.96.0.138]
4 13 ms 14 ms 15 ms 121.96.0.138.bti.net.ph [121.96.0.138]
5 23 ms 12 ms 14 ms 202.78.119.9
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 270 ms 268 ms 266 ms te-8-1.bas-a2.sp1.yahoo.com [209.131.32.19]
11 * * * Request timed out.
tracert 12.129.225.71
Tracing route to 12-129-225-71.attens.net [12.129.225.71]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.2.1
2 13 ms 14 ms 15 ms 121.96.128.1.bti.net.ph [121.96.128.1]
3 11 ms 14 ms 15 ms 121.96.0.138.bti.net.ph [121.96.0.138]
4 12 ms 14 ms 13 ms 121.96.0.138.bti.net.ph [121.96.0.138]
5 14 ms 14 ms 14 ms 202.78.119.9
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 237 ms 238 ms 239 ms 12.122.255.74
16 238 ms 250 ms 239 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
17 * * * Request timed out.
|
|
Rank: Moderator
Groups: Member
, Moderator
Joined: 3/27/2009
Posts: 7,937
Points: 15,729
Location: Sa Web (aka Cyberspace)
|
errolski wrote:Mikos, do not worry as I do not blame you or any person in this matter. I am just stating what I observed. relax there. =) No insinuation intended too. Its the facts i am talking about and not the person. In fact, i appreciate your concern about this specific thread.
I think I am misunderstood, I did not intend to make a list of rants or whining. The list is meant to be in chronological order which I believe does not make sense if you look at it in that manner.
Anyway, as for my technical point of view, it doesn't jive or match. It would make more sense if the facts in chronoligical order was something like the following:
1. around 3 weeks high latency
2. then 10-15mins RTO on all website (this mean something was re-routed/re-configured)
3. then all latency was FINE and became the USUAL. (IF THIS FACT/EVENT DID NOT HAPPENED HERE)
4. after a day, back to high latency again. (means something was re-configured again back to the Number 1 state)
5. then the repair announcement
6. then all latency was FINE and bacme the USUAL. <<--this event should've been here hehe...
Hope I made sense.. can anyone see my point? hehe! Sorry about that. I now get your point. Please just excuse me and I beg your indulgence on this (you probably know the reason why na rin having posted it earlier, pero I edited it for personal reasons). I did not mean to argue there. Perhaps just to state my perspective. I appreciate your clearing the air for everyone. 
Anyhow, the repair is not yet done. It is still on going. It will take them 15-20 days this March to complete the repairs. This is so because they are doing a staggered repair. Thus step number 6 will not happen yet till they are done with the repairs this month.
These are my current tracerts:
Tracing route to yahoo.com [209.131.36.159]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms ****** <-- Blotted it. I do not like my private ip address exposed (yeah I am using a router with all the security thing up).
2 10 ms 10 ms 10 ms 121.97.74.168.bti.net.ph [121.97.74.168]
3 10 ms 10 ms 10 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
4 10 ms 10 ms 13 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
5 10 ms 10 ms 10 ms 202.78.119.1
6 438 ms 446 ms 444 ms so-4-1-0.sjc11.ip4.tinet.net [213.200.84.209]
7 423 ms 408 ms 392 ms xe-0-0-0.sjc10.ip4.tinet.net [89.149.187.181]
8 170 ms 259 ms 169 ms ge-0-3-9.pat1.sjc.yahoo.com [216.115.96.10]
9 170 ms 170 ms 171 ms UNKNOWN-216-115-107-61.yahoo.com [216.115.107.61]
10 170 ms 170 ms 171 ms te-9-1.bas-a2.sp1.yahoo.com [209.131.32.23]
11 170 ms 170 ms 170 ms b1.www.vip.sp1.yahoo.com [209.131.36.159]
I also tried WoW... I do get RTOs.
Tracing route to 12-129-225-71.attens.net [12.129.225.71]
over a maximum of 20 hops:
1 <1 ms <1 ms <1 ms ******
2 10 ms 10 ms 10 ms 121.97.74.168.bti.net.ph [121.97.74.168]
3 16 ms 10 ms 10 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
4 13 ms 203 ms 147 ms s32.lvlup3.bt-ix.bti.net.ph [202.78.96.221]
5 10 ms 10 ms 10 ms 202.78.119.1
6 169 ms 168 ms 169 ms 12.119.139.13
7 183 ms 182 ms 184 ms cr1.sffca.ip.att.net [12.122.137.66]
8 182 ms 183 ms 182 ms cr1.la2ca.ip.att.net [12.122.3.122]
9 183 ms 184 ms 183 ms cr83.la2ca.ip.att.net [12.123.30.109]
10 181 ms 181 ms 181 ms gar5.la2ca.ip.att.net [12.122.128.25]
11 182 ms 181 ms 183 ms 12.122.255.74
12 182 ms 182 ms 190 ms 12.129.193.242
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
I do get RTOs.
Possibly due to the routing done.
The Forum is NOT an Online Technical Support.
For your DSL/Phone concerns please call the hot lines FIRST before posting it in the Forum.
This includes requests for port resets, DSL connection footprints (ATT and SNRs), requests for technicians and repairs.
Please read the Bayan Forum Rules. Bayan Forum Rules
|
|
Rank: Advanced Member
Groups: Member
Joined: 12/23/2008
Posts: 42
Points: 126
Location: QC
|
Cheers sir! Gising ka pa, umaga na.. I understand where you are coming from because I do read some of the other threads. ;)
|
|
Rank: Member
Groups: Member
Joined: 2/22/2010
Posts: 15
Points: 45
Location: Davao City
|
Currently, WoWTunnels having High Ping!
Or dumadami lang ang users? ... High Ping in WoW Servers are Global scale problem na ba? lol, hope not.
try Gamepath, if you want hourly disconnection. Smoothping is nice kaso 20mins but someone cracked it though (no idea...how he do it).
besides, sabihan mo lang kaparty mo na 'Magrelog k lng'. Restart putty *poof* another 40mins. But do it in the right time.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
Freezerburn wrote:Currently, WoWTunnels having High Ping!
Or dumadami lang ang users? ... High Ping in WoW Servers are Global scale problem na ba? lol, hope not.
try Gamepath, if you want hourly disconnection. Smoothping is nice kaso 20mins but someone cracked it though (no idea...how he do it).
besides, sabihan mo lang kaparty mo na 'Magrelog k lng'. Restart putty *poof* another 40mins. But do it in the right time. try singapore server sa wow tunnels. 200-400 ms
|
|
Rank: Member
Groups: Member
Joined: 2/22/2010
Posts: 15
Points: 45
Location: Davao City
|
yep. singapore.
Previous days, nasa less 150 ms toh ah. T_T
200 = High ping. lol.
Btw, pumatak kanina ng 700 ang malaysia at singapore kaso a mere secs lang. weird. sabagay weekends ngayon. tsk.
Malaysia got 185, while sing is 200+.
Lunch muna ako. *sigh*
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/27/2010
Posts: 42
Points: 126
Location: QC
|
yeps we will have to make do with dc's every 40mins for the time being. going to try gamepath later. i want my old connection back!! QQ! still hoping for the best. :)
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/6/2008
Posts: 46
Points: 138
Location: manila
|
we're almost 1 month broken with our latency.. may feedback ba tayo pag mabilis din sa globe.. or pldt? so we have something to compare with
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/20/2010
Posts: 75
Points: 225
|
I've been online for a few hours now...It seems the situation is getting better. But remains to be seen. Current Latency is 350ms. Raidable. However, I keep a constant ping stream and lag terribly when interrupted by one or two RTO's. Which is weird. But thought I'd let you know nonetheless. The lag gives me a rubberband effect. Everything stops for a few seconds, then its like everything goes fast forward.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/27/2010
Posts: 71
Points: 213
Location: Valenzuela
|
InternetBoss wrote:I've been online for a few hours now...It seems the situation is getting better. But remains to be seen. Current Latency is 350ms. Raidable. However, I keep a constant ping stream and lag terribly when interrupted by one or two RTO's. Which is weird. But thought I'd let you know nonetheless. The lag gives me a rubberband effect. Everything stops for a few seconds, then its like everything goes fast forward. -Same here, not that good latency but better than total lagness that i felt past few days, plus RTOs are visible, but still its better, i hope itwill get back to normal soon.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/27/2010
Posts: 42
Points: 126
Location: QC
|
ok this may be a little premature but the latency seems to be getting better since last night. around 5-6pm there was terrible lag and just for the heck of it, i tried disconnecting and reconnecting my connection, then bam!! i got a good tracert, 200-300ms. been stable until now. hope this lasts!! keeping my troll fingers crossed!! :)
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/6/2008
Posts: 46
Points: 138
Location: manila
|
lucky for you guys.. mine was fine til about 12 noon then its back to the same old sluggish crap
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/27/2010
Posts: 71
Points: 213
Location: Valenzuela
|
-Wew i thought it will be for a whole day but im wrong, as of now it turned back to normal(High Latency), i just realize 15-20days is half a month(sobbing).
-They must have a compensation about this problem.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/27/2010
Posts: 42
Points: 126
Location: QC
|
/sob the lag is back :(
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/20/2010
Posts: 75
Points: 225
|
15-21 days pa naman raw ang repair schedule, so...2-3 weeks to go.
|
|
Rank: Advanced Member
Groups: Member
Joined: 2/19/2010
Posts: 30
Points: 90
Location: QC
|
napansin ko playable siya whole day except:
9pm-1am (kahit may wow tunnels hindi pwede mag raid,Nakakainis at napakamalas ko kasi ang guild ko ay nag raraid ng 9pm-12am)
12noon-9pm (500+MS pero pwede paren mag raid kahit 25s)
obervations ko lang to nung friday-sunday.
ewan ko kung ganito ren sa inyo
EDIT: as of 03/08/10 330pm 250 ms paren.
|
|
|
Guest |
