shahzadmasih,
Depending on the nature of the question you may have to open a trouble ticket. However, if you PM me your request I can help you determine what path you need to take to obtain this information.

I have a problem to send e-mail to Yahoo! from 67.15.54.2:

root@linux [/var/log]# telnet mx1.mail.yahoo.com 25
Trying 4.79.181.168...
Connected to mta-v8.level3.mail.vip.mud.yahoo.com (4.79.181.168).
Escape character is '^]'.
451 Message temporarily deferred - 4.16.50
Connection closed by foreign host.

When I try from another of my servers I get this response:

root@linux [/var/log]# telnet mx1.mail.yahoo.com 25
Trying 67.28.113.19...
Connected to mta-v3.level3.mail.vip.re2.yahoo.com (67.28.113.19).
Escape character is '^]'.
220 mta240.mail.re2.yahoo.com ESMTP YSmtp service ready

Just wondering what I cand do to solve the issue, the server is not blacklisted on any of the major Blocking Lists.

A traceroute from 67.15.54.2 to mx1.mail.yahoo.com :

root@linux [~]# traceroute mx1.mail.yahoo.com
traceroute: Warning: mx1.mail.yahoo.com has multiple addresses; using 4.79.181.168
traceroute to mx1.mail.yahoo.com (4.79.181.168), 30 hops max, 38 byte packets
1 ev1s-67-15-54-1.ev1servers.net (67.15.54.1) 0.399 ms 0.548 ms 0.394 ms
2 gphou-66-98-241-3.ev1.net (66.98.241.3) 0.395 ms 0.381 ms 0.398 ms
3 gphou-66-98-240-10.ev1.net (66.98.240.10) 0.628 ms 0.613 ms 0.391 ms
4 g0-3.na21.b015619-0.iah01.atlas.cogentco.com (38.112.25.21) 1.047 ms 1.026 ms 1.243 ms
5 g4-0-0.core01.iah01.atlas.cogentco.com (38.112.36.49) 20.028 ms 2.459 ms 44.635 ms
6 p5-0.core01.dfw01.atlas.cogentco.com (66.28.4.97) 6.534 ms 6.434 ms 6.552 ms
7 p1-0.core01.dfw03.atlas.cogentco.com (154.54.2.22) 6.479 ms 6.646 ms 6.456 ms
8 t4-4.mpd01.dfw03.atlas.cogentco.com (154.54.6.66) 24.152 ms 20.320 ms 6.933 ms
9 yahoo.dfw03.atlas.cogentco.com (154.54.12.62) 6.855 ms 6.673 ms 6.794 ms
10 ge-0-1-0-p110.msr2.mud.yahoo.com (216.115.104.101) 7.730 ms ge-1-1-0-p100.msr1.mud.yahoo.com (216.115.104.105) 8.005 ms ge-0-1-0-p110.msr2.mud.yahoo.com (216.115.104.101) 7.677 ms
11 ge-8-1.bas-g2.mud.yahoo.com (68.142.193.215) 7.833 ms 7.511 ms ge-9-1.bas-g1.mud.yahoo.com (68.142.193.221) 7.730 ms
12 * * *
13 * * *
14 * * *
15 * * *

elenlace,
Yahoo is, most likely, filtering ICMP/UDP packets to prevent DDoS attacks against their servers. This is why the traceroute is dying. You should open a trouble ticket to get further assistance with this matter.

icrosoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:Documents and Settingseggnog>tracert forums.cpfc.org

