Some apps down with timeouts for last 8 hours in the FRA region (egress IP)

Questions / Help
1

4 of my 6 apps in the FRA region are down with a connection timeout error (Socket timeout, unable to connect to server). The first three came down at 5 am UTC, now another one came down at 2:20 pm UTC. I emailed Support at 7 am UTC, I have still not heard from them. The issue came on suddenly, I assume they are doing some network maintenance work in the background, which failed.

Is anyone else facing this issue or has recommendations on what to do? I am quite frustrated, we had a similar issue just 2 weeks ago which support in the end fixed for us (they changed a third party provider which made the egress IP feature not work). I am starting to worry about fly’s reliability.

2

Who was/is the third-party provider?

Can you shell into the apps that are down? (Network test)

If you can shell into downed apps, can you see if the listener is alive in each case?

Can you launch a demo app in FRA and then reach it?

3

that’s referring to one of our upstreams not supporting a feature we need for static egress IPs; we’ve set up a workaround so it does work now.

1 Like
4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.