OVH Community, your new community space.

Anyone having routing problems from their servers today?


turbanator
22-08-2009, 23:29
http://translate.google.com/translat...istory_state0=

mvegetto
22-08-2009, 23:06
Indeed so!!!, it stressed me out aswell. Good job Oles, the netherlands owe you a lot!

ig0r
22-08-2009, 23:03
Many thanks Oles - my day of stress is finally over lol

turbanator
22-08-2009, 22:57
Quote Originally Posted by mvegetto
Everything is back to normal now, just 1 min ago after oles said it was fixed.
YES LOOKS LIKE ITS FIXED FOR NOW I HOPE I DONT JINX IT

mvegetto
22-08-2009, 22:55
Everything is back to normal now, just 1 min ago after oles said it was fixed.

turbanator
22-08-2009, 22:50
Nothing is fixed Oles! trying to connect to some NL ips and its timing out! PLEASE fix

turbanator
22-08-2009, 22:49
traceroute to leaseweb.com (83.149.80.111), 30 hops max, 60 byte packets
1 94.23.6.254 (94.23.6.254) 1.024 ms * *
2 * * *
3 * * *
4 hosted.by.leaseweb.com (85.17.100.202) 8.482 ms * *
5 * * *
6 * www.leaseweb.com (83.149.80.111) 6.843 ms 6.354 ms


1 94.23.6.254 (94.23.6.254) 1.873 ms * *
2 * * *
3 * * *
4 10g.p19-52-6k.routers.chtix.eu (213.186.32.230) 4.212 ms * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

1 94.23.6.254 (94.23.6.254) 1.842 ms * *
2 * * *
3 * * *
4 hosted.by.leaseweb.com (94.75.255.58) 6.299 ms * *
5 * * *
6 * * *
7 xxxxxxxxxxxxxx.com (xx.xxx.xx.xxx) 14.722 ms 14.736 ms 14.706 ms

mvegetto
22-08-2009, 22:46
it's now FIXED, I can reach my server and websites, thx OVH!

turbanator
22-08-2009, 22:45
nothing is fixed oles

[L] 150 File status okay; about to open data connection from 1
[L] 426- connect timed out
[L] 426 connect timed out
[L] ABOR

that si trying to downalod via ftp from LW server

turbanator
22-08-2009, 22:39
i am able to reach all those websites..from my kimsufi server

are u talking abt refresh times while accessing from a NL server?

oles@ovh.net
22-08-2009, 22:38

fixed

http://travaux.ovh.com/?do=details&id=3322


mvegetto
22-08-2009, 22:19
What is also interesting is:

OVH.nl is reachable perfect
OVH.co.uk can't be reached from NL
forum.ovh.co.uk, 10 times refresh is needed
forum.ovh.nl, 10 times refresh is needed.

mvegetto
22-08-2009, 22:17
OVH at NL is also having a topic with a lot of people pasting the trace routs, hopefully it will get sorted out this weekend.

turbanator
22-08-2009, 22:06
Quote Originally Posted by derchris
No problems in the UK:
what u talking abt?

traceroute to www.ovh.co.uk (87.98.255.34), 30 hops max, 60 byte packets
1 94.23.6.254 (94.23.6.254) 17.513 ms * *
2 * * *
3 80g.p19-7-6k.routers.chtix.eu (213.186.32.133) 4.288 ms * *
4 10g.p19-52-6k.routers.chtix.eu (213.186.32.230) 4.192 ms * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

derchris
22-08-2009, 21:50
No problems in the UK:

3 102 ms 111 ms 121 ms 10.1.3.50
4 115 ms 117 ms 99 ms sw1.tc.lon.ovh.net [195.66.224.220]
5 127 ms * 114 ms 20g.vss-1-6k.routers.chtix.eu [94.23.122.66]
6 106 ms 102 ms 110 ms ns204531.ovh.net [94.23.9.139]

mvegetto
22-08-2009, 21:05
I also have the same problem!!!! it started 2:16 PM

Tracing route to ns204531.ovh.net [94.23.9.139]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms m0n0wall.local [192.168.1.1]
2 6 ms 7 ms 7 ms 5355B801.cable.casema.nl [83.85.184.1]
3 49 ms 9 ms 7 ms mnd-rc0001-cr101-ae11-212.core.as9143.net [213.5
1.162.161]
4 12 ms 11 ms 7 ms asd-lc0006-cr101-ae7-0.core.as9143.net [213.51.1
58.2]
5 15 ms * 14 ms amsix.routers.ovh.net [195.69.145.231]
6 19 ms * 19 ms 20g.vss-1-6k.routers.chtix.eu [94.23.122.70]
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.


