public
join:2002-01-19
Santa Clara, CA
 ·DSL EXTREME
| Bad day at SBC
Outages, Santa Clara |
The first outage is explained by
Event Date: Wednesday, April 05, 2006
posted by Support Team on 4/5/2006 8:56:29 AM
Some SBC DSL customers in Northern California may experience trouble connecting to the Internet. Engineers are working to resolve the issue. ETA 30 minutes.
RESOLVED @ Apr 5 2006 9:17AM PST
but evidently it was not completely resolved. | |
|
 
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| Re: Bad day at SBC You might want to turn on the packet loss % for each hop, it's not possible to tell where the packet loss is occuring screen shot. Could be on the SBC network, or your particular line, etc. Tough to say...
--
The question isn't "what are we going to do," the question is "what aren't we going to do?" - Ferris | |
|
 | public
join:2002-01-19
Santa Clara, CA
·DSL EXTREME
| Re: Bad day at SBC said by deblin  :You might want to turn on the packet loss % for each hop, it's not possible to tell where the packet loss is occuring screen shot. Could be on the SBC network, or your particular line, etc. Tough to say... 100% loss in the red areas from hop 2.
PL is turned on. | |
|
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV | Well then you might want to change your "Statistics - Samples to include:" to ALL. That way when you run long duration ping tests, you won't effectively throw away all, but the last 10 data points from your packet loss statistics. | |
|
| public
join:2002-01-19
Santa Clara, CA
·DSL EXTREME
| Re: Bad day at SBC said by d_l :Well then you might want to change your "Statistics - Samples to include:" to ALL. That way when you run long duration ping tests, you won't effectively throw away all, but the last 10 data points from your packet loss statistics. Yes you are absolutely right. The link is normally reliable, and extended "red" is rare.
The problem seems to have been corrected for now. | |
|
| |
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV
| Re: Bad day at SBC Many people fail to set up PingPlotter with "Statistics - Samples to include:" to ALL before they do extended duration ping tests and don't realize how much information they lose in the upper statistical summaries even though the basal timeline graph will show all the packet loss events. Sometimes I think PingPlotter should be shipped with ALL as the default setting.  | |
|
|
|
|
