Situation's improved somewhat. 200-300ms in Dalaran. But only 11pm-10am. Still have to resort to other networks for the raids. Hope the repairs will be done soon.

Update po. QQ !

This is similar to what I have during peak hours (I assume it to be 6pm-11pm). And yes, latency issues can kill you and lose your spot in raids. However, work is still being done, so I have not quite lost hope yet. Interestingly enough, I get very good latencies in the morning (6am-10am) before the lag hits me hard again for most of the day and night. I will post my tracerts when I get home for reference and comparison.

Update as of March 18:

There are currently 3 subterranean cables that carry traffic for internet users in the Philippines going out of Asia, the EAC, APCN2 and the Intra-Asia network of cables. As of March 17, only the EAC cable and Intra-Asia cables are operational, with the EAC being restored under normal operations by March 31 2010. The APCN2 cable as of 1AM March 17 suffered additional major cable breaks that rendered the Philippine Islands temporarily isolated via the APCN2 cables. To augment this, a 4 way re-routing was done as indicated in our previous updates, with our connections being re-routed to Malaysia, Thailand, Indonesia and Australia to bypass the APCN2 cables. The repair vessels slated to fix the damages of the APCN2 cable is due to arrive at the affected areas by March 19 2010. There are no ETRs established as to when the APCN2 affected segments will be fully operational. Internet services in the region will remain operational due to the re-routing of internet traffic done to bypass the affected areas.

Further updates will be provided as necessary. Please note that this update is only for registered Bayan Forum Members.

---

If the post is in size 6 or big sized font, it means I am addressing you as a moderator. If the post is in the default size, it means I am Mikos the plain subscriber.

Bayan Forum Rules

Tracing route to 12-129-225-103.attens.net [12.129.225.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 10 ms 12 ms 121.97.73.229.bti.net.ph [121.97.73.229]
3 10 ms 10 ms 10 ms 121.96.0.218.bti.net.ph [121.96.0.218]
4 9 ms 10 ms 10 ms 121.96.0.218.bti.net.ph [121.96.0.218]
5 10 ms 12 ms 10 ms 202.78.119.1
6 346 ms 349 ms 359 ms 12.119.139.13
7 361 ms * 372 ms cr1.sffca.ip.att.net [12.122.137.66]
8 371 ms 367 ms 376 ms cr1.la2ca.ip.att.net [12.122.3.122]
9 * 369 ms 372 ms cr83.la2ca.ip.att.net [12.123.30.109]
10 366 ms 373 ms 376 ms gar5.la2ca.ip.att.net [12.122.128.25]
11 365 ms 370 ms 370 ms 12.122.255.74
12 366 ms 361 ms 368 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]

Latency at this time as I post sucks. 963 ms. However, I guess when most people go to sleep (or are still asleep), judging by the route described by Mikos, Indonesia and Malaysia will still be mostly "asleep". Save for Australia since they are ahead in time of us. (Yes I am aware of the router setup, but I cannot remove it for the moment). Could explain the good latencies during those morning hours. As seen here:


Tracing route to 12-129-225-103.attens.net [12.129.225.103]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 10 ms 10 ms 121.97.73.229.BTI.NET.PH [121.97.73.229]
3 10 ms 10 ms 10 ms 121.96.0.218.BTI.NET.PH [121.96.0.218]
4 10 ms 9 ms 10 ms 121.96.0.218.BTI.NET.PH [121.96.0.218]
5 30 ms 10 ms 10 ms 202.78.119.1
6 170 ms 168 ms 169 ms 12.119.139.13
7 183 ms 183 ms 183 ms cr1.sffca.ip.att.net [12.122.137.70]
8 183 ms 182 ms 182 ms cr1.la2ca.ip.att.net [12.122.3.122]
9 182 ms 183 ms 183 ms cr83.la2ca.ip.att.net [12.123.30.109]
10 180 ms 181 ms 181 ms gar5.la2ca.ip.att.net [12.122.128.25]
11 184 ms 182 ms 182 ms 12.122.255.74
12 182 ms 182 ms 182 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]


So the problem deepens, and it looks more complicated and troubling than first assumed. Not entirely unexpected. What I do expect however is a prolonged wait before things get better. New problems = new ETR's and with problems like these, ETR's can be very arbitrary.

Time to do the rarely thinkable. For those of you who REALLY want to raid. Raid with the Americans or Australians. Assuming raids usually start 7pm, THEIR time, the schedule is as follows:

PST Servers = 7:00 pm for them, 10 am for us.
CST Servers = 7:00 pm for them 8:00 am for us
EST Servers = 7:00 pm for them, 7:00 am for us
Oceanic Servers = 7:00 pm for them, 4:00 pm for us.

So I guess oceanic servers are a bad idea at the moment (unless you raid at a cafe). Thanks Mikos for shedding some more light on how these undersea cables work and route. Repairing those things are no joke. Nor can they be hurried or solved immediately. (Short of maybe changing isp's, but given the state of things, its not a guaranteed thing.)

Latency at this ungodly hour is at 1100ms (heroic dungeon)

Time: 7:17am
Latency: 450ms ~ 550ms (latency is starting to look good at this moment)

Wasn't able to continue to monitor the latency since I had to leave early for OT work around 8am but it looks like the latency only starts to drop at around 7am, which leaves roughly a 3hr (or less) window for raiding ... assuming there are enough people online at that time *sigh*

600ms - 1K ms so far. However, I took a risk and at the very least I wasn't disconnecting (a whole lot). Tolerable. Definitely not tank or healer worthy for raids. But it'll do. At least I sense some improvement. :D

EDIT: It's not tolerable however in 25's. :/ Stick to 10's for the meantime if you're not a tank or healer.

Actually it got worse based on my experience. Dati 6am-10am maayos yung connection. Ngayon 7am hangang 8:30am na lang maayos yung connection, the rest of the day you get 600ms ~ 1k ms latency