SOTT Mail Server is down

Scottie

Scottie

Administrator
Administrator
Moderator
FOTCM Member
The SOTT Mail server has been inaccessible since about 9am this morning (Frenchie time).

According to the hosting company, the server is fine and working okay, but nobody can connect to it.

According to a tracert, packets are lost at 154.25.4.133 (or similar), which is Cogent in Washington, DC. :rolleyes:

Of course, since the SOTT Mail server is in the EU, one question is why packets within the EU are being routed via Washington, DC - although this is not unheard of since packets on the internet don't always travel from point A to point B as you would when driving in a car. Still, you'd think they'd just go via Germany, which has a monster fast network anyway.

It's been a couple of hours since our hosting company responded, and at this point I'm getting a bit suspicious. I can't find any other info about a current general Cogent outage...

:huh:
 
Trace goes all the way through for me and none of it goes via DC. I can't telnet to port 25 though, not from my desktop. But, for whatever reason, I can telnet to port 25 on sott from a server in the middle of the USA. Hmmm.
 
Oh, forgot - my ISP blocks connections to port 25. So that explains why I can't telnet to 25 from my desktop.
 
Did you try: http://mxtoolbox.com ?

mail.sott.net tests fine @ http://mxtoolbox.com site.

From my site, I tried:

$ telnet 50.7.246.162 25
Trying 50.7.246.162...
Connected to 50.7.246.162.
Escape character is '^]'.
220 mail.sott.net ESMTP Postfix (Ubuntu)
^]
telnet> ^D
Connection closed.

So I was able to reach your mail site.

On linux, I tried:

$ traceroute mail.sott.net
traceroute to mail.sott.net (50.7.246.162), 30 hops max, 60 byte packets
1 sonic.cdkkt.com (10.1.0.200) 0.463 ms 0.342 ms 0.668 ms
2 static-50-126-86-233.smrw.or.frontiernet.net (50.126.86.233) 31.625 ms 31.954 ms 31.865 ms
3 50-39-211-217.bvtn.or.frontiernet.net (50.39.211.217) 3.917 ms 4.247 ms 4.160 ms
4 ae2---0.cor02.bvtn.or.frontiernet.net (74.40.1.181) 8.634 ms 8.949 ms 8.869 ms
5 ae0---0.cor01.bvtn.or.frontiernet.net (74.40.1.185) 10.957 ms 43.596 ms 43.924 ms
6 ae4---0.cor01.sttl.wa.frontiernet.net (74.40.1.221) 11.124 ms 10.160 ms 10.063 ms
7 ae0---0.cbr01.sttl.wa.frontiernet.net (74.40.5.122) 9.975 ms 9.846 ms 9.838 ms
8 six.zayo.com (206.81.80.19) 9.745 ms 9.790 ms 14.355 ms
9 ae16.cr1.ord2.us.zip.zayo.com (64.125.21.137) 54.436 ms 55.234 ms 54.794 ms
10 ae0.cr2.ord2.us.zip.zayo.com (64.125.20.246) 52.239 ms 54.174 ms 54.488 ms
11 ae6.cr2.lga5.us.zip.zayo.com (64.125.24.29) 72.353 ms 74.433 ms 74.746 ms
12 xe-3-1-3.cr1.ams5.nl.zip.zayo.com (64.125.20.170) 152.432 ms 152.432 ms 154.004 ms
13 ae4.mpr1.fra3.de.zip.zayo.com (64.125.32.105) 154.694 ms 155.001 ms 159.593 ms
14 ae8.mpr1.fra4.de.zip.zayo.com (64.125.26.234) 154.441 ms 171.790 ms 156.732 ms
15 * * *
[...]
 
AHA!
Fascinating... that means it's our ISP here, or something between our ISP and the rest of the net!
No wonder the hosting company stopped answering my ticket requests.
SIGH...
 
It's not our ISP, because I CANNOT reach SOTT Mail from any of our other servers...
Hmm.
 
It seems a few mails are actually getting through to us now, but not all of them.

