Unreachable sites

A few days ago, I couldn't reach ieee-denver.org from my office in Denver, and today I can't reach businessinsider.com. Here's the traceroute:

Richards-MacBook-Pro:~ Richard$ traceroute businessinsider.com

traceroute to businessinsider.com (64.27.101.155), 64 hops max, 52 byte packets

1 10.1.10.1 (10.1.10.1) 4.480 ms 6.678 ms 9.055 ms

2 67.177.216.1 (67.177.216.1) 54.558 ms 48.352 ms 19.502 ms

3 xe-9-0-0-0-sur03.wheatridge.co.denver.comcast.net (68.85.107.5) 20.240 ms 17.107 ms 10.523 ms

4 ae-10-0-sur02.wheatridge.co.denver.comcast.net (162.151.51.42) 9.985 ms 14.296 ms 15.308 ms

5 ae-30-0-ar01.aurora.co.denver.comcast.net (162.151.51.17) 20.982 ms 25.100 ms 13.193 ms

6 he-0-5-0-4-cr02.denver.co.ibone.comcast.net (68.86.95.205) 21.928 ms

he-0-5-0-6-cr02.denver.co.ibone.comcast.net (68.86.93.153) 29.906 ms

he-0-5-0-5-cr02.denver.co.ibone.comcast.net (68.86.95.201) 16.343 ms

7 ae14.edge3.denver1.level3.net (4.68.127.129) 19.806 ms 28.679 ms 19.678 ms

8 ae-2-70.ear1.washington39.level3.net (4.69.149.86) 56.569 ms

ae-3-80.ear1.washington39.level3.net (4.69.149.150) 94.051 ms

ae-2-70.ear1.washington39.level3.net (4.69.149.86) 85.911 ms

9 * * ae-2-70.ear1.washington39.level3.net (4.69.149.86) 83.408 ms

10 datapipe-in.ear1.washington39.level3.net (4.15.136.14) 69.911 ms 57.076 ms 72.740 ms

11 te1-3.border2.iad.datapipe.net (64.27.127.149) 53.201 ms 56.844 ms 62.252 ms

12 te1-3.border2.iad.datapipe.net (64.27.127.149) 62.973 ms 63.832 ms 70.125 ms

13 te1-3.border2.iad.datapipe.net (64.27.127.149) 68.507 ms 70.913 ms 69.859 ms

14 te1-3.border2.iad.datapipe.net (64.27.127.149) 62.505 ms 67.013 ms 69.626 ms

15 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.963 ms 70.334 ms 59.334 ms

16 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.515 ms 59.437 ms 59.968 ms

17 te1-3.border2.iad.datapipe.net (64.27.127.149) 65.703 ms 63.708 ms 69.807 ms

18 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.999 ms 69.194 ms 62.837 ms

19 te1-3.border2.iad.datapipe.net (64.27.127.149) 67.088 ms 69.213 ms 150.085 ms

20 te1-3.border2.iad.datapipe.net (64.27.127.149) 140.136 ms 148.884 ms 75.802 ms

21 te1-3.border2.iad.datapipe.net (64.27.127.149) 64.780 ms 69.219 ms 59.620 ms

22 te1-3.border2.iad.datapipe.net (64.27.127.149) 129.869 ms 58.768 ms 62.745 ms

23 te1-3.border2.iad.datapipe.net (64.27.127.149) 57.975 ms 54.220 ms 64.746 ms

24 te1-3.border2.iad.datapipe.net (64.27.127.149) 60.528 ms 68.828 ms 69.521 ms

25 te1-3.border2.iad.datapipe.net (64.27.127.149) 69.336 ms 80.840 ms 55.665 ms

26 te1-3.border2.iad.datapipe.net (64.27.127.149) 63.475 ms 67.647 ms 56.596 ms

27 te1-3.border2.iad.datapipe.net (64.27.127.149) 54.301 ms 70.537 ms 69.537 ms

28 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.510 ms 64.079 ms 65.593 ms

29 te1-3.border2.iad.datapipe.net (64.27.127.149) 70.936 ms 58.538 ms 58.145 ms

30 te1-3.border2.iad.datapipe.net (64.27.127.149) 60.161 ms 85.743 ms 123.795 ms

31 te1-3.border2.iad.datapipe.net (64.27.127.149) 77.753 ms 72.501 ms 70.676 ms

32 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.743 ms 68.924 ms 69.845 ms

33 te1-3.border2.iad.datapipe.net (64.27.127.149) 70.403 ms 62.681 ms 56.525 ms

34 te1-3.border2.iad.datapipe.net (64.27.127.149) 69.757 ms 69.287 ms 59.674 ms

35 te1-3.border2.iad.datapipe.net (64.27.127.149) 61.466 ms 67.931 ms 69.789 ms

36 te1-3.border2.iad.datapipe.net (64.27.127.149) 70.323 ms 62.587 ms 63.596 ms

37 te1-3.border2.iad.datapipe.net (64.27.127.149) 62.670 ms 79.424 ms 62.921 ms

38 te1-3.border2.iad.datapipe.net (64.27.127.149) 60.031 ms 56.131 ms 65.641 ms

39 te1-3.border2.iad.datapipe.net (64.27.127.149) 62.542 ms 61.718 ms 69.169 ms

