I built the provider I always wished I could call.

I've spent 14 years in infrastructure—writing code, managing networks, debugging packet loss at 3am. I've worked at hosting providers, ISPs, and industry associations. I've built systems that process millions in revenue and configured BGP sessions across three continents.

Throughout all of it, I kept running into the same problem: calling my own providers for help was painful. I'd have a specific routing issue—asymmetric paths, a BGP community not propagating, whatever—and I'd get put on hold. Level 1 would answer, read from a script, ask if I'd tried rebooting.

Escalate. Wait 48 hours. Level 2 asks for the same information I already provided. Escalate again. By the time someone who actually understands the protocol looks at my ticket, a week has passed and my customers have already complained.

This isn't a support problem. It's a structural problem. When providers optimize for sales volume over technical depth, support becomes a cost center to minimize. The people answering phones have never configured the services they're supporting.

I started The IT Dept because I wanted to work with a provider like the one I'm building. One where the person answering the phone can actually read a BGP looking glass. Where support tickets go to someone who has configured the service you're asking about. Where there's no "Account Manager" sitting between you and the technical team.

I automate everything I can so humans can focus on problems that actually need human judgment. Provisioning is API-driven. Monitoring is proactive. When something breaks, I often know before you do.

This approach doesn't scale to millions of customers. That's fine. I'm not trying to be Telstra. I'm trying to be the best infrastructure partner for businesses that actually care about their connectivity—companies run by people who've felt the same frustration I have.