2010-08-05, 16:17
2010-08-05, 16:30
Fast here.. just you
2010-08-05, 16:57
Humm, any idea whats going on here?
Code:
chrisu@ubun:~$ tracepath xbmc.org
1: ubun.home (192.168.1.6) 0.111ms pmtu 1500
1: DD-WRT.home (192.168.1.1) 1.169ms
1: DD-WRT.home (192.168.1.1) 1.034ms
2: 192.168.0.1 (192.168.0.1) 6.578ms
3: lvrgtnhed11-dy1001.network.tds.net (96.61.168.1) 46.520ms
4: mtjltndst51.network.tds.net (64.50.234.105) 46.919ms
5: CHCGILDTcor01.peering.tds.net (206.223.119.64) 81.142ms asymm 6
6: xe1-1.cr01.ord01.mzima.net (206.223.119.62) 81.354ms asymm 7
7: te0-0.cr1.dal1.us.packetexchange.net (69.174.120.14) 101.228ms
8: te1-1.cr1.atl1.us.packetexchange.net (69.174.120.50) 112.361ms asymm 7
9: xe0-gnax.cust.atl01.mzima.net (67.199.136.158) 105.261ms asymm 8
10: silvercore2.whbdns.com (64.22.117.234) 90.929ms
11: silvercore2.whbdns.com (64.22.117.234) 91.330ms asymm 10
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Resume: pmtu 1500
2010-08-05, 17:20
No idea... Looks okay here. You can even try it from:
http://network-tools.com/default.asp?pro...t=xbmc.org
http://network-tools.com/default.asp?pro...t=xbmc.org
2010-08-05, 17:38
tslayer Wrote:No idea... Looks okay here. You can even try it from:
http://network-tools.com/default.asp?pro...t=xbmc.org
Yeah, that works fine. I guess I'll have a look at my DNS servers. Not having any trouble with anything else, strange.
2010-08-11, 08:24
If I use the dns servers from my providers (inside switzerland) ... the url is sometimes very very slow.
If I change the dns servers to the google dns ( 8.8.8.8 / 8.8.4.4) the response time
is better ..
If I change the dns servers to the google dns ( 8.8.8.8 / 8.8.4.4) the response time
is better ..
2010-08-31, 20:09
Same problem for me. Nothing to do with DNS; the site IP is resolved just fine. ISP is Comcast (business class) in WA, USA. However, the site works fine from my work. Interestingly enough, if I ping and wait a while I start getting ping responses and then while it's pinging I can get through to the website(s) too. Traceroute/tracepath is quite similar to Redneck's trace above, at least before the point of no reply:
Just a data point; I doubt either my ISP or XBMC's host can do anything about it directly; looks like a routing snarl-up somewhere in the backbone that us mortals don't have a hope of influencing.
Code:
rivendell ~ $ tracepath xbmc.org
1: i4031.net (173.160.134.93) 0.113ms pmtu 1500
1: no reply
2: no reply
3: be-50-ar01.burien.wa.seattle.comcast.net (68.86.96.213) 10.985ms
4: be-40-ar01.seattle.wa.seattle.comcast.net (68.85.240.94) 16.268ms asymm 5
5: pos-0-1-0-0-cr01.portland.or.ibone.comcast.net (68.86.93.109) 14.527ms asymm 4
6: pos-1-12-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.86.229) 26.961ms asymm 5
7: pos-1-14-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.85.190) 40.265ms asymm 6
8: pos-0-15-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.138) 72.923ms asymm 7
9: pos-0-13-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.254) 93.905ms asymm 8
10: pos-0-1-0-0-pe01.56marietta.ga.ibone.comcast.net (68.86.86.86) 95.635ms asymm 9
11: 66-208-229-54-ubr02b-muncie01-in.hfc.comcastbusiness.net (66.208.229.54) 93.441ms asymm 10
12: xe0-gnax.cust.atl01.mzima.net (67.199.136.170) 93.950ms asymm 11
13: atl-core-f-p2.gnax.net (207.210.95.254) 93.516ms asymm 11
14: silvercore2.whbdns.com (64.22.117.234) 96.893ms asymm 12
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1500
Just a data point; I doubt either my ISP or XBMC's host can do anything about it directly; looks like a routing snarl-up somewhere in the backbone that us mortals don't have a hope of influencing.
2010-08-31, 20:11
We've noticed some weird things going on this week. I've been in touch with our ISP, but so far, it seems you're right. Nothing we/they can do. Let's just hope the internet overlords get it worked out.
Cory
Cory
2010-09-19, 07:49
OK, here's something completely odd: site works fine from one of my other machines. Both behind the same NAT box. The one that works runs Linux; the one that doesn't runs Windows; in both I used Firefox. I tried the same various sub-sites (xmbc.org, Trac, and this forum), and at the same time, too. Just a curious data point.