OVH should hurry up fixing this, NL isn't happy atm!

Neil
22-08-2009, 20:35
Quote Originally Posted by monkey56657
Neil is visiting the forum out of the goodness of his heart
England are about to win the ashes , thought it would pop in as it has just finished for day 3.

freshwire
22-08-2009, 20:34
Neil is visiting the forum out of the goodness of his heart

Neil
22-08-2009, 20:29
Thank you for the traceroutes, I have passed them on just now so they are aware of the situation if they weren't.

turbanator
22-08-2009, 19:29
i have an old kimi ig0r connection times out too to a couple of NL servers :/

2 20g.ams-1-6k.routers.chtix.eu (94.23.122.69) 5.808 ms * *
3 * * *
4 * * *
5 * * *
6 * * *
7 wildeyeentertainment.com (95.211.96.245) 9.221 ms 9.223 ms 9.208 ms

traceroute to leaseweb.com (83.149.80.111), 30 hops max, 60 byte packets
1 94.23.6.254 (94.23.6.254) 0.344 ms * *
2 20g.ams-1-6k.routers.chtix.eu (94.23.122.69) 5.626 ms * *
3 * * *
4 * * *
5 * * *
6 * www.leaseweb.com (83.149.80.111) 6.388 ms 6.633 ms

1 94.23.6.254 (94.23.6.254) 0.811 ms * *
2 20g.ldn-1-6k.routers.chtix.eu (94.23.122.65) 3.998 ms * *
3 * * *
4 * * *
5 * * *
6 * 72.14.233.114 (72.14.233.114) 16.636 ms 16.423 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * ew-in-f104.google.com (74.125.77.104) 15.334 ms


FAIL FAIL FAIL on my kimsufi!

1 94.23.6.254 (94.23.6.254) 0.990 ms * *
2 * * *
3 * * *
4 10g.p19-52-6k.routers.chtix.eu (213.186.32.230) 4.219 ms * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * *

traceroute to nforce.nl (85.17.52.226), 30 hops max, 60 byte packets
1 94.23.6.254 (94.23.6.254) 14.256 ms * *
2 20g.ams-1-6k.routers.chtix.eu (94.23.122.69) 5.842 ms * *
3 crs-tc2.leaseweb.net (195.69.144.215) 6.376 ms 6.382 ms 6.383 ms
4 te1-4.sr1.esy.leaseweb.net (62.212.80.102) 6.232 ms 6.333 ms 6.375 ms
5 * * *
6 shop.nforce.nl (85.17.52.226) 6.187 ms 6.264 ms 6.250 ms

traceroute to ovh.nl (94.23.151.34), 30 hops max, 60 byte packets
1 94.23.6.254 (94.23.6.254) 0.674 ms * *
2 * * *
3 * * *
4 10g.p19-52-6k.routers.chtix.eu (213.186.32.230) 4.258 ms * *
5 * * *
6 * 94.23.151.34 (94.23.151.34) 4.269 ms 4.480 ms

mimi2008
22-08-2009, 19:29
I am having the issues with 2 storage servers

ig0r
22-08-2009, 19:21
From all the servers I manage for clients plus my own ovh PRO - its only these 2 6tb storeage servers that Im having problems with , all the others are fine. None of the servers are Kimsufis- all are OVH servers. One of the 6tb storeage servers is only about 5 months old.

mimi2008
22-08-2009, 19:18
it just seems weird that the older kimi/ovh servers i have are having the problems, but the new range are fine

ig0r
22-08-2009, 19:15
Absolutely no idea - at this point we need OVH staffs help to look into/fix this as its confirmed theres an issue. If theres whole parts of the interwebs these servers cant connect to- then it effectively makes these servers a waste of money

Credit to OVH though - they are usually very good at sorting problems - we just picked a bad day (the weekend) to discover problems lol

mimi2008
22-08-2009, 19:10
so do we know what the issue is then?

ig0r
22-08-2009, 18:47
strangely ovh.nl tracerts, ovh.co.uk doesnt,ovh.com doesnt
and most importantly - icanhascheezburger.com fails- if ovh cannot correctly supply lolcats - then its the end of the world as we know it and OVH should refund all affected servers with 2 years rental and a free lolcat pack!!

