Network plasticity and full picture

 

Transform dilemma between resilience and agility to solution

This year (2025) we are a widespread DNS/BGP failure away from engineering managers and public knowing what in each other’s service stacks. That is still a resiliency level above regional electricity blackouts blocking customers from providers, and providers from customers. Followed by a few other unfortunate scenarios culminating at rare what-if Carrington event.

These are much harder cases to bypass than today’s (2025/11/18) Cloudflare’s outage.

Resiliency is quite challenging. When executed as an addon it is often a dilemma between slowing down technology operations and product development in favor of adding plasticity. Or episodically adding a resiliency in one place to discover how partial it is: like building a biometrics-protected gate with 24/7 video surveillance without fully securing adjacent perimeter with the fence.

For Cloudflare’s redundancy you can add bypass to another CDN, or as a short fallback option – to load balancer directly. But what if second exception happens (at DNS management, or internal controls) and you can’t activate this bypass.

Dynamics are reverted when growing new services relies on platform which puts into foundation and relies on resilience to make things more agile. [2]

In the era of focused specialties and responsibilities, overall picture matters.

[1] - Ask about your “five nines” gap analysis for your service (SaaS)
[2] - Own your SaaS: 12 angles to improve your velocity with blueprints