Hi Mike

Thanks for your reply.

I don't think the issue was in Glattbrugg, sounds like a coincidence. Also, the outage was for ~50 minutes, until the routing changed. Find below two screenshots from mtr running during the problems. At 14:39 the hops after Swisscom went to NTT. At 14:50 it changed to several others, even telia. http://www.claudiokuenzler.com/media/mtr-1439.png http://www.claudiokuenzler.com/media/mtr-1450.png

Anyone from Swisscom able to tell some details?

thanks

On Tue, Oct 11, 2016 at 10:55 AM, Mike Kellenberger < mike.kellenberger@escapenet.ch> wrote:

Hi Claudio

Our monitoring systems detected a short power outage on one of the power feeds in the Interxion datacenter in Glattbrugg exactly in that timeframe. Maybe these incidents were connected? A device with a single power supply maybe?

Regards,

Mike

-- Mike Kellenberger | Escapenet GmbH www.escapenet.ch +41 52 235 0700/04 Skype mikek70atwork

On 11.10.2016 08:51, Claudio Kuenzler wrote:

...

Hello all,

I'd like to know if anyone else experienced routing problems yesterday on October 10th 2016 from Swisscom networks to Amazon AWS (Ireland). We've had our server connections cut between 1400 and 1450. I'm pretty sure the problem was with NTT, which was the next hop after Swisscom.

At 1450 someone (Swisscom or AWS?) changed the routing and the next hop after Swisscom changed to DTAG.

Does anyone have more insights who "fixed" it yesterday? Swisscom only responded to our incident ticket that "Amazon uses loadbalancers and therefore several destination ip addresses" and "traceroute has changed since your screenshot" which is not helpful at all.

Thanks in advance for any information.

ck

---

swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

---

swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog