# Frequent outages is really demonstrating fly is not production ready yet **URL:** \ **Category:** General\ **Tags:** issue, login-only\ **Created:** [March 15, 2023, 11:16pm UTC](https://community.fly.io/t/frequent-outages-is-really-demonstrating-fly-is-not-production-ready-yet/11502 "2023-03-15T23:16:05Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![kurt](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/kurt/32/43757_2.png) [@kurt](https://community.fly.io/u/kurt)\ **Post date:** [March 16, 2023, 12:16am UTC](https://community.fly.io/t/frequent-outages-is-really-demonstrating-fly-is-not-production-ready-yet/11502/3 "2023-03-16T00:16:38Z")
I agree with you. If it helps, here’s roughly what the whole company is doing right now: - Product engineering is entirely focused on reliability and communications - Support is doing ongoing support work, and pitching in extra to help us brute force customer communications - Infra ops is entirely focused on reliability, incident management, and adding more people - Framework teams are still working on Frameworks There aren’t people working on new features. Reliability work sometimes manifests as features ([like the status page](https://community.fly.io/t/new-status-page/11398)). These contribute, though. We’re not working on anything except: stuff that makes apps on our infrastructure more resilient, and stuff that helps us communicate “are we broken or is your app broken?” to y’all. * * * This weeks’ outages have been pretty specialized Nomad/Consul/raft issues that not everyone can address. We have managed to add folks to help out and get them ramped up quicker than I expected, which is helpful. We’re in an architectural hole that we can’t “ops” our way out of. Fingers crossed we can get out from under this stuff any day now. --- _[View the full topic](https://community.fly.io/t/frequent-outages-is-really-demonstrating-fly-is-not-production-ready-yet/11502)._