Tracing route to forums.cpfc.org [67.15.181.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SpeedTouch.lan [10.0.0.138]
2 22 ms 26 ms 23 ms anchor-hg-3-l100.router.demon.net [194.159.161.34]
3 26 ms 23 ms 25 ms anchor-access-4-v155.router.demon.net [194.159.161.161]
4 22 ms 22 ms 31 ms anchor-inside-3-g5-0-2.router.demon.net [194.159.161.90]
5 23 ms 25 ms 30 ms anchor-border-2-g1-0-0.router.demon.net [194.70.98.14]
6 21 ms 24 ms 22 ms 195.66.226.185
7 22 ms 33 ms 31 ms g9-0-0.core01.lon01.atlas.cogentco.com [130.117.1.77]
8 110 ms 113 ms 98 ms p3-0.core02.jfk02.atlas.cogentco.com [66.28.4.189]
9 97 ms 109 ms 95 ms p15-0.core01.jfk02.atlas.cogentco.com [66.28.4.13]
10 121 ms 116 ms 121 ms p9-0.core01.atl01.atlas.cogentco.com [154.54.5.98]
11 144 ms 164 ms 165 ms p10-0.core01.iah01.atlas.cogentco.com [154.54.5.89]
12 147 ms 147 ms 171 ms g0-1.na21.b015619-0.iah01.atlas.cogentco.com [66.28.64.62]
13 * 154 ms 154 ms everyones_internet_2.demarc.cogentco.com [38.112.25.158]
14 190 ms 163 ms * gphou-66-98-241-29.ev1.net [66.98.241.29]
15 * * * Request timed out.
16 * * * Request timed out.
17 * 189 ms * venus.cpfc.org [67.15.181.35]
18 * 181 ms * venus.cpfc.org [67.15.181.35]
19 157 ms * * venus.cpfc.org [67.15.181.35]
20 * 154 ms * venus.cpfc.org [67.15.181.35]
21 * * 155 ms venus.cpfc.org [67.15.181.35]

Trace complete.

C:Documents and Settingseggnog>

Dave#,
I am unable to reproduce the same results:
(From JellyBelly Networks (AS2529) to provided IP address (server is blocking UDP packets)):
1 finch-core-1.router.jellybaby.net (194.159.247.129) 0.769 ms 0.699 ms 0.667 ms
2 finch-service-1-13.router.demon.net (194.159.253.247) 10.875 ms 1.017 ms 0.991 ms
3 finch-backbone-11-162.router.demon.net (194.159.36.65) 3.218 ms 3.136 ms 3.745 ms
4 tele-backbone-11.router.demon.net (194.159.7.3) 9.043 ms 5.266 ms 4.931 ms
5 tele-inside-1-g3-0-0-s268.router.demon.net (194.70.98.225) 1.674 ms 2.484 ms 1.693 ms
6 tele-border-1-g4-0-0.router.demon.net (194.70.98.190) 2.015 ms 1.894 ms 1.848 ms
7 195.66.226.185 (195.66.226.185) 2.041 ms 2.149 ms 2.381 ms
8 g2-0-0.core02.lon01.atlas.cogentco.com (130.117.1.61) 2.346 ms 2.381 ms 2.342 ms
9 p9-0.core02.jfk02.atlas.cogentco.com (66.28.4.253) 75.437 ms 75.398 ms 75.314 ms
10 p15-0.core01.jfk02.atlas.cogentco.com (66.28.4.13) 73.244 ms 73.265 ms 73.220 ms
11 p9-0.core01.atl01.atlas.cogentco.com (154.54.5.98) 93.609 ms 103.534 ms 93.606 ms
12 p10-0.core01.iah01.atlas.cogentco.com (154.54.5.89) 125.018 ms 122.383 ms 122.060 ms
13 g0-3.na21.b015619-0.iah01.atlas.cogentco.com (38.112.35.238) 122.447 ms 123.488 ms 122.451 ms
14 38.112.25.22 (38.112.25.22) 120.758 ms 120.696 ms 120.753 ms
15 gphou-66-98-241-29.ev1.net (66.98.241.29) 121.384 ms 120.587 ms 120.794 ms
16 gphou-66-98-241-112.ev1.net (66.98.241.112) 119.319 ms 119.603 ms 119.462 ms
17 * * *
18 * * *


(From remote location to provided IP address using ICMP):
$ traceroute 67.15.181.35 -I
traceroute to 67.15.181.35 (67.15.181.35), 30 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 0.818 ms 0.978 ms 0.996 ms
2 gw.tvmax-fiber-1.hou.ygnition.net (24.219.200.1) 21.776 ms 11.347 ms 14.723 ms
3 s5-0-0.c1.hou.ygnition.net (24.219.192.249) 21.891 ms 13.580 ms 11.564 ms
4 64.132.191.93 (64.132.191.93) 14.580 ms 15.989 ms 11.732 ms
5 dist-02-ge-1-3-1-508.hsto.twtelecom.net (66.192.246.118) 11.416 ms 15.514 ms 17.047 ms
6 hagg-02-ge-3-3-0-504.hsto.twtelecom.net (66.192.246.125) 12.425 ms 13.189 ms 21.961 ms
7 216-110-27-98.static.twtelecom.net (216.110.27.98) 22.040 ms 16.221 ms 12.581 ms
8 gphou-66-98-241-28.ev1.net (66.98.241.28) 19.999 ms 14.603 ms 14.958 ms
9 gphou-66-98-241-112.ev1.net (66.98.241.112) 17.416 ms 13.643 ms 14.173 ms
10 venus.cpfc.org (67.15.181.35) 22.081 ms 24.077 ms 16.391 ms

Are you still experiencing this problem? If so, you should open a trouble ticket and provide the inbound/outbound traceroute as well as a source IP address so we can assist you in troubleshooting.

this is a tracert to ev1servers.net but I am seeing this same packet loss for a few hours now using the same route going through this "ntt.net" who I have never seen before in my local traces. packet loss is so bad I can't even ssh into my DC1 boxes. It's intermittent however. I managed to get the forum to popup for me after 30 minutes of trying. using pingplotter I am getting constant 30-70% packetloss on most of the hops that are the ntt.net

3 132 ms 148 ms 133 ms nas52.2ga1.Level3.net [209.247.21.99]
4 129 ms 127 ms 131 ms 4.69.4.2
5 130 ms 169 ms 133 ms ae-1-53.bbr1.Atlanta1.Level3.net [4.68.103.65]
6 145 ms 143 ms 140 ms ae-0-0.bbr2.Washington1.Level3.net [4.68.128.210
]
7 149 ms 179 ms 158 ms ae-23-54.car3.Washington1.Level3.net [4.68.121.1
12]
8 145 ms 145 ms 143 ms xe-1-4.r05.asbnva01.us.bb.gin.ntt.net [129.250.9
.113]
9 143 ms 160 ms 144 ms xe-2-2-0.r21.asbnva01.us.bb.gin.ntt.net [129.250
.2.86]
10 177 ms 177 ms 179 ms p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.25
0.5.24]
11 185 ms 223 ms 183 ms p64-1-0-0.r20.hstntx01.us.bb.gin.ntt.net [129.25
0.4.71]
12 188 ms 170 ms 169 ms xe-4-1.r03.hstntx01.us.bb.gin.ntt.net [129.250.2
.229]
13 169 ms 189 ms 170 ms ge-5.ev1.hstntx01.us.bb.gin.ntt.net [129.250.10.
146]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * *

just looked at the EV1 mrtg graphs and in the last hour or so there is a spike across several graphs in the green and a dip in the blue traffic on many of the graphs. Something is going on. It's not just me that's for sure.

rpmws,
We experienced a very large inbound attack at approx. 2:30am US CDT this morning. This caused some saturation on a couple of the backbones (including the backbone you take inbound). This was mitigated and connectivity restored to normal. Are you still experiencing problems with connectivity?

Chris ..I had 2 complaints about latency and packetloss today and I can't remember in 3-4 years ever getting any. One of those people is using DirecWay which is junk at best and they just got the thing so good luck to them. A bird could have flow by that flaky hunk of crap and knocked them out for an hour if it holds up to it's reputation.

However I did have another client complain a bit and their tracert is using the level3 in atlanta to the ntt links. I have been seeing constant 20-50% packetloss mysel;f on ping plotter all day. I haven't noticed too much noticable latency. I am still on a dial-up here ..but only had pop3 timeout once. I have never seen this ntt.net in my traces before now. It's always been savis of above.net. and I used to get in on 12 hops (3 are lan based here) now it's 16 - 18 hops. It's important to note I can't see any trace differences with my boxes at other nocs and in fact dc2 boxes haven't changed. Have you guys changes peering preference orders or something lately? I can't stand this ntt.net ..not sure who they are or who stuck them in there on me but it seems to ping 10ms faster for me ..but 129.250.2.86 is showing 20 - 50% packetloss in the loop on and off for me.. makes it "bursty" at best. any help you might can do for me would be great.

by the way ..its all the dc1 sites i see this route. and in fact dc2 boxes are now showing ntt.net routes and 129.250.2.86 is constantly dropping packets from here.

