Who's Responsible If Your Cloud Provider Has an Outage?
Moving infrastructure off your own premises raises a question a lot of businesses never quite get round to asking clearly: if something goes wrong, who's actually responsible?
It's easy to assume the answer is "the cloud provider," and move on. In practice, the answer depends entirely on what you've signed up for, and a lot of businesses find out how vague that answer actually was only once something's already gone wrong.
Why "the cloud" isn't one thing
"Cloud hosting" covers a wide range of arrangements — from a basic hosting account with minimal support, to a fully managed environment where a team is actively responsible for uptime, security, and recovery. The service level attached to each is very different, even when the marketing language sounds similar.
Before assuming your data is "in good hands," it's worth knowing specifically whose hands, and what they're actually accountable for.
The POPIA question underneath this
In South Africa, this isn't purely a technical or contractual question — it's a data protection one. POPIA doesn't stop applying because your infrastructure isn't physically on your premises. Businesses remain responsible for how personal information is processed and protected, regardless of where the underlying servers happen to sit. "Where is our data, and who's responsible for protecting it" is a genuine business question with real accountability attached, not just an IT department's concern.
That doesn't mean cloud hosting is a compliance risk in itself — often the opposite, if it's properly managed. It does mean the question of accountability deserves a clear answer, not an assumption.
Questions worth asking about your current setup
- If there's an outage, who is actually notified, and how quickly?
- Who is responsible for backups — is that included, or a separate arrangement entirely?
- What's the actual recovery process if something goes wrong, and how long would it realistically take?
- Is there a named team or person accountable, or a general support queue?
If the honest answer to any of these is "I'm not sure," that's worth resolving before an outage forces the question. It's a much easier conversation to have calmly, in advance, than during the middle of an actual incident when the business is already under pressure and everyone's looking for someone to blame.
What this looks like when it's handled properly
A properly managed cloud setup means there's a documented answer to each of the questions above before you ever need it — not something worked out for the first time during an actual outage. It means backups are tested, not just scheduled. It means recovery time is a known figure, not a guess. And it means if something does go wrong, there's a specific team already responsible for fixing it, rather than a support ticket entering a general queue.
What "fully managed" cloud hosting actually adds
Fully managed hosting with Ensite means the accountability question has a clear answer from the start: someone is actively responsible for uptime, security, and recovery — not just a login to a dashboard and a support email address that might get a reply. Backed by our partnerships with Veeam and Acronis for backup and recovery, it's built around having a real answer to "who's responsible," not hoping the question never comes up.
Not sure who's accountable for your business's data right now?
If you're not confident you could answer these questions about your current hosting setup, that's a reasonable thing to want checked. Tell us what's not working — or what you're not sure about — and we'll help you get a clear picture.