Cannot Connect to FastMail

[farmer512]

Got home and went to check mail through web interface. Won't load. Picked up my phone and tried mail client on it, nothing. Turned off wifi and tried fastmail.fm through browser on phone/cellular and it loads fine. Internet works fine for every domain I try but fastmail.fm. Anyone else w/ Time Warner experiencing the same?

[Chipper]

I'm at a library in Maryland. Couldn't access using their WiFi and my laptop. Went to one of the public PCs and can't access either.

[farmer512]

I'm in texas. Hope something can be figured out soon. Have a business that uses web interface for all our desktops.

[Webgenie]

This has been the case for about an hour, no connection through The Bat!, cannot get to fastmail.fm on the web, and have tried on both my desktop and tablet. Same connection/wifi. Am a bit alarmed as I don't see evidence of an outage here or at the status page. What gives?

[cyberpear]

I'm in New Hampshire. I can't get to fastmail, either. I'm on Comcast. Using my phone's internet, I can get to fastmail.

Traceroute doesn't get me there, either.

3 te-7-2-ur01.exeter.nh.boston.comcast.net (68.85.142.121) 15.640 ms 15.876 ms 15.883 ms
4 te-2-8-0-6-ar01.needham.ma.boston.comcast.net (68.85.37.165) 19.426 ms 22.296 ms 22.563 ms
5 he-1-12-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.90.253) 31.649 ms 31.723 ms 31.885 ms
6 * * *
7 vlan52.ebr2.NewYork2.Level3.net (4.69.138.254) 22.048 ms 22.288 ms 19.358 ms
8 ae-48-48.ebr2.NewYork1.Level3.net (4.69.201.37) 19.895 ms ae-47-47.ebr2.NewYork1.Level3.net (4.69.201.33) 18.837 ms ae-46-46.ebr2.NewYork1.Level3.net (4.69.201.29) 22.302 ms
9 ae-2-2.ebr1.Newark1.Level3.net (4.69.132.98) 18.420 ms 18.152 ms 17.883 ms
10 ae-1-51.edge2.Newark1.Level3.net (4.69.156.9) 22.670 ms 18.456 ms 18.095 ms
11 THE-NEW-YOR.edge2.Newark1.Level3.net (4.30.130.234) 18.551 ms 23.369 ms 23.032 ms
12 * * *

[Webgenie]

I'm on Wave Broadband in Northern California and can't access FastMail, either.

[farmer512]

I just remote desktop'ed into a couple local businesses w/ time warner service in the same city. I can access fastmail.fm from them.

[ellentk]

Had no trouble getting through to fastmail.fm today until about 7:30 p.m. EDT.
Can't get through on website or send email using the SMTP server. I am on
Time Warner in NYC.

[ellentk]

I haven't been able to connect for about an hour either, both to fastmail.fm and the SMTP server.

(Sorry for posting about this twice, but thought my post in the discussion about
Time Warner possibly causing this might not be noticed.)

[Webgenie]

Thanks ellentk. I found a workaround for the time being. I am using a desktop computer, and can't connect using an email client or a normal web browser at fastmail.fm. I tried the Tor browser and can connect with that on the desktop computer. I hope the issue gets fixed, as I have everything set up in The Bat! for multiple email accounts and the way I use email.

[ellentk]

Was just able to connect on my iPad. I turned off my desktop though but my iPad and desktop use the same Wi-Fi connection.

Thanks for the workaround. If this happens again I'll use Tor on my desktop.

[farmer512]

Working for me again as well.

[Webgenie]

Yes, ability to connect seems to have just restored. Hooray!

[robn]

tl;dr minor routing screwup at NYI made the whole site unavailable to a few places for a couple of hours

Bron has been at our New York datacentre this week moving all of our servers into new racks. Every single server has been physically powered down and moved in the last few days. We're actually pretty happy with how well our redundancy has worked; no one has noticed anything.

Today everything was switched over to new network routers. It appears that one of them had a broken route configured somewhere, which made our network unavailable to a small number of external networks. Unfortunately they're not ones that any of our external probes (eg pingdom) operate through, so we didn't notice.

I happened to notice because a package repository we use happens to be on that part of the network and I was unable to contact it. A few network traces discovered the problem, and to their credit the NYI engineers had the problem fixed within a couple of minutes of me reporting it.

This is an unfortunate incident, and I'm not sure exactly how we can protect against it in the future. We can certainly try to run up some basic availability tests from more places (or pay a third-party service to do it for us), but obviously we can't cover every network. We will keep talking about it because we really don't like situations where we have to fix something but don't know about it.

[Bamb0]

Im glad everything was corrected OK Rob!!

We love your service