From France it's impossible to visit the eservers site and we can't make a traceroute. It's the same since few days.

Someone know why ? :eek:

1 GW (62.161.136.190) 0.305 ms 0.254 ms 0.241 ms
2 26.GIG-9-0.GENG1.Gennevilliers.raei.francetelecom.net (194.2.0.194) 0.589 ms 0.472 ms 0.537 ms
3 195.101.89.170 (195.101.89.170) 1.469 ms 1.446 ms 1.520 ms
4 194.51.159.129 (194.51.159.129) 1.442 ms 1.532 ms 1.560 ms
5 P8-0.ntaub101.Aubervilliers.francetelecom.net (193.251.126.166) 1.608 ms 1.636 ms 1.602 ms
6 193.251.126.154 (193.251.126.154) 1.729 ms 1.674 ms 1.558 ms
7 P12-0.PASCR3.Pastourelle.opentransit.net (193.251.241.129) 2.139 ms 2.031 ms 2.052 ms
8 So0-0-0.TELBB1.Telehouse.opentransit.net (193.251.241.177) 2.138 ms 2.357 ms 2.256 ms
9 pos0-0.mpr1.cdg4.fr.mfnx.net (208.184.210.233) 2.384 ms 2.133 ms 2.009 ms
10 pos8-0.cr1.cdg2.fr.mfnx.net (208.184.231.214) 2.305 ms 2.103 ms 2.174 ms
11 so-5-0-0.cr1.lhr3.uk.mfnx.net (64.125.31.154) 11.969 ms 11.942 ms 11.714 ms
12 so-7-0-0.cr1.dca2.us.mfnx.net (64.125.31.186) 83.808 ms 83.670 ms 83.809 ms
13 so-4-1-0.cr2.atl2.us.mfnx.net (208.184.232.50) 94.704 ms 94.801 ms 95.274 ms
14 pos1-0.per1.atl2.us.mfnx.net (208.185.0.226) 94.989 ms 94.836 ms 94.784 ms
15 abovenet-tr1.atl2-1-1.national-net.com (66.115.128.53) 95.160 ms 95.063 ms 95.103 ms
16 tr1.atl2-1-2-tr1.atl1-1-8.national-net.com (66.115.128.42) 95.302 ms 95.223 ms 94.899 ms
17 209.51.137.125 (209.51.137.125) 95.965 ms 95.404 ms 95.265 ms
18 velocity.eservers.biz (209.51.159.226) 95.311 ms 95.063 ms 95.111 ms

From Annecy and Paris, me and my friends get :

"Couldn't resolve host name : www.eservers.biz"

Whos your ISP? :confused:

It's Wanadoo ADSL France (France Telecom).

You can go to http://www.tracert.com/cgi-bin/trace.pl

and choose "France, Paris, Conservatoire National des Arts et Métiers" to test www.eservers.biz. You'll see what I get.

Traceroute
Result for eservers.biz:
traceroute to eservers.biz (209.51.159.226), 64 hops max, 40 byte packets
1 enst-free.enst.fr (137.194.2.253) 0.355 ms 0.301 ms 0.345 ms
2 telehouse-3.routers.proxad.net (213.228.3.3) 1.451 ms 1.269 ms 1.662 ms
3 blackd-th1-1-a6.routers.proxad.net (213.228.3.23) 2.445 ms 1.760 ms 2.326 ms
4 fe2-1.mpr1.cdg4.fr.mfnx.net (208.184.231.241) 2.601 ms 2.068 ms 2.346 ms
5 pos8-0.cr1.cdg2.fr.mfnx.net (208.184.231.214) 1.618 ms 1.617 ms 1.666 ms
6 so-5-0-0.cr1.lhr3.uk.mfnx.net (64.125.31.154) 11.913 ms 11.647 ms 11.306 ms
7 so-7-0-0.cr1.dca2.us.mfnx.net (64.125.31.186) 83.045 ms 83.109 ms 83.067 ms
8 so-4-1-0.cr2.atl2.us.mfnx.net (208.184.232.50) 94.152 ms 94.390 ms 94.127 ms
9 pos1-0.per1.atl2.us.mfnx.net (208.185.0.226) 95.795 ms 95.889 ms 96.423 ms
10 abovenet-tr1.atl2-1-1.national-net.com (66.115.128.53) 94.852 ms 96.274 ms 94.355 ms
11 tr1.atl2-1-2-tr1.atl1-1-8.national-net.com (66.115.128.42) 94.669 ms 94.763 ms 98.975 ms
12 209.51.137.125 (209.51.137.125) 103.200 ms 102.591 ms 102.984 ms
13 velocity.eservers.biz (209.51.159.226) 103.153 ms 101.939 ms 102.097 ms

