Erm... Lots of routers down for me.

Question

Maulth 4 Junior Poster in Training

16 Years Ago

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Maulth>tracert 205.234.153.26

Tracing route to 26.153.234.205.hypernia.com [205.234.153.26]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     7 ms    12 ms     8 ms  10.229.254.254
  3     7 ms    12 ms     7 ms  222.5.124.24.cm.sunflower.com [24.124.5.222]
  4     8 ms     7 ms     8 ms  242.3.124.24.cm.sunflower.com [24.124.3.242]
  5     9 ms     9 ms    13 ms  wsip-70-166-230-173.ks.ks.cox.net [70.166.230.17
3]
  6     9 ms     9 ms     9 ms  70.183.66.245
  7     9 ms     9 ms    13 ms  70.183.71.61
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    47 ms    19 ms    20 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
 12    19 ms    19 ms    19 ms  68.105.30.34
 13    21 ms    20 ms    19 ms  ae0-40g.cr1.dfw1.us.nlayer.net [69.31.63.125]
 14    29 ms    29 ms    29 ms  xe-2-2-0.cr2.ord1.us.nlayer.net [69.22.142.2]
 15    30 ms    29 ms    29 ms  po6.ar2.ord1.us.scnet.net [69.31.111.6]
 16    30 ms    31 ms    31 ms  62.po2.ar2.ord6.us.scnet.net [75.102.3.230]
 17    35 ms    31 ms    39 ms  as36352.ge9-44.ar2.ord6.us.scnet.net [75.102.4.3
4]
 18    31 ms    32 ms    31 ms  ge-0-1.FZ146.core.chicago.colocrossing.com [75.1
02.34.250]
 19    32 ms    31 ms    32 ms  26.153.234.205.hypernia.com [205.234.153.26]

Trace complete.
----------------------------------------------------------------------------------------------

C:\Users\Maulth>tracert 69.147.227.162

Tracing route to mygamecp.hypernia.com [69.147.227.162]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     8 ms     7 ms     7 ms  10.229.254.254
  3     8 ms     7 ms    24 ms  222.5.124.24.cm.sunflower.com [24.124.5.222]
  4     7 ms     9 ms     7 ms  242.3.124.24.cm.sunflower.com [24.124.3.242]
  5     8 ms     9 ms     9 ms  wsip-70-166-230-173.ks.ks.cox.net [70.166.230.17
3]
  6    23 ms     9 ms    10 ms  70.183.66.245
  7     8 ms     9 ms    10 ms  70.183.71.61
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    19 ms    19 ms    20 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
 12    20 ms    19 ms    20 ms  68.105.30.34
 13    21 ms    20 ms    21 ms  ae0-40g.cr1.dfw1.us.nlayer.net [69.31.63.153]
 14    41 ms    30 ms    31 ms  xe-2-2-0.cr2.ord1.us.nlayer.net [69.22.142.2]
 15    30 ms    38 ms    30 ms  po2-30g.ar1.ord1.us.nlayer.net [69.31.111.138]
 16    31 ms    37 ms    31 ms  er01.chi01.ubiquityservers.com [69.31.111.66]
 17    32 ms    33 ms    31 ms  mygamecp.hypernia.com [69.147.227.162]

Trace complete.


