Direct Phone Lines to BayanDSL Tech Support Unit Heads

BayanDSL Customer Service Numbers You Can Call
CSDIP BayanDSL

If BayanDSL's customer service trunkline just keeps on ringing, you can always call these numbers.

Vincent Dimaculangan
02 4493651
02 4493373

Julie Lutao
02 4493322

Dennis Cruz
02 4493357

Maria Neriza "Ysay" Manuel
02 4972165

Ruben Sison Jr.
02 4493356

Evangeline Esguerra
02 4493328

Mobile Support
0917 8932189

Data and Network Operations Center (DNOC)
02 4493429

Other customer service numbers you can call
02 4493398
02 4493338
02 4493509
02 4493340

They are always here to serve you...

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

Vincent Dimaculangan "NORMAL"

Re: Ping and Tracert Results 11 Sept 2008

Vince Dimaculangan (02 4493651) of BayanDSL called Thursday night (11 Sept 2008) and told me this is... well "normal." Every time he speaks, that's what you would hear... fucking "NORMAL."

If this is normal at 1.2 mbps, how come i don't experience buffering at www.youtube.com from other ISP with lower bandwidth? Maybe its "NORMAL."

FUUUUUUCK!!!

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?!?!?!

Discourteous BayanDSL Tech Support Rep Cynthia Agabin

To: ucnaguit <ucnaguit@bayan.com.ph>

Cc: "Maria Neriza G. Manuel" MGManuel@bayan.com.ph, "Evangeline J. Esguerra" EJEsguerra@bayan.com.ph, "Vincent V. Dimaculangan" VVDimaculangan@bayan.com.ph, "Julie R. Lutao" JRLutao@bayan.com.ph, "Randolf S. Serrano" RSSerrano@bayan.com.ph, "Dennis P. Cruz" dpcruz@bayan.com.ph, "Ma. Paula O. Veridiano" moveridiano@bayan.com.ph, "Cristina M. Gulapa" cmgulapa@bayan.com.ph, CS for Data & IP Services csdip@bayan.com.ph, Customer Care CustomerCare@bayan.com.ph, customersupport@bayan.com.ph, JPSanico@bayan.com.ph


Dear Mr. Naguit,

May I call to your attention what transpired between me and one of your TSRs last Sept 5, 2008 (Friday) at around 8:30 am. I made a call to Tech Support (02 4492959) that morning to ask for updates on my fault ticket. I was able to speak to Cynthia Agabin. Before putting me on hold, the Tech Support Rep (TSR) Cynthia Agabin replied, "First call mo, Juan dela Cruz, saan ka pa!"

Disrespectful and discourteous people like this don't have a place in the customer service industry. May I request for a written apology from the person concerned and CSDIP on this concern? If you want to improve on the delivery of your service, you'd better have necessary corrective actions on matters like this.

Thank you.

Bayantel Dispute Ticket No: 0454425
Date Generated: 5 September 2008 (Friday), 9:11 am

Related posts:
http://request-timed-out.blogspot.com/search/label/Cynthia%20Agabin

LinkedIn:
https://ph.linkedin.com/pub/cynthia-agabin/75/139/405

BayanDSL TSR Cynthia Agabin

I made a call to Tech Support (02 4492959) this morning to ask for updates on my fault ticket. Before putting me on hold, the Tech Support Rep (TSR) Cynthia Agabin replied, "First call mo, Juan dela Cruz, saan ka pa!"

Well... well... Cynthia that's not the proper way to talk to your clients. Putang-ina nyo! My fault ticket's been open/unresolved for the past three months and you talk to your subcribers like this! Putang-ina nyo talaga!

Better be sorry for this!

Bayantel Dispute Ticket No: 0454 425
Date Generated: 5 September 2008, 9:20 am

Related posts:
http://request-timed-out.blogspot.com/search/label/Cynthia%20Agabin

LinkedIn:
https://ph.linkedin.com/pub/cynthia-agabin/75/139/405

Dispute Ticket 0454425

To: "Cristina M. Gulapa" <cmgulapa@bayan.com.ph>, CS for Data & IP Services <csdip@bayan.com.ph>, customersupport@bayan.com.ph, "Dennis P. Cruz" <dpcruz@bayan.com.ph>, "Evangeline J. Esguerra" <EJEsguerra@bayan.com.ph>, "Julie R. Lutao" <JRLutao@bayan.com.ph>, "Ma. Paula O. Veridiano" <moveridiano@bayan.com.ph>, "Maria Neriza G. Manuel" <MGManuel@bayan.com.ph>, MGManuel@bayantel.com.ph, "Randolf S. Serrano" <RSSerrano@bayan.com.ph>, "Vincent V. Dimaculangan" <VVDimaculangan@bayan.com.ph>