Something is seriously screwed up somewhere, that's for sure.
 
It might help to get different network testing tools websites point-of-view?
Try this one: _http://www.hq42.net/net_tools/index.php
 
fwiw traceroute from a DigitalOcean server in ny gives:

Code: 
traceroute to mail.sott.net (50.7.246.162), 30 hops max, 60 byte packets
 1  104.131.223.253 (104.131.223.253)  0.601 ms  0.619 ms  0.591 ms
 2  192.241.164.253 (192.241.164.253)  0.232 ms  2.145 ms 192.241.164.241 (192.241.164.241)  0.221 ms
 3  66.110.96.21 (66.110.96.21)  0.280 ms  0.338 ms 66.110.96.25 (66.110.96.25)  0.265 ms
 4  66.110.96.6 (66.110.96.6)  0.690 ms  0.657 ms  0.634 ms
 5  be3011.ccr21.jfk05.atlas.cogentco.com (154.54.12.17)  1.175 ms  2.303 ms  1.179 ms
 6  be2073.ccr21.jfk10.atlas.cogentco.com (154.54.0.230)  1.022 ms  0.993 ms  1.142 ms
 7  level3.ord03.atlas.cogentco.com (154.54.13.10)  0.492 ms  0.466 ms  0.457 ms
 8  ae2.cr1.lga5.us.zip.zayo.com (64.125.31.213)  0.721 ms  0.773 ms  0.729 ms
 9  ae1.cr2.lga5.us.zip.zayo.com (64.125.29.38)  0.798 ms  0.794 ms  0.759 ms
10  xe-2-0-3.cr1.ams5.nl.zip.zayo.com (64.125.20.90)  92.963 ms  92.949 ms  92.923 ms
11  ae4.mpr1.fra3.de.zip.zayo.com (64.125.32.105)  86.802 ms  93.583 ms  83.565 ms
12  ae8.mpr1.fra4.de.zip.zayo.com (64.125.26.234)  83.696 ms  83.679 ms  83.200 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  *

Never seen timeouts before, when everything is working...
 
No tracert from the Orange French provider:

1 207 ms 2 ms 3 ms livebox.home [192.168.x.x]
2 199 ms 3 ms 5 ms x.x.x.x
3 6 ms 5 ms 5 ms 10.125.118.138
4 9 ms 6 ms 5 ms 81.253.182.226
5 25 ms 21 ms 22 ms 81.253.184.114
6 18 ms 15 ms 16 ms be3011.agr21.fra03.atlas.cogentco.com [130.117.15.1]
7 202 ms 20 ms 18 ms telia.fra03.atlas.cogentco.com [130.117.14.214]
8 347 ms 204 ms 102 ms 94.31.40.214.IPYX-077661-ZYO.above.net [94.31.40.214]
9 * * * Délai d'attente de la demande dépassé.
10 * * * Délai d'attente de la demande dépassé.
11 * * * Délai d'attente de la demande dépassé.
12 * * * Délai d'attente de la demande dépassé.
13 * * * Délai d'attente de la demande dépassé.
14 * * * Délai d'attente de la demande dépassé.

And

telnet mail.sott.net 110

does not respond.
 
Eclipse said:
[...]
telnet mail.sott.net 110
Click to expand...

Port 110 is an POP/IMAP server and may or may not be enabled (it does not work for me),
and port 25 is the SMTP (email) Server. Can you reach port 25?
 
FWIW, I can't reach mail.sott.net from my laptop (Australia/Brisbane) after 30 hops. Below is the traceroute output.

