home about bayan products customer support bayan cares
 
Welcome Guest Search | Active Topics | Members | Log In | Register

bayanFORUM » BayanTech Support » bayanDSL Support » Medyo Unstable after Basyang

2 pages: [1] 2
Medyo Unstable after Basyang Options · View
Previous Topic · Next Topic
jps001
Posted: Thursday, July 15, 2010 6:21:18 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
napansin ko lang na naging unstable connection ko after basyang. most of the time lagi RTO at unstable ping. bale halo halo un lumalabas. may 1000+ms, 200+ms, 93ms etc. isa lang naisip ko na sanhi ay dahil sa iniwang pinsala ni basyang. confirm ko lang is my prob si bayan ngaun if so ano un time frame bago bumalik sa normal ulit? ty
Back to top
 
Mikos
Posted: Friday, July 16, 2010 1:01:29 AM

Rank: Moderator
Groups: Member , Moderator

Joined: 3/27/2009
Posts: 9,989
Points: 18,085
Location: Sa Web (aka Cyberspace)
There are areas hit by the recent typhoon. I would understand if we do not have an ETR on it yet. After all, it was not really the rains that caused the biggest problem but rather, the gustiness of the storm that hit the region. Add to that the fact that Manila was not ready since PAG ASA forecasted it will be Northern and Central Luzon being hit but Metro Manila being the center of the action on the last minute. If I receive word from any of the Bayan Moderators regarding any service updates, I will be more than happy to update this thread. In the same manner any of the moderators with any service update may update this thread or the sticky I started. Angel

jps001 wrote:
napansin ko lang na naging unstable connection ko after basyang. most of the time lagi RTO at unstable ping. bale halo halo un lumalabas. may 1000+ms, 200+ms, 93ms etc. isa lang naisip ko na sanhi ay dahil sa iniwang pinsala ni basyang. confirm ko lang is my prob si bayan ngaun if so ano un time frame bago bumalik sa normal ulit? ty



FLAMERS shall be severely sanctioned!!!
Please lang MATINONG TANONG LANG SANA ANG ITANONG instead of NONSENSE ONES.


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.


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
Back to top
 
ozido_11
Posted: Friday, July 16, 2010 10:30:04 PM
Rank: Newbie
Groups: Member