rpmws,
Ntt.net is Verio and so far they have been a very good provider. Are you using something simular to MTR/WinMTR (Matt's Traceroute) to watch for loss/latency? If so, this can cause issues as it continuously polls all hops on the trace. The reason for the problem is that most providers have ICMP/UDP rate limits. The continuous polls can give false loss/latency readings due to excessive polling. However, I would like to investigate this more closely. It would be helpful if you could open a trouble ticket with inbound/outbound traces from targets experiencing problems. Also, please include source IP of the inbound traces to assist with troubleshooting.

from s*w*e*d*e*n and costa r*i*c*a


[66.98.226.164]
sobre un máximo de 30 saltos:

1 <10 ms <10 ms <10 ms ua-83-227-56-130.cust.bredbandsbolaget.se [83.22
7.56.130]
2 <10 ms <10 ms <10 ms ge2-2.dr2.vst1.se.bredband.com [195.54.115.129]

3 <10 ms <10 ms <10 ms ge0-0.cr2.vst1.se.bredband.com [195.54.119.5]
4 3 ms 3 ms 3 ms pos3-0.cr1.ore1.se.bredband.com [195.54.125.169]

5 3 ms 3 ms 3 ms pos11-0.cr2.ore1.se.bredband.com [195.54.125.222
]
6 9 ms 54 ms 200 ms pos12-0.cr1.sto1.se.bredband.com [195.54.117.17]

7 3 ms 3 ms 9 ms tenge9-1.br1.sto1.se.bredband.com [195.54.123.23
0]
8 3 ms 3 ms 3 ms netnod-ix-ge-a-sth-1500.cogent.com [194.68.123.1
55]
9 17 ms 17 ms 17 ms p15-2.core01.ham01.atlas.cogentco.com [130.117.0
.129]
10 30 ms 30 ms 30 ms p11-2.core01.fra03.atlas.cogentco.com [130.117.0
.165]
11 258 ms 211 ms 219 ms p15-0.core01.par02.atlas.cogentco.com [130.117.0
.18]
12 117 ms 117 ms 117 ms p12-0.core01.par01.atlas.cogentco.com [130.117.0
.117]
13 110 ms 110 ms 110 ms p14-0.core02.dca01.atlas.cogentco.com [66.28.4.2
06]
14 114 ms 114 ms 114 ms p15-0.core01.dca01.atlas.cogentco.com [66.28.4.2
1]
15 153 ms 153 ms 153 ms p3-0.core01.iah01.atlas.cogentco.com [66.28.4.90
]
16 * *

arnold,

This was most likely related to the following:
http://forums.ev1servers.net/showthread.php?t=64278

I see connectivity to the server from external sources:
$ traceroute -I -n 66.98.226.164
traceroute to 66.98.226.164 (66.98.226.164), 30 hops max, 38 byte packets
1 10.54.0.1 9.890 ms 11.156 ms 11.240 ms
2 24.28.96.153 18.658 ms 13.237 ms 15.616 ms
3 24.93.34.94 14.908 ms 18.257 ms 13.296 ms
4 72.179.205.1 25.261 ms 27.632 ms 27.842 ms
5 4.71.12.17 31.901 ms 4.79.180.81 25.547 ms 24.667 ms
6 4.68.122.47 23.062 ms 33.508 ms 34.286 ms
7 4.68.110.62 25.380 ms 24.558 ms 27.177 ms
8 129.250.4.69 34.330 ms 31.515 ms 31.184 ms
9 129.250.2.231 125.249 ms 39.236 ms 31.635 ms
10 129.250.10.66 32.404 ms 31.068 ms 32.600 ms
11 207.218.245.29 31.784 ms 33.015 ms 35.197 ms
12 207.218.245.109 31.656 ms 30.490 ms 30.088 ms
13 66.98.226.164 37.005 ms 41.068 ms 31.718 ms

Are you still experiencing connectivity problems?

Hi,
I'm able to reach all of the .com root name servers from my DC2 box, but not from my DC1 box. Four of them fail. Here are there IPs:

192.5.6.30
192.26.92.30
192.33.14.30
192.31.80.30

The traceroutes don't reveal much, so I've only attached one. Please see the ping report:

(From 216.127.92.0/23)


(From 67.15.156.0/23)


Traceroute to 192.5.6.30 from 216.127.92.0/23:


Traceroute to 192.5.6.30 from 67.15.156.0/23:

ScottPO,
These 4 IPs were blocked in our edges at the Dc1 datacenter. I have now removed the block and ensured no other gtld-servers were also blocked. Thank you for bringing this to our attention.

HI !

URGENT URGENT !

67.15.143.16 - 17 - 18 ... - 15.....
all these servers have lost connectivity with the gphou-66-98-241-29.ev1servers.net ROUTER .

what's going on ?

please respond.


edit edit :
ok solved ,
something was wrong with one of the core routers.....or switches ?!
maiby.
thanks admin for taking care of ev1 network.
very fast fix.

Source IP: 72.232.35.202
Destination IP: 216.127.72.126

Inbound Trace:
Tracing route to ns1.tuclick.com [216.127.72.126]
over a maximum of 30 hops:

1 2 ms 7 ms 7 ms 201.35.232.72.reverse.layeredtech.com [72.232.35.201]
2 5 ms <1 ms <1 ms 10.1.6.13
3 1 ms <1 ms <1 ms 216.39.79.217
4 <1 ms <1 ms <1 ms bhr2-po-2.fortworthda1.savvis.net [216.39.64.49]
5 1 ms 1 ms 1 ms dpr1-so-1-0-0.DallasEquinix.savvis.net [204.70.134.17]
6 28 ms 6 ms 2 ms dcr2-so-7-2-0.Dallas.savvis.net [204.70.193.214]
7 3 ms 1 ms 1 ms bcr1-so-0-0-0.Dallas.savvis.net [204.70.193.9]
8 6 ms 6 ms 5 ms iar1-so-0-0-0.Houston.savvis.net [208.172.131.78]
9 * * * Request timed out.
10 * * * Request timed out.


Outbound Trace:
traceroute to 72.232.35.202 (72.232.35.202), 30 hops max, 38 byte packets
1 216.127.72.1 0.479 ms 0.441 ms 0.217 ms
2 207.218.245.15 2.054 ms 1.069 ms 0.461 ms
3 207.218.223.2 0.584 ms 0.411 ms 0.547 ms
4 216.200.251.57 1.586 ms 1.465 ms 1.661 ms
5 64.125.31.62 1.343 ms 1.303 ms 1.375 ms
6 64.125.29.65 14.240 ms 14.175 ms 14.305 ms
7 64.125.27.50 14.329 ms 14.214 ms 14.378 ms
8 208.173.59.25 21.583 ms 20.783 ms 20.774 ms
9 204.70.193.237 20.906 ms 20.985 ms 208.172.75.109 21.329 ms
10 204.70.192.70 21.143 ms 204.70.194.178 20.775 ms 21.540 ms
11 204.70.192.49 20.811 ms 208.172.131.82 21.787 ms 204.70.192.49 20.872 ms
12 208.172.131.82 21.794 ms 216.39.64.3 22.461 ms 208.172.131.82 21.936 ms
13 216.39.81.34 22.208 ms 22.261 ms 216.39.64.3 22.434 ms
14 * 216.39.81.34 22.540 ms 22.189 ms
15 * * *
16 * * *


Source to Destination via. TCP:
telnet 216.127.72.126 80
Connecting To 216.127.72.126...Could not open connection to the host, on port 80: Connect failed

i think smoething is wrong with the interconnection with abovenet and ev1

please make some tests to these 2 routers

1ms 3ms 2ms [66.98.240.7] gphou-66-98-240-7.ev1servers.net
3ms 60ms 2ms [216.200.251.161] ge-6-0-1.mpr2.iah1.us.above.net



30 % packet loss becuse of this.

( last 40 minutes)

Source: 66.38.252.1
Destination: 67.15.80.76 (my server)

tracert 67.15.80.76

Tracing route to sun.bounceweb.com [67.15.80.76]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 142.67.6.161
2 <1 ms <1 ms <1 ms 142.67.0.12
3 <1 ms <1 ms <1 ms h66-38-252-254.gtconnect.net [66.38.252.254]
4 2 ms 2 ms 2 ms router-onramp.triversity.onramp.ca [204.225.92.4
5]
5 3 ms 3 ms 2 ms 216.138.255.83
6 187 ms 199 ms 199 ms 216.138.255.34
7 2 ms 2 ms 2 ms 216.138.255.70
8 3 ms 3 ms 2 ms 69.156.254.37
9 3 ms 2 ms 3 ms core1-toronto63_pos0-3.net.bell.ca [64.230.229.5
]
10 5 ms 2 ms 2 ms core3-toronto63_pos0-1.net.bell.ca [64.230.242.9
3]
11 13 ms 13 ms 13 ms core2-chicago23_pos2-0-0.net.bell.ca [64.230.147
.10]
12 bx1-chicagodt_pos10-0.net.bell.ca [64.230.203.150] reports: Destination ho
st unreachable.

Trace complete.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Source: 67.15.80.76 (my server)
Destination: 66.38.252.1

root@sun [~]# traceroute 66.38.252.1
traceroute to 66.38.252.1 (66.38.252.1), 30 hops max, 38 byte packets
1 ev1s-67-15-80-1.ev1servers.net (67.15.80.1) 0.452 ms 0.388 ms 0.399 ms
2 gphou-66-98-241-8.ev1servers.net (66.98.241. 0.344 ms 0.376 ms *
3 gphou-66-98-240-4.ev1servers.net (66.98.240.4) 0.440 ms 0.452 ms 0.393 ms
4 ge-1-12.r03.hstntx01.us.bb.gin.ntt.net (129.250.10.105) 1.658 ms 90.871 ms 3.035 ms
5 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 1.731 ms 1.593 ms 1.532 ms
MPLS Label=101088 CoS=5 TTL=1 S=0
6 * xe-0-0-0.r21.hstntx01.us.bb.gin.ntt.net (129.250.3.63) 1.759 ms 1.640 ms
MPLS Label=630832 CoS=5 TTL=1 S=0
7 p64-1-3-0.r21.dllstx09.us.bb.gin.ntt.net (129.250.4.68) 6.505 ms 6.531 ms 6.557 ms
8 t8-3.mpd01.dfw03.atlas.cogentco.com (154.54.11.193) 6.666 ms 6.579 ms 6.611 ms
9 * t8-1.mpd01.dfw01.atlas.cogentco.com (154.54.6.97) 6.733 ms 6.895 ms
10 t9-2.mpd01.mci01.atlas.cogentco.com (154.54.2.230) 27.160 ms 27.356 ms 27.148 ms
MPLS Label=599 CoS=5 TTL=1 S=0
11 t7-1.mpd01.ord01.atlas.cogentco.com (154.54.6.157) 27.128 ms 27.269 ms 27.172 ms
MPLS Label=193 CoS=5 TTL=1 S=0
12 g12-0-0.core02.ord01.atlas.cogentco.com (154.54.3.253) 26.959 ms 26.950 ms 27.005 ms
13 p5-0.core01.yyz01.atlas.cogentco.com (66.28.4.214) 41.268 ms 41.199 ms 41.012 ms
14 v3491.mpd01.yyz01.atlas.cogentco.com (154.54.5.78) 40.991 ms 40.872 ms 41.227 ms
15 v3492.mpd01.yyz02.atlas.cogentco.com (154.54.5.82) 40.958 ms 41.058 ms 41.084 ms
16 Primus.demarc.cogentco.com (38.112.1.6) 40.924 ms 41.012 ms 40.920 ms
17 fa3-0-401.core1.tor2.primus.ca (216.254.130.198) 44.533 ms 41.310 ms 41.368 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *

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

Please let me know. Thank you.

This is seems to be occurring to a LOT of people including people from oversears

a) source = 74.72.47.223
b) destination = 216.127.92.140
c) Traceroute to destination

