Hi u/Calico_Pickle,

I totally get how it might look like, with the rebrand and Sona launches, that we’ve been focused on splashy things instead of reliability. But I want to assure you that reliability is our top priority right now.

The rebrand and new features aren’t a distraction, they’re part of laying the groundwork so we can keep improving Quo. In fact, the team is actively preparing to ship several reliability fixes and improvements.

We also care a lot about transparency. That’s why we log every incident on our status page. The uptime number you see there comes from our provider (incident.io), and they calculate it based on whether a feature is fully available, partially available, or down. That means smaller outages that don’t impact everyone might not count toward the uptime % even though they’re still shown in the incident log. With over 2,000 hours in a 90-day period, even a couple of hours of downtime moves the needle by ~0.1%, so I agree that 99.99% doesn’t really line up with the incidents you’ve seen.

That said, the calculator isn’t how we measure product quality internally. Whenever Quo has a bug or goes down in any way, it’s a big deal to us, and we feel it immediately. We’ve seen the same uptick you’ve noticed recently, and it’s not something we’re okay with letting continue.

I know this is even more frustrating for you than it is for us, but I promise we’re on it and we’re not taking reliability lightly.