Now I suppose today's post isn't too technical. But, it made me chuckle. And, it's from Scott C. Reynolds. So, here goes ...

I've said before that Verizon is like "Joe's House O' Telecom" with a large customer base.  Today proves it.  Our T1 in our New York office went down and we lost connectivity, and our Florida office was basically screwed for the afternoon.  Verizon reported that they were having a router problem "a few hops away"....well, when they still hadn't solved it 6 hours later, we decided to run a test:

Tracing route to [IPADDRESS] over a maximum of 30 hops

  1     7 ms     1 ms     1 ms  192.168.1.1
  2    28 ms     8 ms    12 ms  10.4.0.1
  3    12 ms     9 ms    31 ms  rtr-gancr-hsi-2.ncf.coxexpress.com [24.136.46.101]
  4    16 ms    17 ms    18 ms  68.1.15.25
  5    24 ms    22 ms    32 ms  lkhnbbrc01-pos0203.rd.at.cox.net [68.1.0.36]
  6    21 ms    42 ms    35 ms  so-1-2-0-0.gar2.Atlanta1.Level3.net [65.59.222.5]
  7    22 ms    26 ms    21 ms  so-3-3-0.bbr1.Atlanta1.Level3.net [4.68.96.13]
  8    41 ms    55 ms    38 ms  as-1-0.bbr2.NewYork1.Level3.net [64.159.1.85]
  9    39 ms    39 ms    41 ms  ge-11-0-56.ipcolo5.NewYork1.Level3.net [4.68.97.175]
 10    46 ms    38 ms    54 ms  unknown.Level3.net [209.246.126.10]
 11    53 ms    38 ms    39 ms  207.188.106.254
 12    56 ms    38 ms    37 ms  207.188.106.253
 13    38 ms    39 ms    47 ms  207.188.106.254
 14    40 ms    42 ms    51 ms  207.188.106.253
 15    42 ms    40 ms    42 ms  207.188.106.254
 16    41 ms    40 ms    42 ms  207.188.106.253
 17    47 ms    45 ms    66 ms  207.188.106.254
 18    42 ms    47 ms    39 ms  207.188.106.253
 19    50 ms    40 ms    39 ms  207.188.106.254
 20    39 ms    44 ms    43 ms  207.188.106.253
 21    39 ms    40 ms    42 ms  207.188.106.254
 22    45 ms    46 ms    40 ms  207.188.106.253
 23    44 ms    41 ms    39 ms  207.188.106.254
 24    49 ms    42 ms    39 ms  207.188.106.253
 25    42 ms    44 ms    40 ms  207.188.106.254
 26    50 ms    54 ms    50 ms  207.188.106.253
 27    42 ms    41 ms    45 ms  207.188.106.254
 28    46 ms     *       42 ms  207.188.106.253
 29    39 ms    40 ms    41 ms  207.188.106.254
 30    63 ms    41 ms    41 ms  207.188.106.253

Trace complete.

Circular dependency much?  Basically the request gets all the way to the master subnet and then two routers play pong with the packets.  Nicely done Verizon!  King of all telecoms!  I mean...I can't stand Sprint, but I'd go off the grid before I personally used Verizon.

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!