:confused: Is it the traceroute from "France, Paris, Conservatoire National des Arts et Métiers" ?

I don't think so, it's from "France, Paris, EU.org (via Global One)" (via Global One, it's working).

KPNQWest going dark on Wednesday. It could be routing problems being created from that.

Hal

Yes, maybe it's due to KPNQWest.

opps my mistake, but the other traceroute gives me a 404 :confused:

Welcome in France ! :D

merci, j'apprécierai le sejour!

Tu parles français ou c'est le traducteur de Google ?... ;)

No actually its not a google translator, its a piece of software i have on my pda, useful for when visiting overseas ;)

ok :stickout

I did a couple of traceroutes from France last week, and noticed some weird things happening since KPNQuest went under. For example connections to some other european countries like Ireland are now often routed via New York, instead of directly.

At any rate this isn't a problem at eserver.biz's side.

As more of our isp's and other providers are having financial problems and letting their maintenance slip. From my home, last weekend, I had trouble accessing yahoo, google, dotster and others. Seems XO Communications (my dsl provider) was having dns problems. I had a customer this week who couldn't access his site, because his isp had not undated the dns in spite of the fact that every whois I checked had it right. So, he kept thinking his site was down....(resolving to old address), when it was never down.

The Internet is falling apart. Alright maybe that's a bit over the top, but problems such as this have been going up. Just the other day we had a customer who couldn't properly access his web site because of high packet loss, and it turned out that it was a network along the way.

This sort of thing used to happen far less often last year as far as I can recall.

i agree, worldcom down, i know some bookmakers are taking odds on whos going to be the next worldcom ;)

the world is ending. live with it.

:D

Try a traceroute and ping from Europe to meltdown.site5.com - last week was getting 70 - 80 ms response from Belgium, UK, Germany and France. Be interesting to see if its degraded since then.

Pinging meltdown.site5.com [216.118.109.201] with 32 bytes of data:

Reply from 216.118.109.201: bytes=32 time=112ms TTL=53
Reply from 216.118.109.201: bytes=32 time=112ms TTL=53
Reply from 216.118.109.201: bytes=32 time=111ms TTL=53
Reply from 216.118.109.201: bytes=32 time=118ms TTL=53

That's from my PC in the Netherlands. I'm on the edge of the country, so rather far from the AIX, that could explain the slight delay.

France:

traceroute to meltdown.site5.com (216.118.109.201), 64 hops max, 40 byte packets
1 enst-free.enst.fr (137.194.2.253) 0.385 ms 0.423 ms 0.273 ms
2 telehouse-3.routers.proxad.net (213.228.3.3) 1.426 ms 1.263 ms 1.309 ms
3 blackd-cbv-2-a6.routers.proxad.net (213.228.3.22) 2.625 ms 2.201 ms 3.574 ms
4 Vlan208.msfc2.Paris2.teleglobe.net (195.219.53.97) 2.854 ms 5.015 ms 2.589 ms
5 if-3-0.core1.Paris2.teleglobe.net (195.219.15.161) 2.169 ms 3.216 ms 1.654 ms
6 if-8-0.core1.Frankfurt2.teleglobe.net (195.219.15.206) 11.094 ms 12.050 ms 11.367 ms
7 if-10-0.core3.NewYork.Teleglobe.net (66.110.8.154) 93.548 ms 90.847 ms 90.930 ms
8 if-4-0.core2.NewYork.Teleglobe.net (66.110.8.138) 265.515 ms 101.050 ms 200.959 ms
9 if-4-0.bb8.NewYork.Teleglobe.net (66.110.8.130) 90.888 ms 90.961 ms 91.321 ms
10 ix-8-0-1.bb8.NewYork.Teleglobe.net (207.45.198.74) 84.792 ms 84.573 ms 85.186 ms
11 0.so-6-1-0.XL1.NYC9.ALTER.NET (152.63.22.226) 84.827 ms 85.109 ms 86.743 ms
12 0.so-7-0-0.XR1.NYC9.ALTER.NET (152.63.23.138) 85.942 ms 85.090 ms 87.532 ms
13 181.at-1-1-0.XR1.NYC1.ALTER.NET (152.63.27.102) 85.153 ms 85.036 ms 85.276 ms
14 507.ATM6-0.GW7.NYC1.ALTER.NET (152.63.25.81) 84.959 ms 85.473 ms 84.706 ms
15 nac-nyc-gw1.customer.alter.net (157.130.9.142) 98.361 ms 95.897 ms 88.128 ms