1 3 ms 4 ms <1 ms 192.168.251.1
2 14 ms 14 ms 14 ms 10.42.192.1
3 18 ms 19 ms 14 ms g5-3.nycmnyl-rtr1.nyc.rr.com [24.29.113.21]
4 13 ms 14 ms 15 ms tenge10-0-0.nycmnyrdc-rtr1.nyc.rr.com [24.29.119.117]
5 * 13 ms 14 ms tenge-0-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.94]
6 14 ms 14 ms 14 ms 4.79.188.37
7 19 ms 14 ms 24 ms ae-1-51.bbr1.Newark1.Level3.net [4.68.99.1]
8 12 ms 14 ms 14 ms ae-0-0.bbr1.NewYork1.Level3.net [64.159.1.41]
9 13 ms 19 ms 14 ms ge-6-0-0-55.gar3.NewYork1.Level3.net [4.68.97.132]
10 * * * Request timed out.
11 41 ms 44 ms 39 ms bcs1-so-6-0-0.NewYork.savvis.net [204.70.192.37]
12 53 ms 46 ms 34 ms bcs1-so-6-2-0.Washington.savvis.net [204.70.192.13]
13 57 ms 60 ms 38 ms dcr1-so-3-0-0.Atlanta.savvis.net [204.70.192.53]
14 59 ms 34 ms 59 ms bcr1-so-1-0-0.Dallas.savvis.net [204.70.193.17]
15 56 ms 64 ms 65 ms iar1-so-2-0-0.Houston.savvis.net [208.172.129.21]
16 52 ms 55 ms 64 ms 208.172.129.2
17 53 ms 64 ms 64 ms ivhou-207-218-245-27.ev1servers.net [207.218.245.27]
18 57 ms 64 ms 59 ms iar1-so-2-0-0.Houston.savvis.net [208.172.129.21]
19 66 ms 64 ms 65 ms 208.172.129.2
20 65 ms 69 ms 59 ms ivhou-207-218-245-27.ev1servers.net [207.218.245.27]
21 64 ms 60 ms 59 ms ivhou-207-218-245-126.ev1servers.net [207.218.245.126]
22 64 ms 60 ms 64 ms [216.127.92.140]