freshwire
22-08-2009, 18:26
Curious. tracert from me to ovh.com fails.

Website loads fine though.

mimi2008
22-08-2009, 18:15
Yes i am having the same issues, also on my desktop servers i cant go to certain websites

ig0r
22-08-2009, 18:12
tracerts from my pro server to either of the servers = works
tracert from my pro server to nl =works
tracert from either of the affected servers to my pro/other ovhs =fail
tracert from either of the affected servers to nl = fail

The affected servers arent linked in any way and both seem to have started failing at about the same time from what I can see - about 1pm gmt

Come on OVH - fix it :P


*@*:~$ traceroute ovh.com
traceroute to ovh.com (213.186.33.34), 30 hops max, 40 byte packets
1 94.23.*.* (94.23.*.*) 0.854 ms * *
2 * * *
3 80g.p19-7-6k.routers.chtix.eu (213.186.32.133) 4.183 ms * *
4 10g.p19-52-6k.routers.chtix.eu (213.186.32.230) 4.275 ms * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

all aboard the phail bus !!!- its bad when an ovh cant even tracert to ..ovh lol

mimi2008
22-08-2009, 18:04
I am getting this on 1 of mine:

freshwire
22-08-2009, 18:03
Regarding why the message in a bottle didn't say it worked (when it did) is because it seems I have deleted one of the files

ig0r
22-08-2009, 18:03
traceroute to myxcp.net 30 hops max, 40 byte packets
1 *.*.*.* (*.*.*.*) 1.152 ms * *
2 40g.rbx-1-6k.routers.chtix.eu (213.251.128.25) 3.840 ms * *
3 rbx-53-m1.routers.chtix.eu (91.121.130.31) 0.389 ms 0.497 ms 0.492 ms
4 sv2.myxcp.net 0.234 ms 0.227 ms 0.220 ms


works fine to you

freshwire
22-08-2009, 17:59
Code:
 1  rbx-53-m2.routers.ovh.net (91.121.175.252)  0.324 ms  0.379 ms  0.448 ms
 2  91.121.130.130 (91.121.130.130)  7.652 ms * *
 3  xx.xx.xx.xxx (xx.xx.xx.xxx)  1.049 ms  1.149 ms  1.374 ms
Code:
 1  rbx-53-m2.routers.ovh.net (91.121.175.252)  0.342 ms  0.398 ms  0.469 ms
 2  91.121.130.1 (91.121.130.1)  0.972 ms * *
 3  40g.vss-1-6k.routers.chtix.eu (213.251.128.26)  0.621 ms * *
 4  zzxxxxxx.ovh.net (xx.xx.xx.xx)  0.375 ms  0.381 ms  0.377 ms
Strange Works fine. Can you trace to me: myxcp.net

Also I got your message in a bottle twice

ig0r
22-08-2009, 17:57
clicked on launch on your link with the message - it didnt do anything so no idea if it went through to you monkey56667 - thanks for your help

Tz-OVH
22-08-2009, 17:57
Tracing route to leaseweb.nl [83.149.80.111]
over a maximum of 30 hops:

1 11 ms * <1 ms 94.23.28.254
2 116 ms 6 ms * 20g.ams-1-6k.routers.chtix.eu [94.23.122.69]
3 9 ms 8 ms 13 ms 195.69.145.215
4 10 ms 8 ms 13 ms hosted.by.leaseweb.com [85.17.100.202]
5 * 6 ms * 83.149.80.111
6 20 ms * * www.leaseweb.com [83.149.80.111]
7 * * * Request timed out.
8 * 6 ms * www.leaseweb.com [83.149.80.111]
9 * * * Request timed out.
10 * 6 ms * www.leaseweb.com [83.149.80.111]
11 * * * Request timed out.
12 * * 6 ms www.leaseweb.com [83.149.80.111]

Trace complete.

Tracing route to nforce.nl [85.17.52.226]
over a maximum of 30 hops:

1 25 ms * * 94.23.28.254
2 9 ms 5 ms * 20g.ams-1-6k.routers.chtix.eu [94.23.122.69]
3 8 ms 8 ms 9 ms 195.69.145.215
4 6 ms 6 ms 13 ms te1-1.sr1.esy.leaseweb.net [85.17.100.150]
5 9 ms 6 ms 6 ms 85.17.96.225
6 * * * Request timed out.
7 * * * Request timed out.
8 * * 6 ms shop.nforce.nl [85.17.52.226]

