Why Your Cloud Backup Still Sucks (And What Korea Taught Us)

·Commentary on Pieter Levels Blog

Cloud backup is still a mess for most people. Pieter Levels made it look easy back in 2015 when he uploaded 4 terabytes over Korean 4G for $48, but that story is more exotic vacation than practical reality. The guy flew to a country with world-beating infrastructure, ate BBQ for a month, and solved his backup problem. Great for him. For the rest of us? We're stuck with capped plans, throttled speeds, and the nagging feeling that our data is one hard drive failure away from disappearing.

I run PainSignal, where we track real problems builders and users face. Right now, we have 112 problems in internet connectivity with an average severity of 3.8 out of 5. Cloud backup specifically accounts for 23 problems at severity 3.6. These aren't niche complaints — they're widespread frustrations that scream for better solutions.

Levels' story highlights exactly what's possible when infrastructure cooperates. Korean 4G gave him 50 Mbps upload speeds, which he calculated as 5 MB/s, translating to 432 GB per day theoretical max. He actually averaged 200 GB/day over 20 days. That's absurd by any standard. But here's the thing: most people can't replicate that. Our data shows 89 problems in the remote work category (severity 4.1/5) related to unreliable internet abroad. The gap between Korea and everywhere else is a chasm.

The author took a dig at CrashPlan, claiming it caps uploads at 2 Mbps. Our data doesn't confirm a universal hard cap — speeds vary wildly by region and plan. Some users report acceptable performance. But the frustration is real. When you're paying for unlimited data and getting dial-up speeds, it doesn't matter if the cap is real or perceived. The pain point is the same.

What makes this story useful isn't the envy — it's the blueprint for building better tools. Levels used AWS Glacier in Tokyo with Arq Backup, achieving encrypted, server-side transfers at near-maximum throughput. That's a hack, not a product. Most travelers don't want to set up AWS instances and configure backup software. They want something that works out of the box, adapts to whatever network they're on, and doesn't punish them for having intermittent connectivity.

We track 37 problems in telecommunications (severity 3.5/5), with complaints about slow speeds and data caps in nearly every country outside East Asia. The market opportunity is clear: build a backup solution that assumes the network is hostile. One that pauses intelligently, resumes without fuss, and optimizes for the connections people actually have — not the ones we wish they had.

The author's overage scare is instructive too. He feared a $40,000 bill because standard overage rates can hit $10/GB. He avoided it because Korean plans were truly unlimited. Most carriers aren't that generous. A backup tool that respects data caps and warns users before blowing through them would solve a real anxiety. Our data shows this is a top complaint among travelers and remote workers.

So what can you build? A cloud backup service designed for mobile-first, travel-heavy users. One that compresses and deduplicates aggressively, syncs only when on unmetered networks, and supports incremental uploads that survive connection drops. Think of it as CrashPlan meets eSIM management. The author's extreme example — flying to Korea to upload a terabyte — is a signpost for where we should be heading, not a practical solution for today.

The infrastructure gap isn't closing fast. Our data suggests that while Korea was a positive outlier in 2015, most regions still struggle with slow wired connections and expensive wireless data. Levels' conclusion was that wireless is the future. I'd argue it's the present, but only if you're in the right place. For everyone else, we need software that bridges the gap.

Pieter's original post remains a fun read and a useful benchmark. But the real lesson for builders is this: don't assume your users have Korean 4G. Assume they have a flaky 3G connection in a coffee shop with a 5 GB cap. Solve for that, and you'll have a product people actually need.

If you're interested in building something in this space, I've been tracking opportunities like a cloud backup service for travelers and problems around slow internet while traveling. The data is clear: the market is frustrated and underserved.

This article is commentary on the original article at Pieter Levels Blog. We encourage you to read the original.

Explore more problems and app ideas across Cloud Services, Remote Work.

Browse App Ideas

Join the beta — full access for the first 1,000 builders

Join Beta