d) traceroute from server

1 ev1s-216-127-92-1.ev1servers.net (216.127.92.1) 0.579 ms 0.273 ms 0.202 m
s
2 ivhou-207-218-245-3.ev1servers.net (207.218.245.3) 0.781 ms 0.391 ms *
3 ge-1-15.r03.hstntx01.us.bb.gin.ntt.net (129.250.10.69) 1.675 ms 1.245 ms 1.088 ms
4 * * *
5 * * *
6 p64-1-3-0.r21.dllstx09.us.bb.gin.ntt.net (129.250.4.68) 6.110 ms 6.059 ms 6.022 ms
7 te-3-1.car3.Dallas1.Level3.net (4.68.110.61) 6.234 ms 6.320 ms *
8 ae-32-56.ebr2.Dallas1.Level3.net (4.68.122.190) 18.838 ms ae-31-55.ebr1.Dallas1.Level3.net (4.68.122.158) 19.649 ms ae-31-53.ebr1.Dallas1.Level3.net (4.68.122.94) 12.462 ms
9 ae-3.ebr1.Atlanta2.Level3.net (4.69.132.82) 43.377 ms 52.040 ms *
10 ae-2.ebr1.Washington1.Level3.net (4.69.132.86) 50.314 ms 49.795 ms 40.013 ms
11 ae-1-100.ebr2.Washington1.Level3.net (4.69.132.30) 50.104 ms 42.371 ms *
12 ae-4.ebr2.Newark1.Level3.net (4.69.132.102) 50.394 ms 53.370 ms ae-1-100.ebr2.Washington1.Level3.net (4.69.132.30) 40.114 ms
13 ae-21-56.car1.Newark1.Level3.net (4.68.99.165) 49.704 ms ae-21-52.car1.Newark1.Level3.net (4.68.99.37) 51.368 ms *
14 ae-21-56.car1.Newark1.Level3.net (4.68.99.165) 50.101 ms ROADRUNNER.car1.Newark1.Level3.net (4.79.188.114) 45.312 ms 4.79.188.38 (4.79.188.38) 49.358 ms
15 tenge8-0-0.nycmnyrdc-rtr1.nyc.rr.com (24.29.119.93) 50.477 ms 45.371 ms *
16 tenge0-0-0.nycmnyl-rtr1.nyc.rr.com (24.29.119.118) 50.743 ms tenge8-0-0.nycmnyrdc-rtr1.nyc.rr.com (24.29.119.93) 45.823 ms tenge0-0-0.nycmnyl-rtr1.nyc.rr.com (24.29.119.118) 50.300 ms
17 g0-2.nycmnyl-ubr7.nyc.rr.com (24.29.113.22) 45.823 ms tenge0-0-0.nycmnyl-rtr1.nyc.rr.com (24.29.119.118) 51.035 ms *
18 * * g0-2.nycmnyl-ubr7.nyc.rr.com (24.29.113.22) 50.849 ms

my firewall blocks it after that point

Hi, sorry but I need help.

I try connect to taigaclan.com (216.40.243.206) … my tracing route:


1 <1 ms <1 ms <1 ms 10.168.56.1
2 1 ms 1 ms 1 ms core-3750-6.sibeltelecom.ru [ 217.117.80.17]
3 <1 ms <1 ms 1 ms gw1-core-fa0-1-18.sibeltelecom.ru [217.117.82.217]
4 8 ms 5 ms 5 ms gw2-core2-Gi0-2-480.sibeltelecom.ru [217.117.87.17]
5 5 ms 7 ms 7 ms nsk252-vl314.ll-nsk.zsttk.ru [82.200.66.65]
6 7 ms 3 ms 5 ms nsk15-transtelecom.ll-nsk.zsttk.ru [ 82.200.66.249]
7 104 ms 106 ms 103 ms 195.66.224.185
8 223 ms 224 ms 222 ms t3-2.mpd01.bos01.atlas.cogentco.com [130.117.0.185]
9 223 ms 221 ms 226 ms t2-2.mpd01.ord01.atlas.cogentco.com [154.54.7.81 ]
10 222 ms 227 ms 232 ms t4-2.mpd01.iah01.atlas.cogentco.com [154.54.5.221]
11 220 ms 223 ms 221 ms g2-0-0.core01.iah01.atlas.cogentco.com [154.54.2.241]
12 * * * Request timed out.
13 * * * Request timed out
14 * * * Request timed out
15 * * * Request timed out

I have asked “cogent” support and has received the answer:

It appears that the route is reaching Everyone's Internet, but at that point, it has left the Cogent network, and the return path may have changed.

You should contact Everyone's Internet directly.
Cogent Network Operations

I use cogent Looking Glass:

Tracing the route to taigaclan.com (216.40.243.206)

1 g9-2.3.core01.lon02.atlas.cogentco.com (130.117.16.121) 0 msec 0 msec 4 msec
2 t1-1.mpd02.lon01.atlas.cogentco.com (130.117.2.26) 188 msec 4 msec 0 msec
3 t3-2.mpd01.bos01.atlas.cogentco.com (130.117.0.185) 124 msec 120 msec 120 msec
4 t2-2.mpd01.ord01.atlas.cogentco.com (154.54.7.81) 248 msec 204 msec 192 msec
5 t4-2.mpd01.iah01.atlas.cogentco.com (154.54.5.221) 128 msec 128 msec 128 msec
6 g2-0-0.core01.iah01.atlas.cogentco.com (154.54.2.241) 120 msec 120 msec 120 msec
7 EveryonesInternet.demarc.cogentco.com (38.112.12.178) 124 msec 124 msec 124 msec
8 ivhou-207-218-245-27.ev1servers.net (207.218.245.27) 124 msec 124 msec 124 msec
9 ivhou-207-218-245-126.ev1servers.net (207.218.245.126) 124 msec 124 msec 124 msec
10 taigaclan.com (216.40.243.206) 124 msec 124 msec 124 msec

Where problem ?

Hi, I have been unable to connect my server at http://cmsbox.co.uk for about a day and a half. The trace route dies after reaching the planet, which led me to post here. Any ideas what the problem could be? Could it be someone on my end? Here's my traceroute information:

source IP: 74.196.182.29
destination IP: 70.85.162.34

