High Latency BayanDSL

My email exchange with CSDIP regarding high latency of my internet connection. I've been getting a rountrip time exceeding 2000ms! HIGH SCORE again for me!

Me (Sep 18):

I'm getting latency exceeding 2000ms. Kindly do something about this. Thank you.

BayanDSL CSDIP (Sep 18):

As per update from our Data Network Team, the IP on the test results given awhile ago is with the same block as one of our DNS servers and is restricted for PING.

As part of our basic isolation, may we request again screenshots of ping and trace route to www.yahoo.com. Together with the IP obtained.

Cristina M. Gulapa
Customer Support for Data & IP Services

Me (Sep 19):

Kindly retrieve all these 14 emails from me to CSDIP for your reference. I've been using 202.78.97.1 since June 18, 2008 and nobody from CSDIP or DNOC bothered to correct (if this was an error). Most of these email were even acknowledged by your unit heads and TSRs.

BayanDSL CSDIP (Sep 19):

This is to acknowledge that we have already received your e-mail. As on our conversation earlier ago, this will be forwarded to our concern group for their assistance.

Best Regards,

Maple Veridiano
TSR, Customer Support for Data & IP Services Customer Care Division

Me (Sep 20):

I'm still getting latency exceeding 2000ms. Kindly do something about this. Thank you.

BayanDSL CSDIP (Sep 20):

Internet traffic is typical in this link. You may try to do the test again or conduct the test results from any websites.

Thank you.

Cristina M. Gulapa
Customer Support for Data & IP Services

Me (Sep 20):

Same goes for http://www.yahoo.com/, but i guess you would reason out that this is an "international website"

BayanDSL CSDIP (Sep 20):

This is to acknowledge your e-mail. Your test result already forwarded to our data network for checking.

Thank You,

Roxanne C. Lee
Customer Support for Data and IP Services











Learn more about latency and networking: http://compnetworking.about.com/od/speedtests/a/network_latency.htm

Ping Results 11-Sept-08

Dear Julie and Erwin,

Here are the screenshots of ping and tracert results from various websites that I frequently visit.

BayanDSL

It's only now that they did a follow-up on my 27-Aug-08 email request. I have a new blogsite. It's called http://bayandsl.multiply.com/ WAHAHAHAHAHA Taken na kasi 'yung http://bayandsl.blogspot.com/ eh ;p















Oh! Who was that?!?!?!

Five Days Later...

Five days have passed and i'm not getting ANY reply from bayan customer support

It has been five days since my last email. I haven't recieved any reply yet and i'm still getting a high latency. Please see to it that this be addressed the soonest time possible.

The fault ticket has been open for MORE THAN two months now.

Ping results are still bad... darn!!!

