User: ‘Why did I get disconnected?’ Me, staring at empty logs: ‘Great question. I literally cannot tell you.’ This is the no-logs promise in action.

Our VPN has a strict no-logs policy. We don’t track user activity. We don’t store connection logs. We don’t identify individual users.

This is exactly what our users want—and need.

But here’s the challenge nobody talks about:

How do you improve service quality when you’ve deliberately blinded yourself?

In traditional IT service management, troubleshooting looks like this:
→ User reports an issue
→ Pull their connection logs
→ See exactly what happened
→ Fix the root cause

With a no-logs policy, troubleshooting looks like this:
→ User reports an issue
→ We have… aggregated metrics? Maybe?
→ Try to reproduce the problem
→ Hope we get lucky

The questions we can’t answer:

1. Why did this specific user get disconnected?
2. Which server was performing poorly for them?
3. What route did their traffic take?
4. When exactly did the authentication fail?
5. What was their actual experience?

All the data that would help us debug? Gone by design.

So how do we maintain quality without compromising privacy?

We’ve had to get creative:

1. Aggregate everything
– Server-level metrics (not user-level)
– Regional performance patterns (not individual sessions)
– Device type trends (anonymized)
– Time-based connection success rates

2. Build feedback loops that preserve privacy
– In-app quality surveys (voluntary, anonymous)
– Connection success/failure counts (no identifying info)
– Automated health checks from monitoring nodes worldwide

3. Proactive monitoring instead of reactive troubleshooting
– If we can’t debug individual issues, we prevent them
– Synthetic monitoring from every region
– Continuous infrastructure testing
– Predictive capacity planning

4. Statistical pattern recognition
– When 50 anonymous users from Brazil report issues at 3 PM, we know – something’s wrong
– We don’t need to know WHO they are to fix the WHAT

The hard truth:
We probably catch problems slower than competitors who log everything.
We definitely have blind spots they don’t have.
Some issues we simply cannot root-cause with certainty.

But here’s what we gain:
User trust. Real privacy. The confidence that we CAN’T betray their data because we DON’T HAVE IT.
And that’s a trade-off I’m willing to manage.

The question that keeps me up at night:
How much service quality are users willing to sacrifice for true privacy? Where’s the line?

Why your VPN works perfectly in London but barely connects in Jakarta isn’t a bug—it’s geography.

After managing VPN services across 100+ countries, I’ve learned that “global coverage” on a map tells you nothing about actual user experience. The world isn’t flat when it comes to internet infrastructure. And that reality shapes everything we do in IT service management.

Let me show you what I mean:

Western Europe: The Easy Mode
-Dense fiber infrastructure
-Multiple tier-1 ISPs competing
-Predictable network paths
-Strong data center presence
Result: Sub-100ms latency, 99%+ connection success rates

Southeast Asia: The Archipelago Challenge
-Traffic often routes through Singapore—even between neighbouring countries
-Undersea cable dependency (and occasional breaks)
-ISP throttling of encrypted traffic varies wildly
-Government filtering adds latency layers
Result: Same server, 3x different experiences depending on which island you’re on

Middle East: The Regulatory Maze
-VPN protocols blocked or throttled by national policy
-Limited peering between countries—traffic goes to Europe and back
-Port blocking forces protocol switching
-Deep packet inspection at national gateways
Result: What works in UAE might not work 200km away in Saudi Arabia

Sub-Saharan Africa: The Infrastructure Reality
-Limited local server options
-International bandwidth costs much more than Europe
-Last-mile connectivity highly variable
-Power infrastructure affects data center reliability
Result: It’s not about our service quality—it’s about foundational infrastructure gaps

Even within the same city, user experience varies by ISP:
-Some throttle VPN traffic aggressively
-Some have better international peering
-Some use outdated equipment
-Some actively interfere with encrypted connections

We can’t control the ISP. We can only adapt to it.

What this means for service management:
→ One-size-fits-all SLAs don’t work.
→ Server placement isn’t just about coverage—it’s about understanding local internet topology.
→ Protocol flexibility is mandatory. What works in Germany won’t work in Vietnam.
→ Regional monitoring is essential. Global averages hide local disasters.
→ User education matters. Sometimes “slow VPN” isn’t our fault—it’s a 3G connection on a remote island.