Tracing route to cmsbox.co.uk [70.85.162.34]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 112 ms 10 ms 11 ms 10.227.120.1
3 10 ms 7 ms 9 ms cdm-208-180-219-81.cnro.suddenlink.net [208.180.219.81]
4 25 ms 23 ms 24 ms cdm-66-76-31-165.lfkn.suddenlink.net [66.76.31.165]
5 28 ms 25 ms 27 ms ge-4-22.car4.SanJose1.Level3.net [4.71.114.29]
6 26 ms 32 ms 38 ms vlan79.csw2.SanJose1.Level3.net [4.68.18.126]
7 31 ms 32 ms 34 ms ae-73-73.ebr3.SanJose1.Level3.net [4.69.134.229]
8 42 ms 33 ms 40 ms ae-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
9 32 ms 66 ms 35 ms ae-78.ebr2.LosAngeles1.Level3.net [4.69.135.13]
10 70 ms 72 ms 70 ms ae-3.ebr3.Dallas1.Level3.net [4.69.132.78]
11 74 ms 70 ms 74 ms ae-78.ebr2.Dallas1.Level3.net [4.69.135.5]
12 * * * Request timed out.
13 72 ms 64 ms 81 ms THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
14 64 ms 65 ms 77 ms te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14]
15 74 ms 76 ms 67 ms po31.dsr01.dllstx5.theplanet.com [70.85.127.106]
16 83 ms 77 ms 77 ms po2.car03.dllstx5.theplanet.com [70.84.160.165]
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.

Any help would be greatly appreciated!

Thanks,
Ron

Ron,
It would appear that there is nothing on our network equipment that would be blocking your traffic, but maybe a firewall rule on the remote server. Please contact the system administrator of that website for more details.

Im patching my server, been going on for about 2hrs, then it aborts and I am notified to check network connectivity and retry.

up2date works, ncftp ftp.ensim.com works

Traceroute from my machine to ftp.ensim.com

Looks like there is trouble in the NTT backbone

# /usr/sbin/traceroute ftp.ensim.com
traceroute to ftp2.ensim.com (128.242.109.163), 30 hops max, 38 byte packets
1 ev1s-207-44-xxx-xxx.ev1servers.net (207.44.xxx.xxx) 1.406 ms 1.190 ms 1.160 ms
2 ivhou-207-218-245-5.ev1servers.net (207.218.245.5) 1.340 ms 1.358 ms *
3 ivhou-207-218-223-13.ev1servers.net (207.218.223.13) 1.620 ms 1.372 ms 1.346 ms
4 ge-1-16.r03.hstntx01.us.bb.gin.ntt.net (129.250.10.145) 2.083 ms 2.472 ms 1.984 ms
Icmp checksum is wrong
5 xe-0-1-0.r20.hstntx01.us.bb.gin.ntt.net (129.250.2.228) 2.339 ms *Icmp checksum is wrong
2.360 ms
Icmp checksum is wrong
6 xe-0-0-0.r21.hstntx01.us.bb.gin.ntt.net (129.250.3.63) 2.223 msIcmp checksum is wrong
2.489 msIcmp checksum is wrong
2.324 ms
Icmp checksum is wrong
7 p64-2-0-0.r20.lsanca03.us.bb.gin.ntt.net (129.250.5.12) 44.608 msIcmp checksum is wrong
44.276 msIcmp checksum is wrong
44.295 ms
Icmp checksum is wrong
8 as-0.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.96) 54.422 msIcmp checksum is wrong
54.257 msIcmp checksum is wrong
54.124 ms
Icmp checksum is wrong
9 ae-0.r20.snjsca04.us.bb.gin.ntt.net (129.250.2.96) 54.264 msIcmp checksum is wrong
54.199 msIcmp checksum is wrong
54.202 ms
10 xe-1-3.r02.mlpsca01.us.bb.gin.ntt.net (129.250.5.61) 107.590 ms 87.285 ms 56.495 ms
11 mg-1.a00.mlpsca01.us.da.verio.net (129.250.24.194) 56.380 ms 56.850 ms 56.577 ms
12 *

not sure if this is related to my problem but it seems to be a problem nevertheless.

You can check http://www.internetpulse.net/ for current latency information for most of the major US ISPs listed at this site. It is very useful if you are able to track back problems to a specific location.

Currently it does seem that NTT is experiencing some latency issues which could account for your problems.

Hope you can find this useful.

the original post was here; i am from malaysia and i have some servers at ev1. when i use 3G service from one of my ISPs (namely, Celcom) i cannot access servercommand.net and my server.

tracert:
from my machine (public IP is 219.93.152.3, or celcom3g.tm.net.my) to servercommand.net


Tracing route to servercommand.net [207.44.253.236]

over a maximum of 30 hops:

1 135 ms 119 ms 119 ms 10.221.1.174

2 106 ms 109 ms 99 ms 10.221.1.197

3 117 ms 172 ms 96 ms 219.93.152.1

4 496 ms 209 ms 120 ms 219.93.153.49

5 128 ms 129 ms 162 ms 210.187.132.50

6 120 ms 139 ms 139 ms brf-odsy02-srp1-0.tm.net.my [210.187.135.2]

7 418 ms 128 ms * 58.27.101.38

8 139 ms 139 ms 138 ms 210.187.129.131

9 256 ms 252 ms 246 ms 58.27.124.46

10 124 ms 139 ms 139 ms 219.93.173.37

11 326 ms 320 ms 329 ms 219.93.153.150

12 338 ms * 368 ms g1-14.mpd01.sjc03.atlas.cogentco.com [154.54.12.1]

13 * 312 ms * v3493.mpd01.sjc01.atlas.cogentco.com [154.54.6.109]

14 306 ms 329 ms 339 ms g6-0-0.core01.sjc01.atlas.cogentco.com [154.54.3.33]

15 * 360 ms 369 ms p14-0.core01.iah01.atlas.cogentco.com [66.28.4.237]

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.


many of my clients are switching to Celcom 3G now, and the issue affects my existing clients as well. i am curious that this is happening because back in May 2007, i still could access the services without problem.

i would like to know if it is the problem of my ISP. if it is not, please tell me what i should do.

Hello, I am from Spain

ivhou-207-218-245-112.ev1servers.net [207.218.245.112] have some problem


root@host2 [~]# traceroute 66.98.170.88
traceroute to 66.98.170.88 (66.98.170.88), 30 hops max, 38 byte packets
1 ge-4-0-0-r01.bcn.centrodedatos.datahouse.es (86.109.96.1) 0.398 ms 0.341 ms 0.254 ms
2 g9-0-213.core01.bcn01.atlas.cogentco.com (149.6.83.5) 0.687 ms 0.604 ms 0.334 ms
3 p3-0.core01.par01.atlas.cogentco.com (130.117.0.153) 22.058 ms 149.779 ms 207.282 ms
4 p14-0.core02.dca01.atlas.cogentco.com (66.28.4.206) 102.087 ms 101.860 ms 101.847 ms
5 p14-0.core01.atl01.atlas.cogentco.com (66.28.4.161) 113.339 ms 113.396 ms 113.331 ms
6 p10-0.core01.iah01.atlas.cogentco.com (154.54.5.89) 144.176 ms 144.221 ms 143.954 ms
7 EveryonesInternet.demarc.cogentco.com (38.112.12.186) 144.947 ms 144.894 ms 144.859 ms
8 ivhou-207-218-245-29.ev1servers.net (207.218.245.29) 145.214 ms 144.842 ms 144.886 ms
9 ivhou-207-218-245-112.ev1servers.net (207.218.245.112) 729.275 ms !H 1894.657 ms !H 4000.543 ms !H <===!!!! here
root@host2 [~]#