Joined: 7/16/2010
Posts: 5
Points: 15
Location: Quezon City, Kamias
me too..QC kamias area here.. d n ako mkapag laro ng maayos sa garena after ng bagyong basyang, tpos bumaba pa ng SOBRA ung upload speed ko..ngaun 0.03~0.07 Mbps n lang..pati ping tumaas...:(

If problem continues, I'll afk for technician na.
Back to top
 
notroublefound
Posted: Friday, July 16, 2010 10:53:45 PM

Rank: Moderator
Groups: Moderator

Joined: 5/17/2008
Posts: 2,767
Points: 6,889
Location: Sa Bahay Namin
Mostly all of the IPDSLAMs in Metro Manila Area is affected by the said typhoon and the rotating brownouts. As of now 90% of the IPDSLAMs are already normalized. If your still experiencing slowdown and INT connection you may call the dsl hotline 4112000 for isolation and checking. Thanks.
--Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat--
Back to top
 
Mikos
Posted: Saturday, July 17, 2010 2:50:48 AM

Rank: Moderator
Groups: Member , Moderator

Joined: 3/27/2009
Posts: 9,989
Points: 18,085
Location: Sa Web (aka Cyberspace)
If the problem persist, I would suggest that in advising us here, after asking for a technician, to start your own thread, post your account number, and the fault ticket number.

Thank you.

ozido_11 wrote:
me too..QC kamias area here.. d n ako mkapag laro ng maayos sa garena after ng bagyong basyang, tpos bumaba pa ng SOBRA ung upload speed ko..ngaun 0.03~0.07 Mbps n lang..pati ping tumaas...:(

If problem continues, I'll afk for technician na.



FLAMERS shall be severely sanctioned!!!
Please lang MATINONG TANONG LANG SANA ANG ITANONG instead of NONSENSE ONES.


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.


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
Back to top
 
jps001
Posted: Tuesday, July 20, 2010 3:42:44 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
I present to you:
http://img838.imageshack.us/img838/9349/rto1.jpg
http://img834.imageshack.us/img834/9808/rto2.jpg
http://img827.imageshack.us/img827/59/rto3.jpg
http://img840.imageshack.us/img840/9778/rto4.jpg
http://img831.imageshack.us/img831/8071/rto5.jpg
http://img844.imageshack.us/img844/4025/rto6.jpg
http://img839.imageshack.us/img839/1348/rto7.jpg
http://img830.imageshack.us/img830/4396/rto8.jpg
http://img830.imageshack.us/img830/9769/rto9.jpg


happens somewhere between 2PM-9/10PM everyday after basyang. pero pag madaling araw ok na ok naman connection at walang mga RTOs at consistent pa na nasa 46+ms ang ping ko. hindi naman dinaanan ni basyang area namin so tingin ko walang prob sa line namin at ang prob ay nasa bayantel. ewan ko lang kung nkabalik na sa normal. at idagdag mo pa sa mga RTOs un bagal ng pag browse at this times. di na ako mag popost ng trcert at speedtest kasi madi-disappoint lang kayo^^
link nalang pinost ko kasi ang tagal mag load ng mga images sakin.
Back to top
 
jps001
Posted: Wednesday, July 21, 2010 3:03:37 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
bat ganito na naman c bayan?!

http://img28.imageshack.us/img28/2927/rto10.jpg
Back to top
 
notroublefound
Posted: Wednesday, July 21, 2010 6:50:53 PM

Rank: Moderator
Groups: Moderator

Joined: 5/17/2008
Posts: 2,767
Points: 6,889
Location: Sa Bahay Namin
jps001 wrote:
bat ganito na naman c bayan?!

http://img28.imageshack.us/img28/2927/rto10.jpg


Paki post ulit ng account number mo sir. Thanks.
--Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat--
Back to top
 
jps001
Posted: Friday, July 23, 2010 2:41:45 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
after 2 days bumalik na sa normal i think.

Reply from 74.125.71.106: bytes=32 time=81ms TTL=56
Reply from 74.125.71.106: bytes=32 time=86ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Request timed out.
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=73ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=74ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=70ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=80ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=83ms TTL=56
Reply from 74.125.71.106: bytes=32 time=78ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=79ms TTL=56
Back to top
 
notroublefound
Posted: Sunday, July 25, 2010 11:42:52 PM

Rank: Moderator
Groups: Moderator

Joined: 5/17/2008
Posts: 2,767
Points: 6,889
Location: Sa Bahay Namin
jps001 wrote:
after 2 days bumalik na sa normal i think.

Reply from 74.125.71.106: bytes=32 time=81ms TTL=56
Reply from 74.125.71.106: bytes=32 time=86ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Request timed out.
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=73ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=74ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=70ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=80ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=83ms TTL=56
Reply from 74.125.71.106: bytes=32 time=78ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=79ms TTL=56


Takot ata sakin yung connection mo Anxious
--Strategy without tactics is the slowest route to victory. Tactics without strategy is the noise before defeat--
Back to top
 
Mikos
Posted: Sunday, July 25, 2010 11:52:21 PM

Rank: Moderator
Groups: Member , Moderator

Joined: 3/27/2009
Posts: 9,989
Points: 18,085
Location: Sa Web (aka Cyberspace)
Niyahahaha....

notroublefound wrote:
jps001 wrote:
after 2 days bumalik na sa normal i think.

Reply from 74.125.71.106: bytes=32 time=81ms TTL=56
Reply from 74.125.71.106: bytes=32 time=86ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Request timed out.
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=73ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=74ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=70ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=80ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=83ms TTL=56
Reply from 74.125.71.106: bytes=32 time=78ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=79ms TTL=56


Takot ata sakin yung connection mo Anxious



FLAMERS shall be severely sanctioned!!!
Please lang MATINONG TANONG LANG SANA ANG ITANONG instead of NONSENSE ONES.


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.


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
Back to top
 
jps001
Posted: Friday, July 30, 2010 1:20:36 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
notroublefound wrote:
jps001 wrote:
after 2 days bumalik na sa normal i think.

Reply from 74.125.71.106: bytes=32 time=81ms TTL=56
Reply from 74.125.71.106: bytes=32 time=86ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Request timed out.
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=82ms TTL=56
Reply from 74.125.71.106: bytes=32 time=73ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=74ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=70ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=85ms TTL=56
Reply from 74.125.71.106: bytes=32 time=80ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=84ms TTL=56
Reply from 74.125.71.106: bytes=32 time=83ms TTL=56
Reply from 74.125.71.106: bytes=32 time=78ms TTL=56
Reply from 74.125.71.106: bytes=32 time=76ms TTL=56
Reply from 74.125.71.106: bytes=32 time=77ms TTL=56
Reply from 74.125.71.106: bytes=32 time=79ms TTL=56


Takot ata sakin yung connection mo Anxious

oo nga eh haha
kaso pag tanghali hanggang gabi ay laging mabagal net. hindi ako makapag youtube ng maayos haha at araw araw yan ganyan.
Back to top
 
jps001
Posted: Saturday, July 31, 2010 1:16:28 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
weeeee

pede mag pa port reset?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\JPS>ping google.com -t

Pinging google.com [74.125.71.103] with 32 bytes of data:

Reply from 74.125.71.103: bytes=32 time=479ms TTL=56
Reply from 74.125.71.103: bytes=32 time=914ms TTL=56
Reply from 74.125.71.103: bytes=32 time=301ms TTL=56
Reply from 74.125.71.103: bytes=32 time=529ms TTL=56
Request timed out.
Reply from 74.125.71.103: bytes=32 time=547ms TTL=56
Request timed out.
Reply from 74.125.71.103: bytes=32 time=547ms TTL=56
Reply from 74.125.71.103: bytes=32 time=522ms TTL=56
Reply from 74.125.71.103: bytes=32 time=431ms TTL=56


eto pa

Reply from 74.125.71.99: bytes=32 time=406ms TTL=56
Reply from 74.125.71.99: bytes=32 time=468ms TTL=56
Reply from 74.125.71.99: bytes=32 time=593ms TTL=56
Reply from 74.125.71.99: bytes=32 time=93ms TTL=56
Reply from 74.125.71.99: bytes=32 time=234ms TTL=56
Reply from 74.125.71.99: bytes=32 time=281ms TTL=56
Reply from 74.125.71.99: bytes=32 time=343ms TTL=56
Reply from 74.125.71.99: bytes=32 time=281ms TTL=56
Reply from 74.125.71.99: bytes=32 time=453ms TTL=56
Reply from 74.125.71.99: bytes=32 time=249ms TTL=56
Reply from 74.125.71.99: bytes=32 time=390ms TTL=56
Reply from 74.125.71.99: bytes=32 time=343ms TTL=56
Reply from 74.125.71.99: bytes=32 time=374ms TTL=56
Reply from 74.125.71.99: bytes=32 time=499ms TTL=56
Reply from 74.125.71.99: bytes=32 time=624ms TTL=56
Reply from 74.125.71.99: bytes=32 time=734ms TTL=56
Reply from 74.125.71.99: bytes=32 time=265ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=390ms TTL=56
Reply from 74.125.71.99: bytes=32 time=281ms TTL=56
Reply from 74.125.71.99: bytes=32 time=546ms TTL=56
Reply from 74.125.71.99: bytes=32 time=359ms TTL=56
Reply from 74.125.71.99: bytes=32 time=609ms TTL=56
Reply from 74.125.71.99: bytes=32 time=296ms TTL=56
Reply from 74.125.71.99: bytes=32 time=374ms TTL=56
Reply from 74.125.71.99: bytes=32 time=531ms TTL=56
Reply from 74.125.71.99: bytes=32 time=593ms TTL=56
Reply from 74.125.71.99: bytes=32 time=343ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.71.99: bytes=32 time=328ms TTL=56
Reply from 74.125.71.99: bytes=32 time=390ms TTL=56
Reply from 74.125.71.99: bytes=32 time=421ms TTL=56
Reply from 74.125.71.99: bytes=32 time=484ms TTL=56
Reply from 74.125.71.99: bytes=32 time=609ms TTL=56
Reply from 74.125.71.99: bytes=32 time=796ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.


eto pa


Reply from 74.125.71.99: bytes=32 time=426ms TTL=56
Reply from 74.125.71.99: bytes=32 time=395ms TTL=56
Reply from 74.125.71.99: bytes=32 time=437ms TTL=56
Reply from 74.125.71.99: bytes=32 time=511ms TTL=56
Reply from 74.125.71.99: bytes=32 time=346ms TTL=56
Reply from 74.125.71.99: bytes=32 time=347ms TTL=56
Reply from 74.125.71.99: bytes=32 time=173ms TTL=56
Reply from 74.125.71.99: bytes=32 time=297ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=403ms TTL=56
Reply from 74.125.71.99: bytes=32 time=418ms TTL=56
Reply from 74.125.71.99: bytes=32 time=448ms TTL=56
Reply from 74.125.71.99: bytes=32 time=407ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=428ms TTL=56
Reply from 74.125.71.99: bytes=32 time=451ms TTL=56
Reply from 74.125.71.99: bytes=32 time=486ms TTL=56
Reply from 74.125.71.99: bytes=32 time=454ms TTL=56
Reply from 74.125.71.99: bytes=32 time=396ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=323ms TTL=56
Reply from 74.125.71.99: bytes=32 time=400ms TTL=56
Reply from 74.125.71.99: bytes=32 time=431ms TTL=56
Reply from 74.125.71.99: bytes=32 time=332ms TTL=56
Reply from 74.125.71.99: bytes=32 time=244ms TTL=56
Reply from 74.125.71.99: bytes=32 time=555ms TTL=56
Reply from 74.125.71.99: bytes=32 time=542ms TTL=56
Reply from 74.125.71.99: bytes=32 time=618ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=375ms TTL=56
Reply from 74.125.71.99: bytes=32 time=465ms TTL=56
Reply from 74.125.71.99: bytes=32 time=566ms TTL=56
Reply from 74.125.71.99: bytes=32 time=515ms TTL=56
Reply from 74.125.71.99: bytes=32 time=359ms TTL=56
Reply from 74.125.71.99: bytes=32 time=374ms TTL=56
Reply from 74.125.71.99: bytes=32 time=510ms TTL=56
Reply from 74.125.71.99: bytes=32 time=557ms TTL=56
Reply from 74.125.71.99: bytes=32 time=417ms TTL=56
Reply from 74.125.71.99: bytes=32 time=507ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=466ms TTL=56
Reply from 74.125.71.99: bytes=32 time=272ms TTL=56
Reply from 74.125.71.99: bytes=32 time=411ms TTL=56
Reply from 74.125.71.99: bytes=32 time=267ms TTL=56

yan pa


Reply from 74.125.71.99: bytes=32 time=417ms TTL=56
Reply from 74.125.71.99: bytes=32 time=507ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=466ms TTL=56
Reply from 74.125.71.99: bytes=32 time=272ms TTL=56
Reply from 74.125.71.99: bytes=32 time=411ms TTL=56
Reply from 74.125.71.99: bytes=32 time=267ms TTL=56
Reply from 74.125.71.99: bytes=32 time=314ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=207ms TTL=56
Reply from 74.125.71.99: bytes=32 time=454ms TTL=56
Reply from 74.125.71.99: bytes=32 time=327ms TTL=56
Reply from 74.125.71.99: bytes=32 time=362ms TTL=56
Reply from 74.125.71.99: bytes=32 time=232ms TTL=56
Reply from 74.125.71.99: bytes=32 time=297ms TTL=56
Reply from 74.125.71.99: bytes=32 time=433ms TTL=56
Reply from 74.125.71.99: bytes=32 time=359ms TTL=56
Reply from 74.125.71.99: bytes=32 time=270ms TTL=56
Reply from 74.125.71.99: bytes=32 time=269ms TTL=56
Reply from 74.125.71.99: bytes=32 time=244ms TTL=56
Reply from 74.125.71.99: bytes=32 time=354ms TTL=56
Reply from 74.125.71.99: bytes=32 time=321ms TTL=56
Reply from 74.125.71.99: bytes=32 time=186ms TTL=56
Reply from 74.125.71.99: bytes=32 time=184ms TTL=56
Reply from 74.125.71.99: bytes=32 time=175ms TTL=56
Reply from 74.125.71.99: bytes=32 time=337ms TTL=56
Reply from 74.125.71.99: bytes=32 time=419ms TTL=56
Reply from 74.125.71.99: bytes=32 time=346ms TTL=56
Reply from 74.125.71.99: bytes=32 time=286ms TTL=56
Reply from 74.125.71.99: bytes=32 time=518ms TTL=56
Reply from 74.125.71.99: bytes=32 time=476ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=349ms TTL=56
Reply from 74.125.71.99: bytes=32 time=469ms TTL=56
Reply from 74.125.71.99: bytes=32 time=227ms TTL=56
Reply from 74.125.71.99: bytes=32 time=371ms TTL=56
Reply from 74.125.71.99: bytes=32 time=680ms TTL=56
Reply from 74.125.71.99: bytes=32 time=385ms TTL=56
Reply from 74.125.71.99: bytes=32 time=158ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=416ms TTL=56
Reply from 74.125.71.99: bytes=32 time=379ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=430ms TTL=56

at eto

Reply from 74.125.71.99: bytes=32 time=356ms TTL=56
Reply from 74.125.71.99: bytes=32 time=447ms TTL=56
Reply from 74.125.71.99: bytes=32 time=141ms TTL=56
Reply from 74.125.71.99: bytes=32 time=404ms TTL=56
Reply from 74.125.71.99: bytes=32 time=513ms TTL=56
Reply from 74.125.71.99: bytes=32 time=557ms TTL=56
Reply from 74.125.71.99: bytes=32 time=399ms TTL=56
Reply from 74.125.71.99: bytes=32 time=369ms TTL=56
Reply from 74.125.71.99: bytes=32 time=472ms TTL=56
Reply from 74.125.71.99: bytes=32 time=279ms TTL=56
Reply from 74.125.71.99: bytes=32 time=448ms TTL=56
Reply from 74.125.71.99: bytes=32 time=502ms TTL=56
Reply from 74.125.71.99: bytes=32 time=278ms TTL=56
Reply from 74.125.71.99: bytes=32 time=393ms TTL=56
Reply from 74.125.71.99: bytes=32 time=503ms TTL=56
Reply from 74.125.71.99: bytes=32 time=697ms TTL=56
Reply from 74.125.71.99: bytes=32 time=550ms TTL=56
Reply from 74.125.71.99: bytes=32 time=350ms TTL=56
Reply from 74.125.71.99: bytes=32 time=858ms TTL=56
Reply from 74.125.71.99: bytes=32 time=861ms TTL=56
Reply from 74.125.71.99: bytes=32 time=90ms TTL=56
Reply from 74.125.71.99: bytes=32 time=501ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=476ms TTL=56
Reply from 74.125.71.99: bytes=32 time=445ms TTL=56
Reply from 74.125.71.99: bytes=32 time=533ms TTL=56
Reply from 74.125.71.99: bytes=32 time=582ms TTL=56
Reply from 74.125.71.99: bytes=32 time=610ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 74.125.71.99: bytes=32 time=345ms TTL=56
Reply from 74.125.71.99: bytes=32 time=120ms TTL=56
Reply from 74.125.71.99: bytes=32 time=763ms TTL=56
Reply from 74.125.71.99: bytes=32 time=204ms TTL=56
Reply from 74.125.71.99: bytes=32 time=342ms TTL=56
Reply from 74.125.71.99: bytes=32 time=867ms TTL=56
Request timed out.
Reply from 74.125.71.99: bytes=32 time=377ms TTL=56
Reply from 74.125.71.99: bytes=32 time=321ms TTL=56
Request timed out.


sinusumpong na naman si bayan xD

pinagtataka ko lang eh bakit pag madaling araw almost perfect connection, halos walang RTO pero pag tanghali hanggang gabi ang sagwa ng connection. anong palusot kaya dito? halos araw-araw ganyan nalang lagi scenario, nakakasawa na.

Quote:
Takot ata sakin yung connection mo Anxious

takutin mo ulit :D

account #: 330-420-731
Back to top
 
jps001
Posted: Sunday, August 01, 2010 1:47:34 AM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
eto ang sinasabi ko na pag madaling araw eh smooth na smooth ang connection:

Reply from 74.125.71.104: bytes=32 time=47ms TTL=56
Reply from 74.125.71.104: bytes=32 time=49ms TTL=56
Reply from 74.125.71.104: bytes=32 time=41ms TTL=56
Reply from 74.125.71.104: bytes=32 time=162ms TTL=56
Reply from 74.125.71.104: bytes=32 time=49ms TTL=56
Reply from 74.125.71.104: bytes=32 time=43ms TTL=56
Reply from 74.125.71.104: bytes=32 time=44ms TTL=56
Reply from 74.125.71.104: bytes=32 time=60ms TTL=56
Reply from 74.125.71.104: bytes=32 time=43ms TTL=56
Reply from 74.125.71.104: bytes=32 time=45ms TTL=56
Reply from 74.125.71.104: bytes=32 time=42ms TTL=56
Reply from 74.125.71.104: bytes=32 time=42ms TTL=56
Reply from 74.125.71.104: bytes=32 time=50ms TTL=56
Reply from 74.125.71.104: bytes=32 time=43ms TTL=56
Reply from 74.125.71.104: bytes=32 time=48ms TTL=56
Reply from 74.125.71.104: bytes=32 time=43ms TTL=56
Reply from 74.125.71.104: bytes=32 time=50ms TTL=56
Reply from 74.125.71.104: bytes=32 time=44ms TTL=56
Reply from 74.125.71.104: bytes=32 time=44ms TTL=56
Reply from 74.125.71.104: bytes=32 time=44ms TTL=56
Reply from 74.125.71.104: bytes=32 time=45ms TTL=56
Reply from 74.125.71.104: bytes=32 time=60ms TTL=56
Reply from 74.125.71.104: bytes=32 time=46ms TTL=56
Reply from 74.125.71.104: bytes=32 time=50ms TTL=56
Reply from 74.125.71.104: bytes=32 time=51ms TTL=56
Reply from 74.125.71.104: bytes=32 time=51ms TTL=56
Reply from 74.125.71.104: bytes=32 time=43ms TTL=56
Reply from 74.125.71.104: bytes=32 time=75ms TTL=56
Reply from 74.125.71.104: bytes=32 time=45ms TTL=56
Reply from 74.125.71.104: bytes=32 time=44ms TTL=56
Reply from 74.125.71.104: bytes=32 time=42ms TTL=56
Reply from 74.125.71.104: bytes=32 time=48ms TTL=56
Reply from 74.125.71.104: bytes=32 time=48ms TTL=56
Reply from 74.125.71.104: bytes=32 time=47ms TTL=56
Reply from 74.125.71.104: bytes=32 time=55ms TTL=56
Reply from 74.125.71.104: bytes=32 time=46ms TTL=56
Reply from 74.125.71.104: bytes=32 time=43ms TTL=56
Reply from 74.125.71.104: bytes=32 time=46ms TTL=56
Reply from 74.125.71.104: bytes=32 time=44ms TTL=56
Reply from 74.125.71.104: bytes=32 time=161ms TTL=56
Reply from 74.125.71.104: bytes=32 time=42ms TTL=56
Reply from 74.125.71.104: bytes=32 time=48ms TTL=56
Reply from 74.125.71.104: bytes=32 time=46ms TTL=56
Reply from 74.125.71.104: bytes=32 time=42ms TTL=56

so, ano ba talaga pinag kaiba ng connection pag umaga at tuwing madaling araw? kita nyo naman difference diba...
Back to top
 
kulafu123
Posted: Sunday, August 01, 2010 2:47:49 AM
Rank: Advanced Member
Groups: Member

Joined: 7/3/2010
Posts: 127
Points: 381
Location: Quezon City
atleast sayo sir hindi nadi-dc? akin walang pinipiling oras grabe ang dc, tsambahan mka 1 hour or 2 hour na walang DC. ayoko lang talaga bitiwan si bayantel kasi isa to sa mga may magandang technical support service. sana lang tlga maayos na tong connection ko. almost 2 months nako nagtitiis e :)
Account # 303715703
Back to top
 
jps001
Posted: Sunday, August 01, 2010 9:51:14 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
kulafu123 wrote:
atleast sayo sir hindi nadi-dc? akin walang pinipiling oras grabe ang dc, tsambahan mka 1 hour or 2 hour na walang DC. ayoko lang talaga bitiwan si bayantel kasi isa to sa mga may magandang technical support service. sana lang tlga maayos na tong connection ko. almost 2 months nako nagtitiis e :)


