Quote:
	
	
		
			
				
					Originally Posted by  cavedude
					 
				 
				I haven't spoken with FNW yet, if it's hardware he would be the first to know. But, my traceroute times out a few hops before PEQ so that suggests it may be ISP related. 
			
		 | 
	
	
 Strange.  My traceroute times out on projecteq.net's IP and not the ISP.
	Code:
	Tracing route to projecteq.net [66.28.184.13]
over a maximum of 30 hops:
....
  6    99 ms    60 ms    66 ms  te2-2.mpd01.ord01.atlas.cogentco.com [154.54.6.18] 
  7    40 ms   105 ms    62 ms  te8-4.mpd01.mci01.atlas.cogentco.com [66.28.4.185] 
  8   175 ms   198 ms    60 ms  te4-4.mpd01.den01.atlas.cogentco.com [154.54.24.81] 
  9    50 ms    49 ms    49 ms  vl3802.na01.b000544-0.den01.atlas.cogentco.com [66.28.66.170] 
 10   175 ms   189 ms    50 ms  TelosOnline.demarc.cogentco.com [66.28.21.42] 
 11     *        *        *     Request timed out.
 12  
~ > tracert 66.28.184.12
Tracing route to 66.28.184.12 over a maximum of 30 hops
...
  6    38 ms    26 ms    37 ms  te7-8.mpd02.ord01.atlas.cogentco.com [154.54.6.182] 
  7    26 ms    26 ms    29 ms  te9-1.mpd01.ord01.atlas.cogentco.com [66.28.4.105] 
  8    53 ms    38 ms    46 ms  te2-4.mpd01.mci01.atlas.cogentco.com [154.54.2.233] 
  9    83 ms    64 ms    71 ms  te4-4.mpd01.den01.atlas.cogentco.com [154.54.24.81] 
 10    50 ms    55 ms    67 ms  vl3502.na01.b000544-0.den01.atlas.cogentco.com [66.28.66.166] 
 11    60 ms   120 ms    70 ms  TelosOnline.demarc.cogentco.com [66.28.21.42] 
 12    84 ms    96 ms    63 ms  66.28.184.12 
Trace complete.
 I could be wrong, but this kind of suggest that its a problem with the box. Might just need to be rebooted.