tracert 66.98.170.88

Traza a la dirección host1.cat1.net [66.98.170.88]
sobre un máximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 24 ms 25 ms 1.220.217.87.dynamic.jazztel.es [87.217.220.1]
3 * * * Tiempo de espera agotado para esta solicitud.
4 24 ms 24 ms 25 ms 163.216.106.212.static.jazztel.es [212.106.216.1
63]
5 * * * Tiempo de espera agotado para esta solicitud.
6 25 ms 24 ms 24 ms ge-4-0-0-dcr1.bap.cw.net [208.175.154.177]
7 32 ms 44 ms 32 ms so-7-0-0-dcr1.mad.cw.net [195.2.2.94]
8 33 ms 39 ms 32 ms so-0-0-0-dcr1.esx.cw.net [195.2.9.122]
9 58 ms 50 ms 50 ms so-7-0-0-dcr2.tsd.cw.net [195.2.9.145]
10 50 ms 50 ms 50 ms abovenet-gw-ies1.lnt.cw.net [166.63.218.194]
11 124 ms 125 ms 135 ms so-4-0-0.cr1.dca2.us.above.net [64.125.27.57]
12 171 ms 171 ms 171 ms so-5-1-0.mpr2.atl6.us.above.net [64.125.29.37]
13 178 ms 171 ms 172 ms so-0-0-0.mpr3.iah1.us.above.net [64.125.26.13]
14 170 ms 169 ms 170 ms 289.ev1servers.net [216.200.251.26]
15 172 ms 170 ms 171 ms ivhou-207-218-245-29.ev1servers.net [207.218.245
.29]
16 ivhou-207-218-245-112.ev1servers.net [207.218.245.112] informes: Host de destino inaccesible. <=== !!! here again

Traza completa.


Please! help!

I have the same problem as you exactly the same,and now i sloved it.

Having problems connecting from Australia today.

Microsoft® Windows DOS

©Copyright Microsoft Corp 1990-2001.



C:\DOCUME~1\UMAKU>tracert umaku.com



Tracing route to umaku.com [67.15.16.7]

over a maximum of 30 hops:



1 1 ms 1 ms <1 ms 192.168.0.1

2 5 ms 2 ms 2 ms mygateway1.ar7 [10.1.1.1]

3 31 ms 33 ms 33 ms 203.23.236.34

4 33 ms 32 ms 32 ms core-syd.comcen.com.au [203.23.236.65]

5 33 ms 32 ms 33 ms vlan551.22rrc76f000.optus.net.au [59.154.10.17]



6 230 ms 230 ms 226 ms ge-0-1-0-0.plapx-dr1.ix.singtel.com [203.208.149

.249]

7 267 ms 270 ms 272 ms ge-5-2-1.mpr4.pao1.us.above.net [64.125.13.5]

8 260 ms 263 ms 263 ms so-1-2-2.mpr2.sjc2.us.above.net [64.125.29.126]



9 265 ms 263 ms 262 ms so-1-0-0.mpr2.lax9.us.above.net [64.125.26.29]

10 * 272 ms * so-0-1-0.mpr3.iah1.us.above.net [64.125.25.17]

11 * 257 ms 256 ms so-0-0-0.mpr4.iah1.us.above.net [64.125.26.14]

12 * * * Request timed out.

13 * * * Request timed out.

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17



======================
WAN ipnumber (210.1.196.151)

In computer networking, the Transport Layer is a group of methods and protocols within a layered architecture of network components, within which it is responsible for encapsulating application data blocks into datagrams suitable for transfer to the network infrastructure for transmission to the destination host, or managing the reverse transaction by abstracting network datagrams and delivering them to an application. Such protocol are also referred to as "transport protocols".

-------------------------
sandy223

CONSUMER GENERATED MEDIA

I'm having an issue reaching one of your hosted services - I have been receiving pretty bad responses times that can cause frequent disconnects and yet it seems localized to theplanet.com servers.

The IP trying to reach is 207.44.136.67
My IP is 76.229.139.214

1 5 ms 4 ms 4 ms 192.168.1.254
2 10 ms 10 ms 10 ms adsl-76-229-139-254.dsl.scrm01.sbcglobal.net [76.229.139.254]
3 11 ms 10 ms 10 ms dist2-vlan60.scrm01.pbi.net [64.171.152.131]
4 10 ms 10 ms 12 ms 151.164.93.214
5 15 ms 15 ms 15 ms ex2-p10-0.pxpaca.sbcglobal.net [151.164.190.83]
6 15 ms 16 ms 15 ms as4323-twtelecom.pxpaca.sbcglobal.net [151.164.248.110]
7 62 ms 63 ms 62 ms hagg-03-ge-0-0-0-540.hsto.twtelecom.net [66.192.246.206]
8 62 ms 62 ms 62 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153
9 70 ms 68 ms 65 ms po1.car01.hstntx1.theplanet.com [207.218.223.2]
10 63 ms 65 ms 62 ms ev1s-207-44-136-67.theplanet.com [207.44.136.67]

The ping summary:

Ping statistics for 207.44.136.67:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 70ms, Average = 63ms


Any ideas?

Sanddemon,

This was brought to our attention via another customer and we have adjusted routing. Please check this and see if it is any better for you. If not, please feel free to open a ticket and provide both inbound and outbound traceroutes.

Source IP: 74.94.11.106
Destination IP: 207.44.225.50

1 * * * Request timed out.
2 177 ms 203 ms 154 ms ge-2-2-ur01.reading.pa.panjde.comcast.net [68.85.195.201]
3 195 ms 160 ms 185 ms te-1-1-ur02.reading.pa.panjde.comcast.net [68.86.208.218]
4 170 ms 161 ms 182 ms te-1-1-ur01.newhanover.pa.panjde.comcast.net [68.86.208.222]
5 44 ms 194 ms 201 ms 68.85.158.46
6 150 ms 174 ms 26 ms 68.85.158.50
7 128 ms 171 ms 175 ms 68.86.153.141
8 239 ms 263 ms 175 ms pos-0-4-0-0-ar01.401nbroadst.pa.panjde.comcast.net [68.86.210.209]
9 184 ms 195 ms 120 ms pos-1-9-0-0-cr01.mclean.va.ibone.comcast.net [68.86.90.13]
10 169 ms 185 ms 99 ms pos-1-12-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.237]
11 234 ms 209 ms 267 ms pos-1-14-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.153]
12 188 ms 228 ms 171 ms theplanet-cr01.dallas.tx.ibone.comcast.net [68.86.88.50]
13 213 ms 242 ms 196 ms et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]
14 207 ms 137 ms 156 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]
15 170 ms 142 ms 213 ms po1.car06.hstntx1.theplanet.com [207.218.223.22]
16 * * * Request timed out.
17 * * * Request timed out.