The hardest conversation I have:

Why is your service slow in “my country”?

The honest answer: “Because your country’s internet infrastructure is fundamentally different, and there are limits to what we can overcome.”

But we try anyway. Different protocols. Different routing. Different server strategies. Different expectations.

Geography isn’t just physical distance. It’s regulatory environments, infrastructure investment, ISP behaviour, and political decisions.

And all of it lands on the IT Service Manager’s desk – making sure that regardless of all of the obstacles, our user could enjoy the best service available.

We’re all gamblers, whether we acknowledge it or not. Life itself is a game of chance, and every decision we make is, at its core, a bet. From the mundane – choosing what to eat for lunch, to the monumental – deciding where to live or which career to pursue, life is a series of wagers with uncertain outcomes.

No matter how much you learn or prepare, the world is too vast and complex for anyone to fully understand. We gather inputs, analyze options, and place our bets. Decisions we hope will lead to positive outcomes. But honestly – none of us can see the future. Will the decision turn out to be good or bad? What will the consequences be? The truth is, no one knows for sure.

The biggest milestones in life and work – buying a home, choosing a career path, starting a business, or launching a new product – are all high stakes gambles. Even small, seemingly inconsequential decisions carry risks, and over time, these small bets add up to shape the course of our lives.

The key to navigating this uncertainty is risk management. Every gambler knows that success isn’t just about luck – it’s about understanding the odds, making informed choices, and preparing for the consequences of failure. Are you comfortable with what might happen if things don’t go as planned?

The hard truth is that most people aren’t great at managing risk. We’re prone to overconfidence, cognitive biases, and decision making shortcuts that can cloud our judgment. But that doesn’t mean we’re powerless. You can improve your odds by doing the work:

• Educate yourself. Gather as much relevant information as you can. Learn from experts, analyze past outcomes, and stay curious.

• Calculate the risks. Assess the potential downsides realistically. What’s the worst that could happen? Can you live with it?

• Prepare for the unexpected. Even the best-laid plans can go wrong. Do you have a contingency plan?

At the end of the day, life’s gambles are unavoidable. But how you play the game is up to you. Instead of fearing uncertainty, embrace it. See every decision as an opportunity to grow, learn, and adapt.

So, as you face this your challenges, ask yourself: what are you doing to improve your odds?

Good luck out there.

As 2023 draws to a close, I find myself in a reflective state, contemplating about the year and planning the year 2024. A central theme that recurs throughout this reflection is the course we’re steering, which is shaped by strategy or, sometimes, the conspicuous absence of it. I recently read a book named Good Strategy Bad Strategy (Goodreads) by Richard P. Rumelt, which I consider essential for anyone looking to grasp how strategic thinking can channel collective efforts for the greater good. Here, I’d like to highlight a few essential insights from the book.

The premise is simple yet profound: by harnessing our existing resources and circumstances, we can navigate the complexities of the world much more effectively. The recipe for a solid strategy involves a three-step process: diagnosing the challenge (1), formulating guiding policies (2), and executing the coherent actions (3). Think of the diagnosis as identifying a disease, while the guiding policy serves as the well-conceived treatment plan that must be consistently implemented until it is cured. The author does an exceptional job of demystifying the concept of strategy:

1. This step involves recognising the hurdles your business currently faces, something you are typically aware of to some extent. The key is to extract the complexity of your reality into a few essential components.

2. Once the critical issues are identified, it’s time to think of a broader approach to tackle them. These approaches are your guiding policies that provide direction.

3. Finally, you must define specific initiatives that align with the guiding policies. These actions should complement each other and be integrated across all parts of the organisation, internal & external processes and most importantly – user journey of the product you’re creating.

While this may sound overly simplistic, it is far from it. If done correctly, the outcome, as Richard P. Rumelt asserts, is what constitutes a ‘Good Strategy’. He expands in greater detail all of these aspects, provides detailed examples and ways to think about the kernel of strategy. Give it a read, highly recommend.