hindi naman pero same experience din kasi paputol putol un transmission ng data kapag panay RTO tapos ang bagal pa ng net pag tuwing tanghali hanggang gabid'oh!


Back to top
 
Xentar
Posted: Sunday, August 01, 2010 10:01:59 PM
Rank: Advanced Member
Groups: Member

Joined: 10/20/2008
Posts: 348
Points: 856
Bro Pwede ka dito post ng Tracert Facebook,. baka same tayo problem
Back to top
 
jps001
Posted: Monday, August 02, 2010 6:06:14 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
Xentar wrote:
Bro Pwede ka dito post ng Tracert Facebook,. baka same tayo problem


Tracing route to facebook.com [69.63.189.16]
over a maximum of 30 hops:

1 13 ms 15 ms 13 ms lo1.pe2.leg.bayan.net.ph [202.78.96.58]
2 34 ms 22 ms 21 ms 121.96.0.218.bti.net.ph [121.96.0.218]
3 25 ms 24 ms 22 ms 121.96.0.218.bti.net.ph [121.96.0.218]
4 23 ms 28 ms 22 ms 121.96.1.105.BTI.NET.PH [121.96.1.105]
5 21 ms 23 ms 24 ms 7600-GW4.bti.net.ph [202.78.97.195]
6 216 ms * * facebook.com.any2ix.coresite.com [206.223.143.16
1]
7 289 ms 295 ms 290 ms xe-1-3-0.br01.dfw1.tfbnw.net [204.15.21.7]
8 330 ms 315 ms 346 ms ae1.br01.mia1.tfbnw.net [74.119.77.73]
9 332 ms 324 ms 321 ms xe-8-3-0.bb01.iad2.tfbnw.net [74.119.77.75]
10 316 ms 313 ms 321 ms ae1.dr01.ash2.tfbnw.net [74.119.76.77]
11 317 ms 318 ms 321 ms eth-18-1.csw01a.ash2.tfbnw.net [74.119.76.111]
12 317 ms 315 ms 316 ms www-11-01-ash2.facebook.com [69.63.189.16]

