Competition Is Good. Monday Night Was a Reminder of Why We're Building.
We’re big believers in competition. Look at what Texas Card House and The Lodge have done for Austin poker — two great rooms pushing each other, raising the bar, and in the process putting Austin on the map as one of the best poker cities in the country. That’s a fantastic thing for the whole community. A rising tide lifts all boats.
So when we talk about what happened Monday night with Hijack, it’s not to pile on. It’s because moments like this are exactly why we’re building salty.poker — and why we think we can do it better.
What Happened Monday Night
Monday evening. Prime time. Players ready to sit down.
Hijack went down. Zero tables. Zero players. Complete outage.
We flagged it at 6:05pm — login failures, no tables, no activity. Hijack didn’t send a push notification to their own users acknowledging the issue until 6:50pm. By the time most of their players even knew something was wrong, we had already been watching it for forty-five minutes. The platform came back at 7:53pm — one hour and forty-eight minutes of total downtime on a Monday evening.
We genuinely hope they get it sorted. A healthy online poker ecosystem is good for everyone, including salty.poker.
How salty.poker Is Built for This
Outages like this aren’t random bad luck. They’re the result of architectural decisions made early — or not made at all. Resilience isn’t something you add after launch. It’s something you design in before the first line of code gets written, which is exactly what we did.
salty.poker is built on Microsoft Azure with redundancy at every layer. Auto-scaling absorbs traffic spikes before they become incidents. Health checks and automated failover mean a single failing component doesn’t bring the whole system down. Our monitoring is built to detect problems fast — sometimes, as Monday night demonstrated, faster than the platform experiencing the outage even knows it has one.
The goal is simple: when something breaks — and something always eventually breaks — the tables keep running, players stay in their seats, and most people never know anything happened.
About That 45-Minute Head Start
The fact that we detected the outage nearly 45 minutes before Hijack notified their own players is worth sitting with for a moment. We’re not their ops team. We have no access to their internal infrastructure. And yet here we are.
It raises some questions. Questions that start to connect to some interesting patterns we’ve been noticing in their player data. There are rumors circulating in the community about bots running loose on that platform. We have some thoughts on that.
But that’s a post for another day.
Stay salty.