I can connect fine from other sites. Reseller was useless - they said it was Comcast blocking it and were unwilling to contact you.

I can provide a traceroute from a working location if desired.

Giverson,

I am able to traceroute from a Comcast location so it doesn't appear to be a nation-wide block:

(UDP traceroute)
# traceroute 207.44.225.50
traceroute to 207.44.225.50 (207.44.225.50), 30 hops max, 38 byte packets
1 [DELETED] ([DELETED]) 1.542 ms 1.366 ms 1.365 ms
2 * * *
3 ge-2-25-ur02.bisbee.tx.houston.comcast.net (68.85.250.9) 18.405 ms 10.177 ms 12.236 ms
4 po-11-ur01.bisbee.tx.houston.comcast.net (68.85.244.13) 11.331 ms 11.214 ms 10.865 ms
5 po-12-ur02.almeda.tx.houston.comcast.net (68.85.244.18) 15.100 ms 13.611 ms 14.309 ms
6 po-11-ur01.almeda.tx.houston.comcast.net (68.85.244.21) 15.604 ms 14.232 ms 13.953 ms
7 po-12-ur02.pike.tx.houston.comcast.net (68.85.244.26) 15.239 ms 19.250 ms 15.064 ms
8 po-11-ur01.pike.tx.houston.comcast.net (68.85.244.29) 32.928 ms 18.721 ms 16.659 ms
9 po-14-ar02.bearcreek.tx.houston.comcast.net (68.85.244.33) 17.013 ms 16.807 ms 17.809 ms
10 po-16-ar01.greenspoint.tx.houston.comcast.net (68.85.244.73) 28.227 ms 20.453 ms 17.979 ms
11 po-12-ar02.greenspoint.tx.houston.comcast.net (68.85.244.154) 20.379 ms 19.565 ms 18.692 ms
12 te-0-1-0-1-cr01.dallas.tx.ibone.comcast.net (68.86.91.53) 24.134 ms 27.544 ms 24.120 ms
13 theplanet-cr01.dallas.tx.ibone.comcast.net (68.86.88.50) 24.610 ms 35.145 ms 23.777 ms
14 et1-1.ibr01.hstntx2.theplanet.com (70.87.253.50) 28.827 ms 31.910 ms 29.766 ms
15 et3-3.ibr01.hstntx1.theplanet.com (70.87.253.153) 29.135 ms 30.235 ms 28.422 ms
16 po1.car06.hstntx1.theplanet.com (207.218.223.22) 29.952 ms 30.109 ms 31.998 ms
17 web03.simpleupdates.com (207.44.225.50) 30.215 ms 40.491 ms 30.250 ms

(ICMP traceroute)
# traceroute -I 207.44.225.50
traceroute to 207.44.225.50 (207.44.225.50), 30 hops max, 38 byte packets
1 [DELETED] ([DELETED]) 1.470 ms 1.434 ms 1.400 ms
2 * * *
3 ge-2-25-ur02.bisbee.tx.houston.comcast.net (68.85.250.9) 9.013 ms 20.245 ms 9.428 ms
4 po-11-ur01.bisbee.tx.houston.comcast.net (68.85.244.13) 10.466 ms 9.421 ms 8.973 ms
5 po-12-ur02.almeda.tx.houston.comcast.net (68.85.244.18) 13.537 ms 12.101 ms 13.567 ms
6 po-11-ur01.almeda.tx.houston.comcast.net (68.85.244.21) 14.631 ms 15.248 ms 15.379 ms
7 po-12-ur02.pike.tx.houston.comcast.net (68.85.244.26) 18.338 ms 13.151 ms 14.391 ms
8 po-11-ur01.pike.tx.houston.comcast.net (68.85.244.29) 15.524 ms 14.727 ms 25.377 ms
9 po-14-ar02.bearcreek.tx.houston.comcast.net (68.85.244.33) 24.535 ms 20.256 ms 18.242 ms
10 po-16-ar01.greenspoint.tx.houston.comcast.net (68.85.244.73) 28.872 ms 22.757 ms 17.360 ms
11 po-12-ar02.greenspoint.tx.houston.comcast.net (68.85.244.154) 16.759 ms 22.915 ms 25.734 ms
12 te-0-1-0-1-cr01.dallas.tx.ibone.comcast.net (68.86.91.53) 21.123 ms 22.172 ms 22.395 ms
13 theplanet-cr01.dallas.tx.ibone.comcast.net (68.86.88.50) 21.662 ms 22.335 ms 23.917 ms
14 et1-1.ibr01.hstntx2.theplanet.com (70.87.253.50) 31.837 ms 29.268 ms 28.966 ms
15 et3-3.ibr01.hstntx1.theplanet.com (70.87.253.153) 29.123 ms 27.363 ms 27.850 ms
16 po1.car06.hstntx1.theplanet.com (207.218.223.22) 28.393 ms 35.846 ms 27.203 ms
17 web03.simpleupdates.com (207.44.225.50) 28.000 ms 34.285 ms 34.121 ms

This leaves a few of possibilities:

A) Comcast is locally blocking the destination IP:
- This would mean that Comcast is blocking the destination IP closer to your source (i.e. in PA or close to there along the path).

B) The return path has a problem such as a block or possibly a routing issue.
- This seems unlikely since your trace makes it all the way to the immediate router before the destination, but is still possible.

C) The server is blocking your IP in some way.
- The server could simply be blocking ICMP traces from your source (or others) or could be blocking your source IP entirely. The blocking of ICMP (or UDP) traces also appears unlikely since my trace from a Comcast source worked with both UDP and ICMP, but still leaves the possibility of your source IP being blocked for ICMP, UDP or completely.

If possible please ask the party responsible for the server to open a ticket with us and provide them with the non-functional traceroute as well as a functional traceroute (preferably from near the same location and on the same provider) so they can put that information in the ticket. Also please provide them with the source IPs of both traces so they can traceroute back to your sources to illustrate the return path for troubleshooting.

We do get transit from Comcast and can work with them to remove a block depending on the situation.