Trace complete.
From mine, SP Best of.

freshwire
22-08-2009, 17:54
OVH forum doesn't have PM support?

http://contact.thepike.co.uk/mail.php

ig0r
22-08-2009, 17:52
yea one min and Ill pm you the ips monkey56657

mimi2008
22-08-2009, 17:52
I am also getting these issues on a few servers

freshwire
22-08-2009, 17:51
Code:
traceroute to leaseweb.nl (83.149.80.111), 30 hops max, 60 byte packets
 1  rbx-53-m2.routers.ovh.net (91.121.175.252)  0.273 ms  0.342 ms  0.410 ms
 2  91.121.130.130 (91.121.130.130)  0.312 ms * *
 3  40g.ams-1-6k.routers.chtix.eu (91.121.131.10)  122.538 ms * *
 4  crs-tc2.leaseweb.net (195.69.144.215)  6.375 ms  6.382 ms  6.379 ms
 5  * * *
 6  www.leaseweb.com (83.149.80.111)  6.065 ms  6.303 ms *
Shall I traceroute to one of your affected servers ? That should fail right ?

ig0r
22-08-2009, 17:47
I tried leaseweb.nl / worldstream.nl / nforce.nl - basically just nl hosting companys I could easily think of lol .

freshwire
22-08-2009, 17:40
Code:
 1  rbx-53-m2.routers.ovh.net (91.121.175.252)  0.384 ms  0.454 ms  0.516 ms
 2  91.121.130.1 (91.121.130.1)  4.536 ms * *
 3  40g.ams-1-6k.routers.chtix.eu (213.251.130.66)  45.706 ms * *
 4  openpeering.nikhef.nl-ix.net (193.239.116.17)  5.791 ms  5.935 ms  6.060 ms
 5  openpeering.eunetworks.cj2.nl (213.207.6.3)  9.068 ms  9.147 ms  9.411 ms
 6  expathos.eu (194.50.163.175)  8.725 ms  9.001 ms  9.055 ms
Any specific host OVH/NL to traceroute? I just found that one in google.

derchris
22-08-2009, 17:07
No problems here.

ig0r
22-08-2009, 17:02
Just a query - been asked to check on 2 clients servers .
Both have exactly the same problems
traceroutes to other OVH servers fail (as do any connections)
traceroutes to NL fail (as do any connections)
traceroutes to google.co.uk .......work fine.....
Both of these are 6 tb storage servers.
Testing from my own (old) 750 gb PRO server - traceroutes are fine - maybe a router error somewhere....

To holland:
2 20g.ams-1-6k.routers.chtix.eu (94.23.122.69) 6.819 ms * *
3 * * *
4 * * *
5 * * *
6 * * *
etc till fail

To ovh:
2 40g.rbx-1-6k.routers.chtix.eu (213.251.128.25) 1.552 ms * *
3 rbx-17-m1.routers.ovh.net (213.251.191.46) 0.782 ms 1.019 ms 1.255 ms
4 * * *
5 * * *
6 * * *
etc till fail

to google.co.uk:
2 20g.ldn-1-6k.routers.chtix.eu (94.23.122.65) 4.043 ms 4.062 ms 4.056 ms
3 195.66.224.125 (195.66.224.125) 7.510 ms 7.522 ms 7.516 ms
4 64.233.175.27 (64.233.175.27) 11.167 ms 11.955 ms 11.158 ms
5 209.85.251.190 (209.85.251.190) 19.007 ms 209.85.250.216 (209.85.250.216) 22.931 ms 209.85.251.190 (209.85.251.190) 19.009 ms
6 66.249.95.164 (66.249.95.164) 19.122 ms 16.316 ms 66.249.95.169 (66.249.95.169) 16.422 ms
7 216.239.49.126 (216.239.49.126) 25.762 ms 25.727 ms 25.742 ms
8 gv-in-f104.google.com (216.239.59.104) 18.497 ms 16.391 ms 16.631 ms
WINNER!!!

So anyone at ovh willing to check whats up with the 6tb storeage servers?
I did check ovh travaux - but nothing listed

Edit: Just ran some checks - it just seems to be the whole of NL and the whole of OVH that is screwed from/to these servers- Got someone to traceroute back from worldstream.nl as well - and the servers are unreacheable, try from uk/de etc - fine - no problems