The Cost of Downtime for Irish E-commerce
The Revolut disruption in October 2026, trending at thousands of searches per hour in Ireland, was a free lesson in downtime economics: when the rails stop, the transactions stop, and the cost is immediate. Your own store is subject to the same arithmetic, and the useful exercise is calculating the number.
The arithmetic, in your own numbers
An hour of downtime costs, at minimum: average hourly revenue lost, plus the customers who buy from a competitor and never return, plus the support and recovery time. The first number is easy to calculate from your sales data; the second is the one that compounds, because a customer lost to an outage usually stays lost.
Where Irish stores lose uptime
- Hosting failures. Shared hosting with no redundancy is the classic single point, the argument in our cloud hosting guide.
- Payment provider outages. Your store is up, but nobody can pay, the Revolut lesson, and the reason for the backup payment stack.
- Deploys gone wrong. A release that breaks checkout, with no rollback plan, converts a five-minute fix into a five-hour incident.
- Security incidents. The PHP flaw episode showed how shared infrastructure failures become everyone’s outage.
The resilience moves that keep the number theoretical
- Monitor what matters. Uptime checks on the checkout, not just the homepage, with alerts that reach a person.
- Redundancy where revenue flows. The backup rails and hosting that fails over.
- Rollback plans. Every deploy reversible in minutes, the discipline from our migration guide.
- The recovery runbook. Names, steps, and communication templates, written before the outage, per the disaster recovery guide.
Do the arithmetic tonight
Take your average daily revenue, divide by trading hours, and multiply by a realistic outage duration. The result is the budget for prevention, and it is usually a lot larger than the prevention costs.
Read next: Data backup and disaster recovery for Irish businesses