Code: 
traceroute to mail.sott.net (50.7.246.162), 30 hops max, 60 byte packets
 1  192.168.43.1 (192.168.43.1)  1.134 ms  1.215 ms  1.661 ms
 2  169.254.80.23 (169.254.80.23)  91.506 ms  91.598 ms  91.852 ms
 3  172.24.178.89 (172.24.178.89)  100.229 ms  103.217 ms  103.303 ms
 4  * * *
 5  * * *
 6  * 172.22.85.196 (172.22.85.196)  73.754 ms *
 7  * 172.22.85.195 (172.22.85.195)  1843.168 ms *
 8  172.22.85.212 (172.22.85.212)  1843.172 ms  1843.170 ms 172.22.85.204 (172.22.85.204)  1843.168 ms
 9  172.22.85.195 (172.22.85.195)  1843.155 ms  204.416 ms *
10  198.142.255.214 (198.142.255.214)  204.350 ms  204.381 ms  204.387 ms
11  * * *
12  198.142.255.214 (198.142.255.214)  204.351 ms  204.361 ms 198.142.255.22 (198.142.255.22)  204.348 ms
13  * * *
14  211.29.125.201 (211.29.125.201)  204.465 ms 210.49.49.153 (210.49.49.153)  204.499 ms  204.489 ms
15  198.142.139.116 (198.142.139.116)  204.464 ms * 198.142.139.118 (198.142.139.118)  204.424 ms
16  198.142.139.132 (198.142.139.132)  204.625 ms 198.142.139.134 (198.142.139.134)  204.534 ms  204.555 ms
17  198.142.139.116 (198.142.139.116)  204.552 ms 203.208.192.161 (203.208.192.161)  259.117 ms 198.142.139.116 (198.142.139.116)  68.291 ms
18  203.208.172.213 (203.208.172.213)  409.572 ms te0-7-0-3.ccr21.lax04.atlas.cogentco.com (154.54.12.129)  409.589 ms 198.142.139.132 (198.142.139.132)  68.400 ms
19  be2019.ccr21.lax01.atlas.cogentco.com (154.54.88.9)  355.060 ms 203.208.190.137 (203.208.190.137)  341.187 ms be2017.ccr22.lax01.atlas.cogentco.com (154.54.0.238)  341.090 ms
20  be2019.ccr21.lax01.atlas.cogentco.com (154.54.88.9)  409.548 ms  409.550 ms be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82)  409.528 ms
21  be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  409.506 ms te0-7-0-3.ccr21.lax04.atlas.cogentco.com (154.54.12.129)  409.484 ms be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81)  296.254 ms
22  be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  296.207 ms  296.156 ms be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82)  296.184 ms
23  be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81)  296.164 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  307.067 ms be2180.ccr21.lax01.atlas.cogentco.com (154.54.41.57)  307.010 ms
24  be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81)  307.003 ms  306.942 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  306.966 ms
25  be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81)  307.022 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  306.973 ms  306.909 ms
26  be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82)  306.934 ms  306.929 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  306.979 ms
27  be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82)  306.960 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  306.949 ms be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81)  306.940 ms
28  be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  306.932 ms  306.958 ms be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82)  306.922 ms
29  be2179.ccr22.lax01.atlas.cogentco.com (154.54.41.81)  306.909 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  306.895 ms be2180.ccr21.lax01.atlas.cogentco.com (154.54.41.57)  306.881 ms
30  be2179.ccr23.lax05.atlas.cogentco.com (154.54.41.82)  307.074 ms  307.069 ms be2180.ccr23.lax05.atlas.cogentco.com (154.54.41.58)  307.060 ms
 
@ Bobo08: since you have a lot more hops, you can increase the max_ttl:

-m max_ttl
Specifies the maximum number of hops (max time-to-live value)
traceroute will probe. The default is 30.

So try a bigger number such as: traceroute -m 50 mail.sott.net
 
Another 3 hours have passed, and still no reply from the hosting company. They also managed to screw up and overcharge us almost $800 for a server I canceled in September.

_http://fdcservers.net :ban:

Even if the problem isn't their fault, the least they could do is tell us SOMETHING, especially given the little billing screw-up. I pointed this out, and still nothing.

:mad:
 
http://www.sott.net

They say the squeaky wheel gets the grease, so perhaps we should all start squeaking loudly?

:halo:
 
You must log in or register to reply here.
Back
Top Bottom