for what it’s worth, most of the incidents listed on the status page are just a byproduct of the global internet not being as stable as one would imagine.
a lot of PaaS/IaaS, while having services across the world, mostly run regions independently from each other; and, while a Fly app running in ams will certainly keep working if sin has flaky network, a client in Singapore will have a hard time connecting to that app - or, an app replicating a database between lax and syd would probably not be able to do that very well if a shark ate a subsea cable again.
people run lots of different kinds of apps on the platform; most incidents only impact a subset of customers. it’s possible, I won’t say easy, to architecture a global app to work around these issues; but we’re happy to help with it. single-region (or couple-nearby-regions) apps will be just fine.
not to say we haven’t had outages for entirely-us reasons! a lot of those tend to be one-time things we learn a lot from.
I wrote something similar to lubien recently here regarding that, notably: