Gamer N' Geek
said: Then we'll call it timing. Because what I know is this: I don't use Roll20 that often. Once, maybe twice a week, if I can get players together. Which means that since I backed, I've played maybe 8 sessons? Of those 8, there has been downtime in at least 3. If someone were to ask me "Do you consider Roll20 a stable service?" Right now my answer would have to be no. February 28. March 26. Today. A ll those are just the ones I've posted on the forums about. Not all there were, just the ones I've posted about. So, maybe it's just bad luck and all your downtimes happen to be on the days I can get players together. Or maybe you're just down a lot more than you should be. <a href="http://status.roll20.net/" rel="nofollow">http://status.roll20.net/</a> I think it's well within a reality of "acceptable ranges" BUT as we all know, any downtime when the party is united is going to feel unacceptable. As such, we work hard to avoid downtime, and it's something we take very seriously. That said, the majority of downtime is out of our hands, in the trust of Firebase. They are usually quick to say when they are having issues: <a href="https://twitter.com/FirebaseStatus" rel="nofollow">https://twitter.com/FirebaseStatus</a> However, I don't want to sound like we "blame" Firebase for things-- their great and consistent service allows us to focus on bettering this program instead of hosting this program. They, like us, are trying to better their new service, and at times that causes hiccups. Given how increasingly rare those hiccups are, we're glad to be working with them. Again, sorry for any troubles and know that we are always pushing for better.
