Barracuda ESS and Cloud Protection Layer global outage
08:55:31 Tue Dec 23 $ telnet d61692a.ess.barracudanetworks.com 25 Trying 64.235.150.197... telnet: connect to address 64.235.150.197: Connection refused Trying 64.235.154.66... telnet: connect to address 64.235.154.66: Connection refused telnet: Unable to connect to remote host
From web site sales chat:
" There is an outage with ESS and cloud protection layer affecting our customers globally at the moment our engineering team are working to fix this issue right now we do not have any ETA's at the moment " Since "early this morning" -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org
Hi Scott, On 23 December 2014 at 07:20, Scott Lambert via Outages <outages@outages.org> wrote:
08:55:31 Tue Dec 23 $ telnet d61692a.ess.barracudanetworks.com 25 Trying 64.235.150.197... telnet: connect to address 64.235.150.197: Connection refused Trying 64.235.154.66... telnet: connect to address 64.235.154.66: Connection refused telnet: Unable to connect to remote host
From web site sales chat:
" There is an outage with ESS and cloud protection layer affecting our customers globally at the moment our engineering team are working to fix this issue right now we do not have any ETA's at the moment
I don't use this barracuda product but I do use another so when I logged into https://login.barracudanetworks.com/auth/login/ I saw this message: The Barracuda Email Security Service is currently experiencing delays in email traffic for a segment of our customers. We are actively working to resolve the issue and will provide further updates here[0]. If you are experiencing delays, please file a support ticket here[1].
"
Since "early this morning"
-- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org
[0] https://community.barracudanetworks.com/ [1] You'll need to be logged in to create a new case. -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si
Just got your message, 11 hours later. =) We saw the issue start Monday at 4:30 pm U.S. Central. Our email server logs noted: Open (64.235.150.197) Error 21sec (399 TCP Read failed (Connection timed out after 0 seconds) 0 sec) A few messages delivered Monday evening (last one was 6:46 am), but they were at a stand-still this morning. More here: https://www.reddit.com/r/sysadmin/comments/2q6f3c/barracuda_spam_service_dow n https://www.reddit.com/r/sysadmin/comments/2q7buu/barracuda_email_security_s ervice_outage/ https://twitter.com/barracuda?lang=en&lang=en It appears that Barracuda didn't really dig in until this morning, at which time they changed host IPs so that customers using their host as the domain's MX record automatically would get the new IP (TTL-depending). More on mailops, too. Frank -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Scott Lambert via Outages Sent: Tuesday, December 23, 2014 9:21 AM To: outages@outages.org Subject: [outages] Barracuda ESS and Cloud Protection Layer global outage 08:55:31 Tue Dec 23 $ telnet d61692a.ess.barracudanetworks.com 25 Trying 64.235.150.197... telnet: connect to address 64.235.150.197: Connection refused Trying 64.235.154.66... telnet: connect to address 64.235.154.66: Connection refused telnet: Unable to connect to remote host
From web site sales chat:
" There is an outage with ESS and cloud protection layer affecting our customers globally at the moment our engineering team are working to fix this issue right now we do not have any ETA's at the moment " Since "early this morning" -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Frank Bulk -
jungle Boogie -
Scott Lambert