reachability troubles

Thu Jul 17 22:53:45 UTC 2003

Hello,
  Folks in Massachusetts connected to Verizon DSL are reporting problems 
getting to websites that I host that are connected via lightship.net.  
When I try to traceroute to the following Verizon router (130.81.9.225) 
that is supposed to pass the traffic I get stopped on qwest.net.  My 
servers are located in Kennebunk, ME.

  All my traffic gets interrupted at terrorist central ... er ...jfk when 
trying to traceroute back to my customer.

Curtis Maurand
President - Maine Line Systems

traceroute to 130.81.9.225 (130.81.9.225), 30 hops max, 38 byte packets
 1  rtr02-ssl-kenn.sslsales.com (216.204.154.1)  2.202 ms  1.516 ms  1.480 
ms
 2  bbr1065-pwmb.lightship.net (216.204.106.5)  8.699 ms 
bbr1069-pwmb.lightship.net (216.204.106.9)  8.930 ms 
bbr1065-pwmb.lightship.net (216.204.106.5)  10.846 ms
 3  bbr7142-mhb.lightship.net (216.204.47.142)  23.908 ms  12.661 ms  
12.442 ms
 4  500.POS2-1.GW3.BOS4.ALTER.NET (208.192.176.97)  14.231 ms  17.420 ms  
15.654 ms
 5  169.at-5-0-0.XR2.BOS4.ALTER.NET (152.63.17.22)  17.087 ms  14.253 ms  
15.888 ms
 6  0.so-4-0-0.XL2.BOS4.ALTER.NET (152.63.16.133)  14.546 ms  14.506 ms  
15.573
ms
 7  0.so-2-0-0.XL2.NYC9.ALTER.NET (152.63.21.74)  24.375 ms  22.124 ms  
21.916 ms
 8  POS7-0.BR1.NYC9.ALTER.NET (152.63.18.221)  26.878 ms  28.162 ms  
21.755 ms
 9  204.255.174.130 (204.255.174.130)  26.739 ms  22.516 ms  22.692 ms
10  ewr-core-01.inet.qwest.net (205.171.17.125)  22.751 ms  22.453 ms  
28.463 ms11  jfk-core-02.inet.qwest.net (205.171.8.246)  24.826 ms  28.636 
ms  25.750 ms
12  jfk-core-03.inet.qwest.net (205.171.230.10)  27.942 ms  25.981 ms  
30.746 ms13  jfk-edge-20.inet.qwest.net (205.171.230.17)  25.477 ms  
22.836 ms  24.374 ms 

It times out here.

-- 
--
Curtis Maurand
mailto:curtis at maurand.com
http://www.maurand.com