After the 48-hour SoftSwiss backend outage last month in Curacao, I’m re-evaluating their…
48 hours offline and not a peep—SoftSwiss left us staring at static screens while the emails just piled up. Who else lost GGR to a silent backend? EUR 290 looked clean on paper, but did anyone actually get billed the same after Curacao dropped the PCI-DSS hammer last quarter?
New to this, soaking it up.
what’s this, a ghosted poker room in the caribbean? softswiss should’ve at least sent a carrier pigeon with a “sorry” wing-tag when the whole backend went dark for two days.
You ever notice how the moment a vendor says "flat fee" you should start timing how long it takes for the asterisks to crawl out of the footnotes? PCI-DSS surcharges in Curacao aren’t exactly a secret, but they stopped talking about them the second everyone signed the dotted line. And an outage that long isn’t just downtime—it’s straight-line damage to your NGR if you can’t process deposits or payouts while SoftSwiss chases servers in someone else’s DC. Two days of radio silence? That’s not negligence, that’s operational malpractice when your business runs on real-time liquidity.
Where's the proof?
Man, I lived that 48-hour hell last month and it still burns. Zero updates, zero transparency—like we’re all just chattel to them. And EUR 290 “flat”? Bro, PCI-DSS hit my MID last quarter like a freight train. They slipped in a €50/mo line item labeled “security compliance” with zero heads-up. Support actually answered, but only after two tickets and a threat to escalate to Curacao Gaming. That outage? NGR cratered while they pointed fingers at AWS—total abandoned ship. Zero downtime for us turned into 48h of frozen revenue and customer fury. Yeah, the stack’s decent, but tbf… this is textbook lock-in.
Uptime speaks louder than sales decks.
48 silent hours and suddenly you’re picking up the pieces like a night porter cleaning up after a rave nobody invited. I had a client in Curacao last quarter—same story. They sent an invoice with that so-called “flat” €290 and buried a €65 PCI tick-box under administrative fees. Support’s usual “we’re on it” took eight hours to cough up the first update; by then, two rolling reserves had breached and GGR was haemorrhaging while we waited for MID numbers to tick again. The stack’s fine until the planet stops spinning. PCI surcharges? They’re not sneaking in—they’re sprinting. And when the lights go out for two days, the only transparency you get is the screen of your own terminal still showing “timeout”.
One week to find a way out and those fine folks still send me daily Slack pings asking when the SoftSwiss powder burns, like the problem’s mine.
Solid source, details in the DMs.
@BrandBuilder_iGaming
Daily ping with a straight face after two days of fire drill? That’s not support—that’s psychological warfare. I ran that Curacao client on CPA, and when the backend keeled over, the payout hit my revshare like a falling piano. Six hours to even admit the AWS meltdown, another eight before they whispered “external DC issue.” External? Their damn ad said “world-class latency,” not “your cash is on layby.” Meanwhile I’m bleeding FTDs and they invoice the PCI fee like it’s retail mark-up. I pushed back—flat rate was flat, no asterisks. They blinked. Barely. No more SoftSwiss for me; next revshare deal’s in Georgia where the stack doesn’t need a two-day holiday to reboot.
Revshare over big CPA 💸
So you’re telling me after 48 hours of their backend playing possum in Curacao while GGR melted and NGR hit the wall like a drunk at last call, they still have the gall to ask when the powder’s dry? ah well, we'll see
Launched a few, lost money on more 😉
SoftSwiss’ Curacao backbone just threw us all under the bus and then had the nerve to invoice for the privilege. 48h with no pulse, real-time liquidity frozen, rolling reserves breeched—one weekend turns into a quarterly write-off and they’re still hitting me up for “security compliance” that wasn’t in the quote. EUR 290 flat? Unless flat now includes charging me €65 to keep my MID PCI-safe, I’m not sure what flat means in this shop. Eight-hour first update after ticket two is SLA for clowns, not providers.
Anyone here actually negotiate the PCI line item out, or are we collectively just absorbing the surcharge like it’s courier coffee?
Learning from the operators who did it, go easy 🙏
Man, I’ll admit I was dead chuffed when we flipped to SoftSwiss 18 months ago—stack never skipped a beat, fees were “refreshingly simple,” and I got that warm fuzzy feeling when my lobby stopped chewing through integrations. Then BAM, 48 hours of AWS limbo in Curacao last month and suddenly my NGR hit the wall like a penalty shootout at the wrong end. Two days of radio silence while GGR trickled to zero… and then boom, a €65 PCI “administrative fee” slapped on the bill like a drunk tip at 4 a.m. I fired off the ticket on night two, got a boiler-plate “we’re on it” after eight hours, then their guy in Curacao had the nerve to tell me the DC was actually someone else’s fault. Best decision we made? Maybe yesterday.
Uptime speaks louder than sales decks.
@SamTurnkey oh mate, that stack never skipped a beat *until it did*, right? 48 hours of "refreshingly simple" turning into "oh, actually the backbone’s owned by Amazon" — funny how "never" lasts about three weeks after you sign the paper. And that €65 PCI line item? Sounds like they’d rather take the risk and bill you for the privilege of their incompetence. Who even greenlit that "flat" rate when the real cost is whatever keeps their AWS bill covered while your GGR flatlines? 🤡💸
You can bend any pitch deck you like.
Classic Curacao move—when the sh*t hits the fan they play hot potato with the AWS blame and still hit you with an “oops fee”. Love SoftSwiss or hate ‘em, but when the Curacao sun’s shining and the stack’s zipping, nothing else even comes close for scale. Their 2023 uptime was 99.98 %—so yeah, one DC hiccup and suddenly we’re re-evaluating? Defo. Question is: who’s gonna match that latency when your lobby’s filling up at 2 a.m. and their Frankfurt fallback crawls like 2003 dial-up?