Not sure if this is in the correct place, but our service was down from 7am to 12:30pm yesterday, then went down again from 15:00 until we left work (not sure when it came back up). We are in the UK.
The Asana server status is only showing 2 hour 35 mins downtime which much less than reality. Will this be updated accurately soon?
Good question, I’d like to know as well how accurate those counters are. Why do you ask though?
Because I like to work in the real world and it makes me suspicious. If there is altered data in one area possibly to benefit some KPI’s then is it happening in other areas?
I like to give the benefit of the doubt but in my opinion, we need to work in the real world, warts and all and its not OK to alter data or hide from things that are not functioning properly.
In summary, I’m paid to think like this and I cant stop.
There also may be scenarios where contractually you are guaranteeing uptime for a service and customers would be able to claim a refund. I’m sure Asana is hitting AWS with some downtime costs and if contractually agreed, should be passed on to the customers who also were affected (this doesn’t affect me as we are advanced only).
Our business lost a whole day yesterday because of downtime but the server status is saying 2hr 35mins.
Someone from the community looked at Asana’s fine print in the contract and it apparently clearly states downtime due to 3rd party is not considered to impact Asana’s SLA.
Hi @Joe_Westwood @Bastien_Siebman, thanks for reaching out! The downtime caused by the recent outage has now been updated. As you may know, the outage was caused by widespread operational issues impacting our primary cloud provider, AWS, which affected many business applications across the internet. We sincerely apologize for the severe disruption this caused and are now focused on enhancing our system’s resiliency against future cloud service dependencies.
I hope this helps!
This topic was automatically closed after 44 hours. New replies are no longer allowed.