"Massive Server Downtime: Lessons Learned from a 72-Hour Nightmare"

[Марина Грабар]

"Y'all, I just got back from a 72-hour server downtime nightmare with my company's crypto exchange. We lost access to user funds, and it was a total disaster. Anyone else ever go through something like this, and what were some key takeaways?"

 

[mangle]

"Yikes, 72 hours is a looong time to be down I feel for u guy, hoping you got some solid backups and a plan to prevent this in the future. What were some of the main causes of the downtime?"

 

[mro]

"Yikes, 72 hours is a long time for a server to be down. Hope the team learned their lesson and implemented some solid redundancies. Anyone know if they've had a chance to give an official update yet?"

 

[polosatic]

"Yikes, 72 hours is a looong time for downtime. What were the main causes? Was it scaling issues, hardware failure, or just good ol' fashioned human error?"

 

[klin4anin]

best practices - let's talk

 

[skyak78]

best practices - let's talk

 

[hhide-res]

Discussion: market updates

 

[teo77]

Discussion: market updates

 

[vit1978]

"Yikes, 72 hrs of downtime? That's insane. Glad you guys were able to get the servers back online ASAP, what were the root causes of the issue?"

 

[genik]

Discussion: strategies

 

[Fratsova2020]

Thoughts on strategies?

 

[anonym66585]

Discussion: strategies

 

[Nickolay12]

What's your take on strategies?

 

[baragoz1]

What's your take on opportunities?

 

[Vitalii89]

Discussion: best practices

 

[Sergych]

Thoughts on strategies?

 

[Божена]

"Dude, been there, done that - we had a similar issue last year with our node and it took us a solid 36 hours to get everything up and running. Lesson learned: always have a backup plan and redundant infrastructure in place, or else you'll be sleeping on a couch for a long time"