# How is reliability?

**URL:** <https://community.fly.io/t/how-is-reliability/26615>\
**Category:** General\
**Tags:** login-only\
**Created:** [December 11, 2025, 4:20am UTC](https://community.fly.io/t/how-is-reliability/26615 "2025-12-11T04:20:14Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![lillian](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lillian/32/49616_2.png) [@lillian](https://community.fly.io/u/lillian)\
**Post date:** [December 11, 2025, 2:45pm UTC](https://community.fly.io/t/how-is-reliability/26615/4 "2025-12-11T14:45:58Z")

</div>

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](https://community.fly.io/t/how-to-have-less-breakages-in-the-complex-fly-ecosystem/26485/3) regarding that, notably:

> [@How to have less breakages in the complex Fly ecosystem?](https://community.fly.io/t/how-to-have-less-breakages-in-the-complex-fly-ecosystem/26485/3):
>
> we’re slowly replacing legacy systems with newer ones that fit the platform better - this trades long-term structural brokenness (or latency/complexity/unreliability, etc) for more obvious short-term brokenness after which the new system will work well.  
> at least that’s our hope!

---

_[View the full topic](https://community.fly.io/t/how-is-reliability/26615)._