Trace complete.


ano ba to, pag tanghali hanggang mga 10PM ng gabi walang kwenta mag youtubeBrick wall


Back to top
 
Mikos
Posted: Tuesday, August 03, 2010 1:04:02 PM

Rank: Moderator
Groups: Member , Moderator

Joined: 3/27/2009
Posts: 9,989
Points: 18,085
Location: Sa Web (aka Cyberspace)
For surfing normal ang tracert readings mo. I said SURFING... Baka me mga mag react na naman diyan na di nagbabasa kung ano ang naipost.

jps001 wrote:
Xentar wrote:
Bro Pwede ka dito post ng Tracert Facebook,. baka same tayo problem


Tracing route to facebook.com [69.63.189.16]
over a maximum of 30 hops:

1 13 ms 15 ms 13 ms lo1.pe2.leg.bayan.net.ph [202.78.96.58]
2 34 ms 22 ms 21 ms 121.96.0.218.bti.net.ph [121.96.0.218]
3 25 ms 24 ms 22 ms 121.96.0.218.bti.net.ph [121.96.0.218]
4 23 ms 28 ms 22 ms 121.96.1.105.BTI.NET.PH [121.96.1.105]
5 21 ms 23 ms 24 ms 7600-GW4.bti.net.ph [202.78.97.195]
6 216 ms * * facebook.com.any2ix.coresite.com [206.223.143.16
1]
7 289 ms 295 ms 290 ms xe-1-3-0.br01.dfw1.tfbnw.net [204.15.21.7]
8 330 ms 315 ms 346 ms ae1.br01.mia1.tfbnw.net [74.119.77.73]
9 332 ms 324 ms 321 ms xe-8-3-0.bb01.iad2.tfbnw.net [74.119.77.75]
10 316 ms 313 ms 321 ms ae1.dr01.ash2.tfbnw.net [74.119.76.77]
11 317 ms 318 ms 321 ms eth-18-1.csw01a.ash2.tfbnw.net [74.119.76.111]
12 317 ms 315 ms 316 ms www-11-01-ash2.facebook.com [69.63.189.16]

Trace complete.


ano ba to, pag tanghali hanggang mga 10PM ng gabi walang kwenta mag youtubeBrick wall



FLAMERS shall be severely sanctioned!!!
Please lang MATINONG TANONG LANG SANA ANG ITANONG instead of NONSENSE ONES.


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.


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
Back to top
 
jps001
Posted: Tuesday, August 03, 2010 2:38:29 PM

Rank: Advanced Member
Groups: Member

Joined: 4/15/2008
Posts: 638
Points: 1,482
Mikos wrote:
For surfing normal ang tracert readings mo. I said SURFING... Baka me mga mag react na naman diyan na di nagbabasa kung ano ang naipost.

jps001 wrote:
Xentar wrote:
Bro Pwede ka dito post ng Tracert Facebook,. baka same tayo problem


Tracing route to facebook.com [69.63.189.16]
over a maximum of 30 hops:

1 13 ms 15 ms 13 ms lo1.pe2.leg.bayan.net.ph [202.78.96.58]
2 34 ms 22 ms 21 ms 121.96.0.218.bti.net.ph [121.96.0.218]
3 25 ms 24 ms 22 ms 121.96.0.218.bti.net.ph [121.96.0.218]
4 23 ms 28 ms 22 ms 121.96.1.105.BTI.NET.PH [121.96.1.105]
5 21 ms 23 ms 24 ms 7600-GW4.bti.net.ph [202.78.97.195]
6 216 ms * * facebook.com.any2ix.coresite.com [206.223.143.16
1]
7 289 ms 295 ms 290 ms xe-1-3-0.br01.dfw1.tfbnw.net [204.15.21.7]
8 330 ms 315 ms 346 ms ae1.br01.mia1.tfbnw.net [74.119.77.73]
9 332 ms 324 ms 321 ms xe-8-3-0.bb01.iad2.tfbnw.net [74.119.77.75]
10 316 ms 313 ms 321 ms ae1.dr01.ash2.tfbnw.net [74.119.76.77]
11 317 ms 318 ms 321 ms eth-18-1.csw01a.ash2.tfbnw.net [74.119.76.111]
12 317 ms 315 ms 316 ms www-11-01-ash2.facebook.com [69.63.189.16]

Trace complete.


ano ba to, pag tanghali hanggang mga 10PM ng gabi walang kwenta mag youtubeBrick wall


oo kasi gabi na yan ng kinuha ko^^

pag tanghali hanggang gabi pangit talaga Youtube experience ko Y_Y
Back to top
 
Users browsing this topic
Guest

2 pages: [1] 2

bayanFORUM » BayanTech Support » bayanDSL Support » Medyo Unstable after Basyang


Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Main Forum RSS : RSS

SoClean Theme Created by Jaben Cargman (Tiny Gecko)
Powered by Yet Another Forum.net version 1.9.1.2 (NET v2.0) - 9/27/2007
Copyright © 2003-2006 Yet Another Forum.net. All rights reserved.
This page was generated in 0.362 seconds.