Re: BayanDSL TSR Cynthia Agabin

I made a call to Tech Support (02 4492959) this morning to ask for updates on my fault ticket. Before putting me on hold, the Tech Support Rep (TSR) Cynthia Agabin replied, "First call mo, Juan dela Cruz, saan ka pa!"

I'm assuming that this is not the proper way to deal with your subscribers. I expect that necessary corrective actions would be put on place.

Thank you.

Related posts:
http://request-timed-out.blogspot.com/search/label/Cynthia%20Agabin

LinkedIn:
https://ph.linkedin.com/pub/cynthia-agabin/75/139/405

BayanDSL CSDIP

BayanDSL CSDIP Team


Ulysses Naguit (far right)

Ulysses C. Naguit
Department Head, Customer Support for Data & IP Services
Bayan Telecommunications, Inc.

Phone (Office): 02 4493914
Mobile Phone: 0917-8545466
Email: ucnaguit@bayan.com.ph


Join BayanDSL's Friendster: http://profiles.friendster.com/11463821

CSDIP Looking for a New Unit Head

I saw this job ad posted at http://ph.jobstreet.com/jobs/2008/7/default/20/1920856.htm?fr=J. Is someone leaving CSDIP? wahahaha

Advertised: 18-7-08 ReAlerted: 25-7-08 Closing Date: 15-9-08.

Bayan Telecommunications Inc.

Bayan Telecommunications Inc. is a leading provider of facilities-based data services and wireless fixed-line telecommunications. We offer a full range of switched and dedicated local exchange services and provide national and international long distance services to residential, business and carrier customers in the Philippines.

CUSTOMER SUPPORT FOR DATA & IP SERVICES HEAD
(National Capital Reg - Quezon City)

Requirements:

Able to implement approaches in gathering information from customer inbound interactions and outbound campaigns to understand their needs and influence business decisions affecting customer product/package development, customer acquisition process and retention programs.

Able to provide actionable information and recommendations from customer experiences through statistical methodologies at the Data and Internet Call Center as critical inputs for customer understanding.

Able to implement the strategy and operationalize the call center and Network utilities for Internet and Data customers considering the various elements such as: systems, technology, industry trends, processes and organization to meet customer satisfaction targets.

Able to recommend state-of-the art quality productivity tools and systems to improve customer satisfaction and operational efficiency.

Able to create an operations capacity plan and recommend the manpower complement to meet the service level target of the call center.

Able to execute the Customer Service Brand in the operations of the call center for Internet and Data to achieve consistency in the look, feel and customer experience.

Able to implement financial policies or improvements in processes that will eliminate mistakes and revenue leakages in the service order, fault and dispute entries for Internet and Data services.

Able to recommend actions to mitigate business risks at the call center for Data and Internet customers.

Able to establish adequate internal control in designing operations processes to ensure optimum productivity and quality call handling.

Able to recommend financial policies, systems and processes that will help meet service level targets.

Able to apply and deploy Quality concepts and principles in strengthening the processes and improving performance of the call center and Network utilities for Internet and Data services.

Able to recommend process and performance standards in order to achieve operational efficiency and customer satisfaction.

Able to lead and recommend Six Sigma projects in the deparment in order to minimize defects and variations from services and transactions.

Able to provide inputs on Rewards & Recognition program as a support structure to achieve a culture of high performance.

Able to function as Project Manager in the call center for Internet and Data projects using its standard tools and articrafts from planning, designing, resource allocation, organization, assigning, directing & controlling activites up to communication using the Project Development Stages of initiation, planning and design, development, execution and closure.

Able to implement strategic directions in the operations in order to achieve its revenue on call center outsourcing contracts.

Able to analyze trends in revenues in order to provide recommendations to the strategic direction.

Able to provide standard cost structure to achieve optimum profit from the revenue transaction.

Able to create and submit operating budgets and prepare project & capital expenses following standard documentation for the business centers.

Able to create plans and programs to support the financial plan for the business center.

Able to monitor and review variances in operating expenses and take action to improve financial results.

Able to demonstrate an in-depth understanding and knowledge of the products and services offered by the company in order to provide recommendations on product definition related to upfront customer support and post sale support planning and implementation for the call center

Interested candidates are invited to APPLY ONLINE.

For more information about us, visit our website at:
http://www.bayantel.com.ph/

BayanDSL, BayanTel Customer Support for Data and IP Services (CSDIP)

