Internet Flatulence

**Vin DSL** · 01-19-2007, 09:38 PM

Hey, did anybody notice that the web just had a major fart, or is it localized to my neck of the woods?

I'm getting timeouts from all over the world...

**Vin DSL** · 01-19-2007, 11:06 PM

Oops!

Code:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>ping yahoo.com

Pinging yahoo.com [66.94.234.13] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 66.94.234.13:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms

C:\>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  10.0.0.1
  2    45 ms    45 ms    45 ms
  3    45 ms    46 ms    45 ms
  4    46 ms    46 ms    46 ms  phv-edge-02.inet.qwest.net [72.164.12.9]
  5    46 ms    52 ms    46 ms  phx-core-02.inet.qwest.net [205.171.129.125]
  6    65 ms    64 ms    65 ms  svl-core-02.inet.qwest.net [67.14.12.10]
  7    65 ms    65 ms    65 ms  pax-brdr-02.inet.qwest.net [205.171.205.30]
  8    65 ms    65 ms    65 ms  if-1-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.149]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *

Looks like 'we' got a bad blade, in the next state over...

**Vin DSL** · 01-19-2007, 11:14 PM

Correction... Montreal...

Damn puddin' heads!

**Spathiphyllum** · 01-19-2007, 11:50 PM

I hadn't noticed it but it looks like there had been an interruption of sorts. It's back to normal now in NA (mid 80's), but the overall world indices look rather poor at the moment... unusually low comprehensive averages.

**Vin DSL** · 01-19-2007, 11:52 PM

Looks like 'my buddies' right here!

I guess it is Cali...

Heh! Look at that packet loss in your link!!!

I knew it farted...

Dude, that's a little scary, you know? I need to get a life!

**Spathiphyllum** · 01-20-2007, 12:54 AM

Originally Posted by Vin DSL

Heh! Look at that packet loss in your link!!!

I knew it farted...

I'm not sure if I'm directly or indirectly affected by that Dallas router. However, I've had an ongoing issue with a node (or series of nodes) on my ISP's branch for several months now. I don't know enough to know if it's a trio of balance loaded switches or a series of poorly configured ones. Whatever the case, each one regularly times out 66% of the time. Technically, packet loss is not happening. Actually, it's a frustrating bottleneck that cramps my surfing style. RoadRunner's acquisition of Comcast's network apparently didn't include fixing that Dallas intersection.

**Vin DSL** · 01-21-2007, 01:05 AM

Here we go again!

Same time, same channel...

**Vin DSL** · 01-21-2007, 01:08 AM

Sigh...

Code:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  10.0.0.1
  2    45 ms    45 ms    45 ms
  3    45 ms    45 ms    45 ms  
  4    45 ms    45 ms    46 ms  phv-edge-02.inet.qwest.net [72.164.12.9]
  5    69 ms    45 ms    46 ms  phx-core-02.inet.qwest.net [205.171.129.125]
  6    64 ms    64 ms    69 ms  svl-core-02.inet.qwest.net [67.14.12.10]
  7    64 ms    64 ms    64 ms  pax-brdr-02.inet.qwest.net [205.171.205.30]
  8    64 ms    64 ms    64 ms  if-1-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.149]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *

**CFusion** · 01-21-2007, 06:36 AM

I think you have a leak here!

**Vin DSL** · 01-21-2007, 11:29 AM

Yeah, it's a weird one!

It's happened the last two nights @ 11:00 PM local -- same router -- I assume in Cali. Then, sometime during the next few hours, it starts working again.

Maybe someone is attacking the blade. I've heard of that happening before...

If it happens again tonight, I'm calling the operations center at my ISP. Just happen to have their number, and they always love to hear from me.

Hello?

Hi, I'm a DSL customer, and I have...

What? Who is this?

I'm a DSL customer.

Oh, okay??!?!

And, I'm having a problem with my account...

I see. Okay. Um... And, how did you get this number?

Et cetera...

**Vin DSL** · 01-21-2007, 11:33 AM

Oops! Spoke too soon...