----------------------------------------------------------------------------------------------

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Maulth>tracert yahoo.com

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

  1    <1 ms     1 ms    <1 ms  192.168.2.1
  2     9 ms     9 ms    19 ms  10.229.254.254
  3     7 ms     7 ms     7 ms  222.5.124.24.cm.sunflower.com [24.124.5.222]
  4   167 ms   366 ms    61 ms  242.3.124.24.cm.sunflower.com [24.124.3.242]
  5     8 ms    10 ms     8 ms  wsip-70-166-230-173.ks.ks.cox.net [70.166.230.17
3]
  6     7 ms     9 ms     9 ms  70.183.66.245
  7     8 ms     9 ms    13 ms  70.183.71.61
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    20 ms    19 ms    19 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
 12    20 ms    22 ms    24 ms  dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
 13    21 ms    24 ms    21 ms  langdspt010-ge0330.r2.la.cox.net [68.105.30.30]

 14    68 ms    63 ms   148 ms  as-1.pat2.pao.yahoo.com [216.115.101.130]
 15    64 ms    64 ms    67 ms  as-0.pat1.pao.yahoo.com [216.115.101.128]
 16    64 ms    64 ms    64 ms  ae-2.pat2.pao.yahoo.com [216.115.101.33]
 17    65 ms   133 ms    65 ms  ae1-p151.msr2.sp1.yahoo.com [216.115.107.79]
 18    66 ms    66 ms    64 ms  te-8-1.bas-a2.sp1.yahoo.com [209.131.32.19]
 19    64 ms    64 ms    66 ms  b1.www.vip.sp1.yahoo.com [209.131.36.159]

Trace complete.

I have complete IPv4 connectivity. I can ping all major websites, such as google, yahoo, and others. Is anyone else having these problems?

microsoft:windows-nt-2000-xp router-proxy-firewall

2 Contributors
2 Replies
348 Views
18 Hours Discussion Span
Latest Post 16 Years Ago Latest Post by sknake

Dani AI

Generated 9 Months Ago

A few quick, practical clarifications based on ’s traces and ’s reply.

Seeing several consecutive “ *” hops in a traceroute does not prove an outage. Many routers simply don’t generate or reply to the traceroute probe used (ICMP TTL-exceeded or the UDP probes traceroute sends), or they rate‑limit those responses. If later hops answer and the destination is reachable (as in the other traces), packets are being forwarded even though some intermediate devices won’t show up in diagnostics. Private addresses (10.x) early in the path are normal for carrier/internal segments and don't imply customer-side misconfiguration.

Useful diagnostic checks and why they help:

tracert -d target.name        # disable DNS lookups so names don't hide IPs
pathping -q 10 target.name   # combines route + per-hop packet-loss stats
tracert -w 2000 -h 30 target # increase timeout / max hops for flaky links
(use tcptraceroute/tracetcp or mtr from another host)  # shows TCP-based paths and continuous loss

Notes and interpretation guidance:

If pathping shows noticeable loss beginning at a single hop and continuing to the destination, that’s evidence of a real packet-loss problem and warrants an ISP trouble ticket (include timestamped pathping/traceroute output and destination IPs).
If only ICMP/UDP probes are blocked but TCP probes succeed (or application traffic works), it’s filtering for probes, not a service outage.
Asymmetric routing, MPLS, and load-based ICMP throttling can produce intermittent or per-protocol differences in traceroute—this is common.

Summary: ’s point is correct—timeouts alone aren’t proof the routers are “down.” The next step is to gather pathping/traceroute (no-DNS) and, if available, a TCP traceroute or a test from an alternate vantage point; persistent loss at an ISP hop is the usual reason to escalate.

All 2 Replies

sknake 1,622 Senior Poster

16 Years Ago

That doesn't mean anything. Some routers are configured to respond to traceroute and others are configured to deny it. If the routers were down you would not get any responses past that router. In one of your traceroutes you have 3 hops that do not respond then it starts responding again. So those 3 routers are working they are just not responding to your traceroute.

Reply to this topic

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

Maulth 4 Junior Poster in Training · Answer 1 · 2009-12-14T14:51:37+00:00

C:\Users\Maulth>tracert 198.32.245.53

Tracing route to torix.tge2-3.ar1.tor1.ca.nlayer.net [198.32.245.53]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     8 ms     7 ms     7 ms  10.229.254.254
  3    50 ms     7 ms     7 ms  222.5.124.24.cm.sunflower.com [24.124.5.222]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  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     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Wow. I can't believe that one. I am going to need someone to see if they can maybe do that last tracert. I'm located in Kansas, by the way. My friend in Canada is having relatively close to the same issue.

Erm... Lots of routers down for me.

Dani AI

Recommended Answers Collapse Answers

All 2 Replies

Recommended Answers