Reply from 202.78.97.1: bytes=32 time=1373ms TTL=250
Reply from 202.78.97.1: bytes=32 time=735ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1143ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1163ms TTL=250
Reply from 202.78.97.1: bytes=32 time=775ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1189ms TTL=250
Reply from 202.78.97.1: bytes=32 time=357ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1036ms TTL=250
Reply from 202.78.97.1: bytes=32 time=639ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1311ms TTL=250
Reply from 202.78.97.1: bytes=32 time=771ms TTL=250
Reply from 202.78.97.1: bytes=32 time=882ms TTL=250
Reply from 202.78.97.1: bytes=32 time=846ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1090ms TTL=250
Reply from 202.78.97.1: bytes=32 time=433ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1096ms TTL=250
Reply from 202.78.97.1: bytes=32 time=425ms TTL=250
Reply from 202.78.97.1: bytes=32 time=552ms TTL=250
Reply from 202.78.97.1: bytes=32 time=817ms TTL=250
Reply from 202.78.97.1: bytes=32 time=329ms TTL=250
Reply from 202.78.97.1: bytes=32 time=807ms TTL=250
Reply from 202.78.97.1: bytes=32 time=176ms TTL=250
Reply from 202.78.97.1: bytes=32 time=624ms TTL=250
Reply from 202.78.97.1: bytes=32 time=826ms TTL=250
Reply from 202.78.97.1: bytes=32 time=507ms TTL=250
Reply from 202.78.97.1: bytes=32 time=640ms TTL=250
Reply from 202.78.97.1: bytes=32 time=624ms TTL=250
Reply from 202.78.97.1: bytes=32 time=20ms TTL=250
Reply from 202.78.97.1: bytes=32 time=252ms TTL=250
Reply from 202.78.97.1: bytes=32 time=59ms TTL=250
Reply from 202.78.97.1: bytes=32 time=332ms TTL=250
Reply from 202.78.97.1: bytes=32 time=276ms TTL=250
Reply from 202.78.97.1: bytes=32 time=662ms TTL=250
Reply from 202.78.97.1: bytes=32 time=766ms TTL=250
Reply from 202.78.97.1: bytes=32 time=944ms TTL=250
Reply from 202.78.97.1: bytes=32 time=448ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1028ms TTL=250
Reply from 202.78.97.1: bytes=32 time=659ms TTL=250
Reply from 202.78.97.1: bytes=32 time=399ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1013ms TTL=250
Reply from 202.78.97.1: bytes=32 time=455ms TTL=250
Reply from 202.78.97.1: bytes=32 time=896ms TTL=250
Reply from 202.78.97.1: bytes=32 time=420ms TTL=250
Reply from 202.78.97.1: bytes=32 time=307ms TTL=250
Reply from 202.78.97.1: bytes=32 time=770ms TTL=250
Reply from 202.78.97.1: bytes=32 time=37ms TTL=250
Reply from 202.78.97.1: bytes=32 time=650ms TTL=250
Reply from 202.78.97.1: bytes=32 time=23ms TTL=250
Reply from 202.78.97.1: bytes=32 time=209ms TTL=250
Reply from 202.78.97.1: bytes=32 time=821ms TTL=250
Reply from 202.78.97.1: bytes=32 time=497ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1477ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1083ms TTL=250
Reply from 202.78.97.1: bytes=32 time=249ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1722ms TTL=250
Reply from 202.78.97.1: bytes=32 time=854ms TTL=250

Print Screen Drop Test at Port

On Sun, Aug 10, 2008 at 1:08 PM, Ariel Aguilar amaguilar427@yahoo.com wrote:

Good pm,

Would like to forward result of droptest at port done by osc 765- Bernardo this morning...see attach files...thanks

My reply, Aug 10, 2008 at 1:42 PM:

There seems to be a conflict with what you got and what i'm getting...

I'm getting a high latency for ping: range of 700ms to 2100ms

and bandwidth connection of 120 kbits/s DL, 219 kbits/s UL



Panalo! High Score pa rin ang ping results ko!

bayanDSL 1.2 mbps plan
BayanTel

Reply from 202.78.97.1: bytes=32 time=1835ms TTL=250
Reply from 202.78.97.1: bytes=32 time=2018ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1869ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1616ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1258ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1362ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1326ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1518ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1700ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1772ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1875ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1904ms TTL=250
Reply from 202.78.97.1: bytes=32 time=2000ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1841ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1788ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1589ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1851ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1752ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1424ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1682ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1245ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1282ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1500ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1306ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1644ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1366ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1142ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1028ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1107ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1236ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1214ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1302ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1024ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1074ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1209ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1374ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1372ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1413ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1765ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1706ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1051ms TTL=250
Reply from 202.78.97.1: bytes=32 time=738ms TTL=250
Reply from 202.78.97.1: bytes=32 time=889ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1122ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1162ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1188ms TTL=250
Reply from 202.78.97.1: bytes=32 time=2029ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1530ms TTL=250
Reply from 202.78.97.1: bytes=32 time=2163ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1595ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1373ms TTL=250
Reply from 202.78.97.1: bytes=32 time=719ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1578ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1326ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1270ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1877ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1419ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1105ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1529ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1594ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1033ms TTL=250
Reply from 202.78.97.1: bytes=32 time=400ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1329ms TTL=250
Reply from 202.78.97.1: bytes=32 time=835ms TTL=250
Reply from 202.78.97.1: bytes=32 time=826ms TTL=250

Ping Results

Ping Results for 1.2mbps plan. DAMN! High Score ako lagi sa mga ping ko!

bayanDSL 1.2 mbps plan
BayanTel