40 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.139 ms 59.339 ms 56.032 ms

41 te1-3.border2.iad.datapipe.net (64.27.127.149) 72.104 ms 61.823 ms 69.877 ms

42 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.861 ms 59.478 ms 66.124 ms

43 te1-3.border2.iad.datapipe.net (64.27.127.149) 63.769 ms 69.792 ms 69.240 ms

44 te1-3.border2.iad.datapipe.net (64.27.127.149) 72.958 ms 57.073 ms 59.697 ms

45 te1-3.border2.iad.datapipe.net (64.27.127.149) 70.031 ms 69.080 ms 69.706 ms

46 te1-3.border2.iad.datapipe.net (64.27.127.149) 64.060 ms 61.196 ms 65.519 ms

47 te1-3.border2.iad.datapipe.net (64.27.127.149) 58.260 ms 69.155 ms 70.193 ms

48 te1-3.border2.iad.datapipe.net (64.27.127.149) 71.222 ms 67.969 ms 182.670 ms

49 te1-3.border2.iad.datapipe.net (64.27.127.149) 74.056 ms 72.270 ms 70.418 ms

50 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.735 ms 71.502 ms 57.388 ms

51 te1-3.border2.iad.datapipe.net (64.27.127.149) 55.857 ms 64.006 ms 58.993 ms

52 te1-3.border2.iad.datapipe.net (64.27.127.149) 60.580 ms 64.417 ms 65.043 ms

53 te1-3.border2.iad.datapipe.net (64.27.127.149) 60.074 ms 66.073 ms 63.092 ms

54 te1-3.border2.iad.datapipe.net (64.27.127.149) 59.843 ms 59.733 ms 69.985 ms

55 te1-3.border2.iad.datapipe.net (64.27.127.149) 69.994 ms 101.685 ms 64.109 ms

56 te1-3.border2.iad.datapipe.net (64.27.127.149) 64.128 ms 68.933 ms 72.520 ms

57 te1-3.border2.iad.datapipe.net (64.27.127.149) 57.486 ms 57.747 ms 61.572 ms

58 te1-3.border2.iad.datapipe.net (64.27.127.149) 69.680 ms 69.374 ms 62.532 ms

59 te1-3.border2.iad.datapipe.net (64.27.127.149) 92.941 ms 74.070 ms 60.113 ms

60 te1-3.border2.iad.datapipe.net (64.27.127.149) 79.640 ms 189.356 ms 70.443 ms

61 te1-3.border2.iad.datapipe.net (64.27.127.149) 69.721 ms 160.190 ms 59.249 ms

62 te1-3.border2.iad.datapipe.net (64.27.127.149) 70.077 ms 65.748 ms 63.401 ms

63 te1-3.border2.iad.datapipe.net (64.27.127.149) 70.460 ms 58.914 ms 58.111 ms

64 te1-3.border2.iad.datapipe.net (64.27.127.149) 111.608 ms 59.111 ms 70.352 ms

Richards-MacBook-Pro:~ Richard$

I have these problems all the time in Denver, but I never had such issues in California.

Responses

train_wreck

Gold Problem solver

•

610 Messages

10 years ago

Judging from the trace, this appears to be a problem coming into "datapipe.net", a hosting provider. As you can see from your posted trace, the packets get stopped at the Datapipe device with address 64.27.127.149, looping until the TTL expires. Either way, I do not THINK this would be a Comcast issue. I've posted a trace to "businessinsider.com" below, with a resolved IP that is the same as the one you got. It is loading fine for me.

PS C:\Windows\system32> tracert businessinsider.com

Tracing route to businessinsider.com [64.27.101.155]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  pLAN9-Gateway.pLAN9.site [172.16.16.1]
  2    19 ms    23 ms    19 ms  c-76-123-194-1.hsd1.tn.comcast.net [76.123.194.1]
  3     8 ms     8 ms     9 ms  xe-11-2-0-sur01.ruralhillrd.tn.nash.comcast.net [68.85.50.193]
  4     9 ms    11 ms    15 ms  xe-5-1-11-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.57]
  5    27 ms    16 ms    19 ms  he-1-1-0-5-cr02.56marietta.ga.ibone.comcast.net [68.86.90.101]
  6    20 ms    19 ms    27 ms  be-11214-cr01.56marietta.ga.ibone.comcast.net [68.86.85.165]
  7    17 ms    26 ms    23 ms  23.30.207.98
  8    31 ms    31 ms    30 ms  ae-2-70.ear1.Washington39.Level3.net [4.69.149.86]
  9    31 ms    30 ms    31 ms  ae-2-70.ear1.Washington39.Level3.net [4.69.149.86]
 10    30 ms    29 ms    30 ms  DATAPIPE-IN.ear1.Washington39.Level3.net [4.15.136.14]
 11    39 ms    38 ms    39 ms  te2-1.core1.iad.datapipe.net [64.27.83.64]
 12    39 ms    38 ms    38 ms  te3-6.core1.smq.datapipe.net [64.27.83.57]
 13    39 ms    39 ms    39 ms  64.27.83.97
 14    37 ms    38 ms    38 ms  64.27.101.155

Trace complete.

0

Connectivity

RichardBennett

Unreachable sites

train_wreck