Is BIM360 down?

[Jason_Roy]

We have suddenly lost the ability to sync or open cloud projects.

[Wentao_Guo]

We got similar issue. Project admin account are ok but rest of account are not able to access. We also had report from contractor using their own BIM360 license report they can't access to project as well.

[M-Alam]

I can only access project I have admin level access to and cannot access all other projects.

[Jason_Roy]

I have been checking the health dashboard and it's all green...kind of useless.

[Wentao_Guo]

I got connection work from different companies says same thing happened to them as well.. let's wait Autodesk's update....maybe they party too hard in AU2022🤣 

[Jason_Roy]

European/North America Revit Clout Outage now official

 

[dtpeter2901]

I'm looking to kick this back to the top of the list again.  

For this outage, we had users experiencing issues starting approx 5:30 CST.  Yet at 8:30cst there was still nothing posted on the Health Website to acknowledge it.  

So I'm requesting Autodesk do 2 things.  I've suggested it in the past before and I'd really like to suggest it again.  Since we (the users that are loosing $1000s ever min the system is down) are usually the first to pick up on this and report issues via the hub, I'd  really love to see a "Report an Issue" button on the Collaborate tab.  This could help Autodesk identify issues more quickly when they happen.  

Second, I'd like to know what the root cause of this outage was.  Having users loose close to a half day of production time is a significant hit.  Along with the Root Cause, I'd like to know what Autodesk plans to do to prevent the issue from happening again.  

Transparency is everything.  When my management asks why it happened, it sure would be nice to provide them with some information.  Even it it's out of anyone's control.  Fiber Cut, there was a Hurricane, a Sharknado....what ever it was, I'd like to be able to say something other than, "It's down, I have no idea what happened and I have no idea how long it'll take to fix"  

[RSomppi]

---

@dtpeter2901 wrote:

Having users loose close to a half day of production time is a significant hit. 

---

Shouldn't there be a plan in place for outages? The outages are gonna happen. A better notification system is in order but the only thing that is gonna help with is determining if the outage is cloud or local network related. It's up to the companies to have plans and/or resources available to minimize losses at these times.

[dtpeter2901]

It sounds like you have some suggestions for how one should mitigate these outage issues.  If someone cuts a fiber between here and there, I can understand that's not on Autodesk.  It sure would be good to know if that was the case.  I guess we could totally switch to the Desktop Connector route, but that's even less reliable and requires updates to be pushed what seems like weekly.  It also required you to have the ability to access BIM360 anyway. 

Autodesk should have redundant systems to mitigate most of these issues.  It would also be great if they would stop applying patches without testing.  Or making 100% absolutely sure if they modify anything they've tested it.  This was actually one of the root causes from the last time there was a significant outage.  They already outsource to AWS for most things; which is why I'm guessing FedRamp certification is still on-going.  If the product being produced was capable of working across a WAN this wouldn't be an issue.  I'd be working on our network and not paying Autodesk.  

I can count on one hand the number of times in the last 7yrs Outlook has failed to work.  I don't have enough fingers and toes to count BIM360 outages.  I'm not really asking for much, just transparency.  Tell us what happened.  Tell us what you're doing to prevent the problem from happening again.  Frankly I'd like to see it attached to the Health page, as an explanation to the issue.  Just look at what AWS provides on their health page.  It's not a secret that something broke.  Tell us what happened.   

[RSomppi]

---

@dtpeter2901 wrote:

I'm not really asking for much, just transparency.  Tell us what happened.  Tell us what you're doing to prevent the problem from happening again.  Frankly I'd like to see it attached to the Health page, as an explanation to the issue.  Just look at what AWS provides on their health page.  It's not a secret that something broke.  Tell us what happened.   

---

To what end, though? Is that information going to make a difference in your down time?

I could see an estimate for when it will be back up being useful information in that it would tell you if it's a possible long term outage that would require implementing a back-up plan to keep people productive. If you are in a strict production environment that is totally reliant on the cloud, that may not be possible. There are possible ways to continue working without being connected but that requires planning for the inevitable outage. If outages are that big of a deal, isn't it a good idea to break down the reliance on the cloud from 100% to something that keeps people at least somewhat productive during these times?

How many outages does it take before a back-up plan is made?