Reply from 202.78.97.1: bytes=32 time=1369ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1713ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1680ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1339ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1275ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1213ms TTL=250
Reply from 202.78.97.1: bytes=32 time=995ms TTL=250
Reply from 202.78.97.1: bytes=32 time=919ms TTL=250
Reply from 202.78.97.1: bytes=32 time=655ms TTL=250
Reply from 202.78.97.1: bytes=32 time=654ms TTL=250
Reply from 202.78.97.1: bytes=32 time=685ms TTL=250
Reply from 202.78.97.1: bytes=32 time=874ms TTL=250
Reply from 202.78.97.1: bytes=32 time=919ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1059ms TTL=250
Reply from 202.78.97.1: bytes=32 time=994ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1808ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1104ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1651ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1495ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1317ms TTL=250
Reply from 202.78.97.1: bytes=32 time=761ms TTL=250
Reply from 202.78.97.1: bytes=32 time=218ms TTL=250
Reply from 202.78.97.1: bytes=32 time=46ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1496ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1058ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1400ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1292ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1132ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1199ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1164ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1402ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1300ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1431ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1635ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1288ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1025ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1215ms TTL=250
Reply from 202.78.97.1: bytes=32 time=731ms TTL=250
Reply from 202.78.97.1: bytes=32 time=700ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1495ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1058ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1058ms TTL=250
Reply from 202.78.97.1: bytes=32 time=870ms TTL=250
Reply from 202.78.97.1: bytes=32 time=827ms TTL=250
Reply from 202.78.97.1: bytes=32 time=903ms TTL=250
Reply from 202.78.97.1: bytes=32 time=856ms TTL=250
Reply from 202.78.97.1: bytes=32 time=622ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1044ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1166ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1258ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1322ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1823ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1401ms TTL=250
Reply from 202.78.97.1: bytes=32 time=1914ms TTL=250
Reply from 202.78.97.1: bytes=32 time=809ms TTL=250
Reply from 202.78.97.1: bytes=32 time=873ms TTL=250

RTO 3-July-2008 2236H (FAULT TICKET OPEN FOR MORE THAN ONE MONTH NOW)

To Vangie Esguerra, Vince Dimaculangan, and Isay Manuel;

I got disconnected again tonight (3-July-2008) at 10:36 pm. Kindly provide me detailed update on this concern thru email. My fault ticket has been open for more than one month now. I find it strange this was reported as early as 23-May-200 and you still haven't addressed this situation up until now.

bayanDSL 1.2 mbps plan
BayanTel

Reply from 202.78.97.1: bytes=32 time=14ms TTL=254
Reply from 202.78.97.1: bytes=32 time=21ms TTL=254
Reply from 202.78.97.1: bytes=32 time=221ms TTL=254
Reply from 202.78.97.1: bytes=32 time=19ms TTL=254
Reply from 202.78.97.1: bytes=32 time=16ms TTL=254
Reply from 202.78.97.1: bytes=32 time=26ms TTL=254
Reply from 202.78.97.1: bytes=32 time=20ms TTL=254
Reply from 202.78.97.1: bytes=32 time=349ms TTL=254
Reply from 202.78.97.1: bytes=32 time=195ms TTL=254
Reply from 202.78.97.1: bytes=32 time=16ms TTL=254
Reply from 202.78.97.1: bytes=32 time=155ms TTL=254
Reply from 202.78.97.1: bytes=32 time=304ms TTL=254
Reply from 202.78.97.1: bytes=32 time=22ms TTL=254
Reply from 202.78.97.1: bytes=32 time=20ms TTL=254
Reply from 202.78.97.1: bytes=32 time=26ms TTL=254
Reply from 202.78.97.1: bytes=32 time=18ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Disconnected for the thrid and fourth time tonight 2-July-2008 (2227H and 2229H)

To Vangie Esguerra, Isay Manuel, and Vince Dimaculangan;

Napapadalas na yata ang disconnection ko. This is not worth the money i'm paying. Please do something about this ASAP.

bayanDSL 1.2 mbps plan
BayanTel

Ping 3rd and 4th disconnection

Reply from 202.78.97.1: bytes=32 time=19ms TTL=254
Reply from 202.78.97.1: bytes=32 time=19ms TTL=254
Reply from 202.78.97.1: bytes=32 time=18ms TTL=254
Reply from 202.78.97.1: bytes=32 time=20ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.78.97.1: bytes=32 time=18ms TTL=254
Reply from 202.78.97.1: bytes=32 time=16ms TTL=254
Reply from 202.78.97.1: bytes=32 time=16ms TTL=254
Reply from 202.78.97.1: bytes=32 time=16ms TTL=254
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 202.78.97.1: bytes=32 time=16ms TTL=254
Reply from 202.78.97.1: bytes=32 time=18ms TTL=254
Reply from 202.78.97.1: bytes=32 time=15ms TTL=254