BayanDSL TSR Cynthia Agabin

Cynthia Agabin: Saan ka pa!!!


http://profiles.friendster.com/32344036

"Slow down and enjoy life. It's not only the scenery you miss by going too fast - you also miss the sense of where you are going and why."

SAAN KA PA!!!

Related Posts:
http://request-timed-out.blogspot.com/search/label/Cynthia%20Agabin

LinkedIn:
https://ph.linkedin.com/pub/cynthia-agabin/75/139/405

Re: Buffering in Youtube

Dear Julie Lutao,

I'm speaking to one of your TSRs (Chris Palad) right now to check on updates. You made another mistake in your report/memo re: IP addresses. As far as I can recall, i've repeatedly told you that 121.97... is a bad IP address. This IP address blocks my access to a range of websites that I browse on a regular basis. I used to get this IP address prior to the month of August (prior to 08 Aug 2008 to be specific).

As of the moment, i'm consistently getting 121.96... and i've also been consistently experiencing problems with websites with flash or java apps. Prior to 121.96... I used to get a range of IP addresses (121.97... included) of which I didn't note down since connectivity was good. One of the points we've discussed last night is the relationship of the IP address and my current web access concern.

Please see to it that your report/memo in my fault ticket be corrected. Thanks.

Ano ba!?!?! Nakikinig ba talaga kayo sa mga customers pag kausap nyo sila? Damn!

Re: Buffering in Youtube

Dear Vangie Esguerra and Isay Manuel,

It seems nothing's really been done on the part of tech and customer support. Puro na lang palusot ang ginagawa. Last Monday, a technician came to my residence to check on my connection. Alfie, the technician told me that it's not normal for www.youtube.com to buffer at 1.2mbps bandwidth speed. Mabagal ang connection ko with all sites that loads java and flash, that includes www.bayan.com.ph. They have used their computer to check my connection. All the screen shots that were made last Monday came from the technician's computer.

The problem now is that Vince Dimaculangan is telling me that this is just normal. All the factors he considred are all computer specific problems. So sino ang nagsasabi ng totoo, 'yun bang technician na nagpunta dito at drop test o ang inyong technical support service?

And dammit!!! How many times do I have to tell you people that I don't use a router!

---------- Forwarded message ----------
From: Customer Support
Date: Wed, Aug 27, 2008 at 10:41 PM
Subject: Buffering in youtube


Good evening! As we have discussed during our conversation. Buffering in youtube.com and other sites that may use quite a bit of flash content is normal even for a 1.2 mbps connection. There are other factors that you need to look into besides your internet bandwidth.

Router
Computer applications that are running
Browser
Type of flash player installed
Java versions or scripting

Sincerely,


VINZ
Customer Support for Data & IP Services
Customer Care Division
Bayan Telecommunications, Incorporated
7th Floor Roosevelt Operations Center
234 Roosevelt Avenue, San Francisco Del Monte
Quezon City, Philippines 1105

CSDIP Replies... Finally

On Thu, Aug 14, 2008 at 11:30 PM, CS for Data and IP Services csdip@bayan.com.ph wrote:

Cc: Ariel Aguilar amaguilar427@yahoo.com, Evangeline J. Esguerra EJEsguerra@bayan.com.ph, Maria Neriza G. Manuel MGManuel@bayan.com.ph, Vincent V. Dimaculangan VVDimaculangan@bayan.com.ph

Greetings!

This is to acknolwedge your email. Test results given will be escalated with our Personnel for thorough checking and resolution. Allow us to get back to you once update is given.

Again, our apology for the inconvenience.

Sincerely,


Cristina M. Gulapa
Technical Support Representative
Customer Support for Data and IP Services
Customer Care Division
Bayan Telecommunications, Inc.
7th Floor Roosevelt Operations Center
234 Roosevelt Avenue, SFDM Quezon City.

Ano daw?!?!? Apologies na naman!

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

Low Download Speed BayanDSL (20.1KB/s)

This is what i'm trying to tell you. I'm getting a very low DL speed. And i'm downloading from your BayanTel servers...

20.1 KB/s kelan pa ako matatapos nyan!!!

219,136 kbps at BayanDSL

Pucha! My bandwidth speed reads 219,136 kbps!!! Kagimbal-gimbal hahaha Paksyet na service 'yan ng BayanDSL. They would recommend a bandwidth speed tester which is not functional at all. Eh kelan pa ba gumana ng matino ang speed tester ng http://speed.skyinet.net/?

Paksyet talaga!

Wish ko lang 219,136 kpbs nga speed ko at hindi 290 kbps sa 1.2 mbps na plan.