The Internet Blackout Playbook: What Iran's 13-Day Shutdown Teaches SaaS About Offline-First Architecture
Iran's internet has been down for 13 days and counting. While the humanitarian crisis dominates headlines, a quieter technical story is emerging: the handful of apps that kept working did so because they were built offline-first. Most SaaS products would simply die. Here is what separates the survivors from the casualties.
By Erik Sundberg, Developer Tools · Mar 14, 2026
Iran's 13-day internet blackout reveals which software design patterns survive total connectivity loss and why most SaaS products would fail instantly.
Frequently Asked Questions
What is offline-first architecture?
Offline-first architecture is a software design pattern where applications are built to function without a network connection by default, treating connectivity as an enhancement rather than a requirement. Data is stored locally on the device, business logic runs client-side, and synchronization with remote servers happens opportunistically when a connection is available. This contrasts with the dominant SaaS model where nearly all data and logic live on remote servers, making applications completely dependent on internet access. Offline-first apps use local databases (SQLite, IndexedDB), background sync queues, and conflict resolution algorithms like CRDTs to maintain functionality during outages.
How long has Iran's internet been shut down in 2026?
As of March 14, 2026, Iran has experienced over 13 days of near-total internet shutdown affecting most of the country's population. The shutdown, which began in early March amid widespread protests, has blocked access to international servers and most cloud-based services. Only Iran's domestic intranet (known as the National Information Network or SHOMA) remained partially functional, allowing access to government-approved local services. This is not Iran's first shutdown -- the country imposed a near-total blackout for 7 days in 2019 and has conducted rolling regional shutdowns since -- but the 2026 event is the longest sustained nationwide disruption to date.
Which apps kept working during Iran's internet blackout?
Apps built with local-first or offline-first architectures maintained core functionality during the shutdown. Messaging apps with local message queues and peer-to-peer capabilities (like Briar and Bridgefy, which use Bluetooth mesh networking) continued to function for nearby communication. Note-taking and document apps with full local storage (Obsidian, Standard Notes) retained all user data and editing capability. Navigation apps with pre-downloaded offline maps (OsmAnd, Google Maps with offline regions) continued to provide directions. Some Iranian-built apps on the domestic SHOMA network also remained accessible. Virtually all cloud-dependent SaaS products -- Slack, Notion, Google Workspace, Figma -- became completely unusable.
Why don't more SaaS companies build offline-first?
Most SaaS companies avoid offline-first architecture for several practical reasons: it dramatically increases engineering complexity (conflict resolution alone can consume months of development), it conflicts with the subscription revenue model (if the app works offline, what prevents users from disconnecting and never paying?), it makes real-time collaboration harder to implement, and it increases the client-side attack surface for security. Cloud-first architecture also enables faster iteration since updates deploy server-side without requiring client updates. For most SaaS companies serving users with reliable internet in North America and Europe, the tradeoff has been rational. But the Iran shutdown -- and increasingly frequent outages from submarine cable cuts, natural disasters, and government censorship -- is forcing a reassessment.
What are CRDTs and why do they matter for offline-first apps?
CRDTs (Conflict-free Replicated Data Types) are data structures that can be modified independently on multiple devices and then merged automatically without conflicts. They are the key enabling technology for offline-first collaboration. When two users edit the same document offline, traditional databases would create a conflict requiring manual resolution. CRDTs mathematically guarantee that all replicas converge to the same state regardless of the order in which edits are received. Libraries like Yjs and Automerge have made CRDTs practical for production use. Linear, the project management tool, uses CRDTs for its offline-capable sync engine, and Figma's multiplayer engine is built on CRDT-like operational transforms.
How can SaaS companies add offline capabilities to existing products?
The most practical approach is progressive offline support rather than a full rewrite. Start by identifying your product's core read path -- the data users need to view most frequently -- and cache it locally using service workers and IndexedDB. Next, implement optimistic writes for the most common mutations, queuing changes locally and syncing when connectivity returns. Use a sync engine like PowerSync, ElectricSQL, or Replicache to handle the bidirectional data flow between local and remote databases. Finally, add conflict resolution logic for the subset of operations where concurrent edits are likely. This incremental approach lets teams ship offline capabilities for critical flows within weeks rather than rebuilding the entire application.
Related Articles
Topics: Engineering, Architecture, SaaS, Resilience
Browse all articles | About Signal