Belgium:

traceroute to meltdown.site5.com (216.118.109.201), 32 hops max, 38 byte packets
1 g4-1-0-3.c7513.science.belnet.net (193.190.199.69) 0.341 ms
2 g1-1.c12410.science.belnet.net (193.191.254.9) 0.399 ms
3 g6-0.c12008.brussels.belnet.net (193.190.197.181) 0.343 ms
4 p1-0.c7206vxr.london.belnet.net (193.191.254.22) 116.066 ms
5 core1.ltn.nac.net (195.66.224.94) 6.277 ms
6 a9-0-0-245.msfc1.oct.nac.net (209.123.11.217) 77.831 ms
7 216.118.109.201 (216.118.109.201) 78.214 ms

Germany:

traceroute to meltdown.site5.com (216.118.109.201), 30 hops max, 40 byte packets
1 fe0-0r0.ffm1.de.carpe.net (212.96.130.129) 0.937 ms 0.834 ms 0.792 ms
2 frankfurt41.de.eqip.net (195.206.67.65) 1.596 ms 1.523 ms 1.457 ms
3 frankfurt5.de.eqip.net (195.206.64.89) 1.958 ms 1.933 ms 2.049 ms
4 frankfurt50.de.eqip.net (195.206.65.149) 1.759 ms 1.767 ms 2.105 ms
5 frankfurt55.de.eqip.net (195.90.66.41) 2.425 ms 2.397 ms 2.759 ms
6 london55.gb.eqip.net (195.90.66.74) 16.112 ms 16.014 ms 15.916 ms
7 london50.gb.eqip.net (195.90.66.137) 16.543 ms 17.039 ms 17.923 ms
8 london2.gb.eqip.net (195.90.64.26) 17.097 ms 16.986 ms 17.571 ms
9 195.206.65.134 (195.206.65.134) 17.687 ms 17.208 ms 17.433 ms
10 nac-gw.thdo.bbc.co.uk (212.58.255.178) 95.925 ms 96.973 ms 95.805 ms
11 a9-0-0-245.msfc1.oct.nac.net (209.123.11.217) 98.368 ms 97.736 ms 97.515 ms
12 216.118.109.201 (216.118.109.201) 98.007 ms 98.234 ms 96.707 ms

Not bad at all.

I put some traceroutes up from various European locations last week in this thread 120ms pings (http://www.webhostingtalk.com/showthread.php?s=&threadid=57673&highlight=site5) as someone as looking for better connectivity than they currently have.

viva leFrance :)

Last year some sites I host could not be reached from Saudi. It was country wide - but all the sites were hosted from one host . It was related to routers or gateways from the Saudi proxy The hosts's site was also inacsesable so were all the stes they hosted.

I got another server from another host, moved the sites, and no more problem.

The problem lasted for over 2 weeks.

I get 80-90m/sec from the UK --> eServers/DV2 depending on which route it takes.

As for Wanadoo, yes we have contacted them on many occasions and never get any prompt or permanent fix from them; however they claim that it is our DNS, which are not setup correctly :eek:

Kind of shocks me, they don’t take it seriously and fix the issues :bawling: some time’s its working fine, others it's not :(

I've got news : I asked on forums in France to test www.eservers.biz and the net surfers who do not have Wanadoo do not have problems to reach your site, it's working.

You should talk about it with wanadoo or solve yourself this problem because Eservers loses customers here...

Ooooooh, thread resurrection. Love that search facility. :D

Well, it IS wanadoo who is at fault here - everyone I know who uses them cannot reach my server @ eservers.biz, but if they try an 'anonymiser' or proxy webserver, they are fine.

TBH my experience with Wanadoo users is they are the #1 people that try to hack my server (or were until this problem ;)).

James

Everything is ok now and we can access eservers site from France :)

Good at least afterw while you can access it.

Happy for you. Have a nice day!

Originally posted by Incognito
As more of our isp's and other providers are having financial problems and letting their maintenance slip. From my home, last weekend, I had trouble accessing yahoo, google, dotster and others. Seems XO Communications (my dsl provider) was having dns problems. I had a customer this week who couldn't access his site, because his isp had not undated the dns in spite of the fact that every whois I checked had it right. So, he kept thinking his site was down....(resolving to old address), when it was never down.

Oh my! I can related. I've had about three customers unable to access their sites, ftp, etc because of this. And they all had cable/DSL. It's so annoying!

Well, WorldCom has no effect on me... I rarely ever have a trace that goes over their network..

My PING to eservers.biz is a 126ms, from the West Coast US.