Related

Tool [NEW] Bandwidth Pricing Calculator Tool
Changed ipaddress of a droplet Question Question
No connection after reboot Question Question

Question

I think OVH is blocking all of Digital Ocean's IP addresses

Posted January 17, 2017 5.9k views
Networking

I’ve tried with 3 different droplets, each in a different location, to reach OVH’s servers (for sending mails, I use them as an SMTP provider) and every time, the connection just seems to be blocked.

I can’t even ping anything from OVH (not only their SMTP service).

I have been trying from :

  • AMS2
  • FRA1
  • LON1

I can not find anything online documenting this issue. Does anyone know is there’s a way to around this issue ?

It has huge consequences because OVH is a pretty big hosting provider in EU and so is Digital Ocean. It means you can’t have any service at Digital Ocean communicating with any service at OVH. Both parties must be aware of that. Why isn’t it documented anywhere ?

Thanks

Add a comment
benjamincoleman
By:
benjamincoleman

Related

Tool [NEW] Bandwidth Pricing Calculator Tool
Changed ipaddress of a droplet Question Question
No connection after reboot Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
4 answers
ryanpq January 17, 2017

Please open a ticket with our support team so we can investigate this. It is the first I have heard about any routing issue between OVH and DO.

Reply Report
mat2b January 17, 2017

What IP address you trying ? (src and dst)

can you try proof.ovh.ca if you’re able to ping it ?

can you send a traceroute from the source to destination (and proof.ovh.ca) ?

Thanks

Reply Report
  • benjamincoleman January 17, 2017

    I can’t share the source IPs publicly.

    However, I can ping proof.ovh.ca and proof.ovh.net. I can not ping ovh.net. I have a couple services at OVH (shared web hosting & dedicated server) and I can’t ping any of those. I can’t ping ovh.net (DNS resolves, then packets are 100% lost).

    The service I’m actually trying to connect to for real purposes here is hosted at ssl0.ovh.net and I can not ping that either. A traceroute to this address yelds :

    traceroute to ssl0.ovh.net (213.186.33.20), 30 hops max, 60 byte packets
 1  37.139.0.254 (37.139.0.254)  1.108 ms  0.864 ms  0.979 ms
 2  138.197.250.26 (138.197.250.26)  7.658 ms  7.642 ms  7.617 ms
 3  * 138.197.250.8 (138.197.250.8)  0.802 ms *
 4  * * *
 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  * * *

    With proof.ovh.net, I get :

    traceroute to proof.ovh.net (188.165.12.106), 30 hops max, 60 byte packets
 1  37.139.0.254 (37.139.0.254)  1.356 ms  1.244 ms  1.178 ms
 2  138.197.250.20 (138.197.250.20)  1.131 ms 138.197.250.26 (138.197.250.26)  0.995 ms 138.197.250.28 (138.197.250.28)  0.944 ms
 3  * 138.197.250.8 (138.197.250.8)  0.834 ms 138.197.250.6 (138.197.250.6)  0.728 ms
 4  * be10-1185.rbx-g2-a9.fr.eu (94.23.122.78)  8.546 ms *
 5  be10-1185.rbx-g2-a9.fr.eu (94.23.122.78)  8.882 ms vl20.rbx-g2-a75.fr.eu (188.165.9.95)  9.226 ms  9.206 ms
 6  vl20.rbx-g2-a75.fr.eu (188.165.9.95)  9.144 ms po9.rbx-s4-6k.fr.eu (178.33.100.134)  9.221 ms vl20.rbx-g2-a75.fr.eu (188.165.9.95)  9.219 ms
 7  * po9.rbx-s4-6k.fr.eu (178.33.100.134)  9.223 ms *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

    And, finally, with proof.ovh.ca :

    traceroute to proof.ovh.ca (192.99.19.165), 30 hops max, 60 byte packets
 1  37.139.0.254 (37.139.0.254)  0.632 ms  0.626 ms  0.670 ms
 2  138.197.250.28 (138.197.250.28)  0.456 ms  0.421 ms 138.197.250.20 (138.197.250.20)  0.356 ms
 3  * 138.197.250.8 (138.197.250.8)  0.327 ms 138.197.250.6 (138.197.250.6)  0.336 ms
 4  be10-1185.rbx-g2-a9.fr.eu (94.23.122.78)  8.019 ms  8.565 ms *
 5  be100-1188.ldn-5-a9.uk.eu (91.121.128.89)  9.316 ms  9.786 ms be10-1185.rbx-g2-a9.fr.eu (94.23.122.78)  8.240 ms
 6  be100-1298.nwk-5-a9.nj.us (192.99.146.133)  76.946 ms  78.231 ms be100-1188.ldn-5-a9.uk.eu (91.121.128.89)  9.787 ms
 7  be10-1018.bhs-g2-a9.qc.ca (192.99.146.101)  87.201 ms  87.298 ms  87.733 ms
 8  vl20.bhs-g2-a75-lo2.qc.ca (192.99.146.51)  86.310 ms be10-1018.bhs-g2-a9.qc.ca (192.99.146.101)  87.885 ms  88.250 ms
 9  vl20.bhs-g2-a75-lo2.qc.ca (192.99.146.51)  86.465 ms  86.608 ms *
10  be50-7.bhs-3b-a9.qc.ca (198.27.73.98)  332.842 ms * be50-7.bhs-3a-a9.qc.ca (198.27.73.94)  321.361 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
    Reply Report
mat2b January 17, 2017

Hrmm at least with your gateway, it seem to work.

1.|– 192.99.19.252 0.0% 10 180.3 179.0 146.1 245.1 33.2
2.|– po111.bhs-g1-a75.qc.ca 0.0% 10 0.2 0.2 0.2 0.2 0.0
3.|– 10.95.81.8 0.0% 10 2.4 2.4 2.3 2.5 0.1
4.|– be100-1319.nwk-1-a9.nj.us 0.0% 10 9.0 9.1 8.9 9.3 0.1
5.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
6.|– nyk-bb4-link.telia.net 0.0% 10 9.0 9.3 9.0 9.5 0.1
7.|– ldn-bb2-link.telia.net 10.0% 10 78.5 100.6 78.5 173.2 36.9
8.|– adm-bb4-link.telia.net 0.0% 10 82.9 83.9 82.9 86.3 1.1
| `|– 62.115.134.26
| |– 213.155.136.83
| |– 62.115.136.194
| |– 213.155.136.93
| |– 213.155.136.79
| |– 62.115.142.221
| |– 213.155.136.91
9.|– adm-b2-link.telia.net 0.0% 10 84.6 85.5 84.6 87.4 0.9
10.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|– ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|– 37.139.0.254 10.0% 10 88.8 88.1 86.0 90.9 1.8

Without telling me the source, are you part of 37.139.0.0/19 ? (at least can you give me the subnet?)

Reply Report
  • benjamincoleman January 17, 2017

    Yes, I’m part of the 37.139.0.0/19 subnet, 37.139.3.0/24 actually. But, as I mentioned, I tried from 3 different droplets, in 3 different regions with the same results. So I think the problem happens at a higher level than that.

    Reply Report
mat2b January 17, 2017

Yup, you’ll need to contact digitalocean. they seem to filter some packet but cannot confirm.

I can ping 37.139.3.23 and 37.139.0.23 (random ips) and they both working from OVH (EU/CA).

Sorry not being helpful.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help