Code:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>tracert yahoo.com

Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  10.0.0.1
  2    45 ms    44 ms    44 ms
  3    49 ms    45 ms    44 ms  
  4    44 ms    45 ms    62 ms  phv-edge-02.inet.qwest.net [72.164.12.9]
  5    45 ms    45 ms    45 ms  phx-core-02.inet.qwest.net [205.171.129.125]
  6    64 ms    64 ms    63 ms  svl-core-01.inet.qwest.net [67.14.12.58]
  7    65 ms    64 ms    65 ms  pax-brdr-02.inet.qwest.net [205.171.214.38]
  8    64 ms    63 ms    64 ms  if-1-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.149]
  9    65 ms    67 ms    65 ms  if-1-1.mcore4.PDI-PaloAlto.Teleglobe.net [207.45.196.78]
 10   125 ms   124 ms   124 ms  if-4-0.mcore4.NQT-NewYork.teleglobe.net [216.6.86.14]
 11   124 ms   124 ms   124 ms  if-5-0.mcore3.NYY-NewYork.teleglobe.net [216.6.87.54]
 12   125 ms   124 ms   124 ms  if-6-0-0.core4.AEQ-Ashburn.teleglobe.net [216.6.81.14]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *

**Vin DSL** · 01-24-2007, 08:51 AM

Grrrr...

I've noticed things are slow this morning, here in Atlanta.

And, to compound the situation, guess what?

Code:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  10.0.0.1
  2    44 ms    44 ms    43 ms  
  3    44 ms    45 ms    45 ms  
  4    43 ms    45 ms    46 ms  phv-edge-02.inet.qwest.net [72.164.12.9]
  5    44 ms    44 ms    44 ms  phx-core-02.inet.qwest.net [205.171.129.125]
  6    63 ms    64 ms    63 ms  svl-core-02.inet.qwest.net [67.14.12.10]
  7    63 ms    63 ms    64 ms  pax-brdr-02.inet.qwest.net [205.171.205.30]
  8    71 ms    63 ms    62 ms  if-1-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.149]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *

**Pawel Kowalski** · 01-24-2007, 09:37 AM

Sounds like you need a new ISP.

**Vin DSL** · 01-25-2007, 01:13 AM

Here's the thing...

Code:

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>tracert yahoo.com

Tracing route to yahoo.com [66.94.234.13]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  10.0.0.1
  2    45 ms    44 ms    44 ms  
  3    43 ms    44 ms    44 ms  
  4    45 ms    45 ms    44 ms  phv-edge-02.inet.qwest.net [72.164.12.9]
  5    45 ms    45 ms    45 ms  phx-core-02.inet.qwest.net [205.171.129.125]
  6    64 ms    64 ms    63 ms  svl-core-02.inet.qwest.net [67.14.12.10]
  7    64 ms    64 ms    65 ms  pax-brdr-02.inet.qwest.net [205.171.205.30]
  8    63 ms    64 ms    64 ms  if-1-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.149]
  9    67 ms    68 ms    67 ms  ix-6-2.core3.PDI-PaloAlto.Teleglobe.net [207.45.213.130]
 10    67 ms    67 ms    72 ms  ge-4-0-0-p450.msr2.scd.yahoo.com [216.115.106.205]
 11    68 ms    68 ms    68 ms  ten-2-3-bas1.scd.yahoo.com [66.218.82.221]
 12    67 ms    67 ms    67 ms  w2.rc.vip.scd.yahoo.com [66.94.234.13]

Trace complete.

That's pretty damn good for DSL! And, I get a dial-up account for *free*!

It's kinda like this place, in a way...

Nobody can be perfect all the time, yes?

**Pawel Kowalski** · 01-25-2007, 11:34 AM

Not bad. Compare that to the qwest DSL line here at work:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 42 ms 49 ms 42 ms albq-dsl-gw02-194.albq.qwe

4 42 ms 41 ms 41 ms albq-agw1.inet.qwest.net [
5 42 ms 42 ms 41 ms abq-core-01.inet.qwest.net
6 43 ms 42 ms 97 ms abq-core-02.inet.qwest.net
7 52 ms 52 ms 52 ms dvr-core-01.inet.qwest.net
8 77 ms 77 ms 76 ms svl-core-02.inet.qwest.net
9 77 ms 78 ms 77 ms pax-brdr-02.inet.qwest.net
10 78 ms 77 ms 77 ms if-1-1.core3.PDI-PaloAlto.
213.133]
11 78 ms 77 ms 77 ms ix-5-0.core3.PDI-PaloAlto.
196.90]
12 78 ms 78 ms 78 ms ge-3-0-0-p251.msr2.scd.yah
3]
13 155 ms 81 ms 79 ms ten-2-3-bas1.scd.yahoo.com
14 79 ms 79 ms 79 ms yahoo.com [66.94.234.13]

When you take in to account my work network it gets the same amount of hops but your ping is much better than ours. I prefer comcast cable at home, I just always need a special to be able to afford it

.

LinkBack

Thread Tools

Display

Internet Flatulence

Bookmarks

Bookmarks

Posting Permissions