On October 20, 2025, AWS suffered a significant global outage. The disruption began around 3:11 AM ET in their US-East-1 region and rippled out across many services, triggering widespread app and website failures. The root cause? A malfunction in AWS’s load-balancer monitoring subsystem and DNS issues.
Major platforms felt the pain: gaming services like Fortnite and Roblox went offline, social apps like Snapchat had issues, banking systems in the UK were affected, and millions of users reported problems.
Why This Matters
This outage is a stark reminder: if you build your services on top of “big-cloud” providers, you inherit their risk. Even giants stumble. The global infrastructure is only as resilient as its weakest link.
How Microart Software Stayed Up While AWS Was Down
Here at Microart Software, we’ve built our flagship services on our own infrastructure — the Microart Cloud, which gave us a critical advantage when AWS went dark:
- BlackFrame (our flagship data-management platform) remained fully operational: DataMaid AI, document storage, entity storage — no interruption.
- Apollo 6 Online Services (including AI features, Drive, Marketplace, Connect Feed) also stayed online and performing.
- Menuify Online Service (store, plugin database) remained accessible.
- Auto Iconifier Online Services (store and user marketplace) likewise had zero downtime.
Because we weren’t riding on AWS’s shared stack, when AWS faltered our services didn’t.
Takeaway
For our clients and users: you can trust that when major players go down, we stay up. We’re proud to provide resilience—and a little smug satisfaction that our infrastructure held fast when the cloud big guns didn’t.
Feel reassured. And yes, the humor of “everyone else going dark while we keep the lights on” isn’t lost on us.