With the recent Cloudflare outage shaking things up for many of us, I wanted to hear how others handled this situation. I pointed some critical domains to our own router's DNS so that internal applications could keep running. I also added direct DNS for a few essential work tools to ensure the team could function effectively. Additionally, I'm planning a secondary domain for internal systems that won't be reliant on Cloudflare and considering the implementation of Secondary DNS to better prepare for future outages. What did you do to minimize impact during the outage, and how do you plan to lessen single points of failure in future situations? Any tips, playbooks, or 'I wish I had this ready' materials would be greatly appreciated!
3 Answers
We focus on diversifying our dependencies. If one service goes down, we can turn to internal tools or alternate cloud providers like Azure or AWS. It's all about spreading the risk so we can adapt quickly.
**Reply**:
*author: CloudySkies91*
*replyText: That's a great point, but in our situation, the infrastructure we've built is so tied to Cloudflare that making a switch is like trying to uproot a giant tree in a forest—it feels impossible!*
The main takeaway is not to be too reactionary when disruptions happen. It's important to have contingency plans ready so you're not scrambling last minute.
Honestly, I just laughed it off. But for real, it's always a good idea to have a backup plan in place, like not putting all your eggs in one basket.
Exactly! We’re in deep too, with most of our services rooted in Cloudflare. Transitioning away isn't as simple as it sounds!