AI News · Edition 34 ·
When the AI goes down, what happens to your Tuesday?
ChatGPT, Claude and Gemini all faltered on the same day. The lesson isn't that AI is fragile — it's that most small businesses never wrote a fallback.
The one that matters
Three big AI services failed on the same day — the question is what your business does next
What happened
ChatGPT, Claude and Gemini all went down or badly degraded inside the same window, and it was reported everywhere. The most-read discussion about it was not an explanation but a question: why were three competitors unavailable at once? That question has not been publicly answered. No shared cause has been established, and the absence of one is the interesting part.
What this actually means for your business
Over the last two years a great many small firms have quietly moved one step of a daily process onto a third-party assistant. A 600-student school drafts fee reminders and parent notices in a chat window. A 30-bed clinic tidies up discharge instructions. A workshop with 40 staff turns a WhatsApp enquiry into a printable quotation. None of this was a formal IT decision. It happened because it worked, and because it costs roughly $20 to $30 per user per month, about ₹1,800 to ₹2,500 — small enough that nobody asked procurement.
The bill for that convenience arrives on a day like this one. The useful question is not whether AI is reliable. It is: which of my processes stops if a website I do not control is unavailable for three hours during my busiest stretch? For most owners the honest answer is two or three of them, and nobody has written down what to do instead.
Consumer and professional plans carry no uptime promise at all. You are not owed a refund, a status call or a restoration time. That is perfectly fine for drafting a letter. It is not fine for anything with a deadline attached — payroll, attendance submission, tax filing prep, invoice dispatch, a same-day discharge summary.
What it does not mean
It does not mean these tools are unreliable in general. They are up the overwhelming majority of the time, and a few hours lost in a year compares well with most local internet connections in either country. It is not a reason to rip anything out.
Two groups are overstating it. The first is vendors now selling multi-model failover or a resilience layer that automatically switches providers when one fails. For a 40-person business that is a second subscription solving a problem that a one-page checklist solves better — and if something shared sat underneath several providers that day, switching models would not have saved you either. The second is the commentary treating this as proof that concentrated AI is inherently dangerous. Possibly. But the cause is unknown, and conclusions drawn ahead of the facts are worth what you paid for them.
What to do this month
- Spend one hour listing every place AI touches a daily process. Mark each one “annoying if it stops” or “we stop working”. Most lists have fewer of the second than owners fear.
- Write the fallback for that second category, one paragraph each, and check that a non-technical staff member can follow it. Usually it is the template or the manual process you used in 2024. Do not delete those.
- Keep deadline-bound work off the critical path. If a person cannot complete the task by hand the same day, it should not depend on an outside assistant.
- Read what your plan actually promises before you build around it. Business and enterprise tiers sometimes commit to something. The plan your staff signed up for on a personal card almost certainly does not.
- If an agency or developer is building on an AI API for you, ask one question: what happens when the API returns an error? Acceptable answers are “queue it and retry” or “fall back to a second provider”. “It hasn't come up” is not one. That conversation costs an hour of their time.
None of this requires new spending. It requires an afternoon and the willingness to admit which parts of the business now quietly depend on somebody else's server.
Also worth knowing
How this briefing is put together
Every morning we read the day’s AI announcements and reporting from the companies themselves and from the technology press, then pick the handful that actually change something for a working business. The analysis is ours and it is written for owners and managers, not engineers. Every story links to its original source — read them, and disagree with us where we’ve got it wrong.