Disconnected Twice 2-July-2008 (2202H and 2207H)

To Vangie Esguerra, Isay Manuel, and Vince Dimaculangan;

I got disconnected twice just now. Your TSR informed me that it was due to port error. It has been a month since i reported this situation. Please see to it that this be resolved immediately.

bayanDSL 1.2 mbps plan
BayanTel




Ping Results prior to the second disconnection.

Pinging 202.78.97.1 with 32 bytes of data:
Reply from 202.78.97.1: bytes=32 time=688ms TTL=254
Reply from 202.78.97.1: bytes=32 time=535ms TTL=254
Reply from 202.78.97.1: bytes=32 time=439ms TTL=254
Reply from 202.78.97.1: bytes=32 time=612ms TTL=254
Reply from 202.78.97.1: bytes=32 time=483ms TTL=254
Reply from 202.78.97.1: bytes=32 time=492ms TTL=254
Reply from 202.78.97.1: bytes=32 time=609ms TTL=254
Reply from 202.78.97.1: bytes=32 time=227ms TTL=254
Reply from 202.78.97.1: bytes=32 time=1087ms TTL=254
Reply from 202.78.97.1: bytes=32 time=558ms TTL=254
Reply from 202.78.97.1: bytes=32 time=132ms TTL=254
Reply from 202.78.97.1: bytes=32 time=623ms TTL=254
Reply from 202.78.97.1: bytes=32 time=753ms TTL=254
Reply from 202.78.97.1: bytes=32 time=410ms TTL=254
Reply from 202.78.97.1: bytes=32 time=562ms TTL=254
Reply from 202.78.97.1: bytes=32 time=742ms TTL=254
Reply from 202.78.97.1: bytes=32 time=357ms TTL=254
Reply from 202.78.97.1: bytes=32 time=253ms TTL=254
Reply from 202.78.97.1: bytes=32 time=316ms TTL=254
Reply from 202.78.97.1: bytes=32 time=620ms TTL=254
Reply from 202.78.97.1: bytes=32 time=346ms TTL=254

Erratic DSL Connection 01-Jul-2008 2344H

Ping round trip time is now exceeding 400ms. Kindly provide solutions the soonest time possible. My fault ticket with you has been open for more than a month now.

bayanDSL 1.2 mbps plan
BayanTel

Reply from 202.78.97.1: bytes=32 time=473ms TTL=250
Reply from 202.78.97.1: bytes=32 time=438ms TTL=250
Reply from 202.78.97.1: bytes=32 time=229ms TTL=250
Reply from 202.78.97.1: bytes=32 time=627ms TTL=250
Reply from 202.78.97.1: bytes=32 time=403ms TTL=250
Reply from 202.78.97.1: bytes=32 time=291ms TTL=250
Reply from 202.78.97.1: bytes=32 time=355ms TTL=250
Reply from 202.78.97.1: bytes=32 time=27ms TTL=250
Reply from 202.78.97.1: bytes=32 time=147ms TTL=250
Reply from 202.78.97.1: bytes=32 time=250ms TTL=250
Reply from 202.78.97.1: bytes=32 time=408ms TTL=250
Reply from 202.78.97.1: bytes=32 time=385ms TTL=250
Reply from 202.78.97.1: bytes=32 time=518ms TTL=250
Reply from 202.78.97.1: bytes=32 time=365ms TTL=250
Reply from 202.78.97.1: bytes=32 time=435ms TTL=250
Reply from 202.78.97.1: bytes=32 time=548ms TTL=250
Reply from 202.78.97.1: bytes=32 time=477ms TTL=250
Reply from 202.78.97.1: bytes=32 time=408ms TTL=250
Reply from 202.78.97.1: bytes=32 time=595ms TTL=250
Reply from 202.78.97.1: bytes=32 time=345ms TTL=250
Reply from 202.78.97.1: bytes=32 time=453ms TTL=250