Bonum Certa Men Certa

When the Employer Doesn't Pay the Bills, So Customers Suffer Outages/Downtimes, Repeatedly Even

One client even said it bluntly to our manager, accusing the company of "incompetence" (the examples below are only the managers' fault)

sirius-competence

Summary: Dishonesty and non-technical problems became a norm under the new Sirius 'Open Source' CEO (or under his watch); today we give one client's story as an example or a case study, where Sirius management is failing to pay upstream providers, resulting in catastrophes

THE "finaliser" of the company may not be the only misguided manager (or saboteur). He turned out to be the barrier and the burier [sic] of the company.

Today we give as an example two separate incidents impacting twice the same client, one year apart. Cause of outage? Not faulty hardware. Not faulty software, either. It was unpaid bills. Who failed to pay? Sirius. The client trusted Sirius to take care of it. Big mistake.

"Sirius failed to pay providers in two countries. The first such incident apparently didn't serve as sufficient warning."Without naming the client or the nature of the client's work, let's just say that it is a critical client, a longtime client (longest), which relies on real-time access to data and cannot afford downtimes (not long downtimes anyway; as alluded/hinted in this meme last month, the effects would potentially be devastating).

Sirius failed to pay providers in two countries. The first such incident apparently didn't serve as sufficient warning. No lessons learned. Or maybe no money left in the bank. Remember that it also looks like Sirius could barely pay its own staff; it's like they failed to pay our pension on several occasions/years; thankfully the pension provider started sending us more and more letters to warn us; it was waiting to report the company, maybe even impose penalties/fines as a result.

Making fun of companies or persons who cannot pay bills is no source for amusement/mockery, but if one company fails to pay another the latter may fail to pay its bills or even its staff. So that's not fair. We're not talking about food bills here; it's stuff like hosting. They kept warning, repeatedly, before taking action (e.g. an E-mail saying payment was "overdue" and lots of warnings before that, for several months in fact).

"It's absurd that pointing out such embarrassing realities would be deemed 'defaming' a company (with facts)."Was the client properly informed about what had happened or were those incidents brushed under the carpet, swept under some rug somewhere? This is the sort of stuff that made me unhappy about the company. The latter incident happened just months ago. I decided not to contact the client and instead hope the company would confess. That never happened though. A host wasn't being paid for a very long time and then it issued warnings which escalated in severity. The client might also want to ask this host and see if there are overdue invoices right now (in 2023). Months ago the client had a very major outage after Sirius had racked up thousands of pounds in unpaid hosting bills (while trying to sell the client AWS 'clown computing', which would be vastly more expensive and I internally opposed efforts to move to it).

It's absurd that pointing out such embarrassing realities would be deemed 'defaming' a company (with facts). The liars love to claim that everyone who says the truth is engaged in "defamatory" behaviour, as if defamation and truth became synonyms. The egoistic boss fails to understand that a company is not a person and facts are not defamation.

When an incident happened in 2021 the handover said: "Logged onto their portal and server is suspended due to unpaid invoice. Raised it with everyone on Slack, and xxxxx told me to tell xxxxx that we're raising an important ticket with them. xxxxx paid the invoice and they lifted the suspension."

The Slack messages at the time:

xxxxx: Does anyone know if xxxxx has been paid yet as xxxxx says he can't get onto xxxxx xxxxx: xxxxx is asking for an update. Can we pay xxxxx tonight or will we have to wait until tomorrow? xxxxx: They have a fairly old-school process for accepting payment if I recall. It took a number of days to clear payment last time. xxxxx: xxxxx and/or xxxxx put the payment through last time to a specific bank account.


"It took a number of days to clear payment last time," it says. Not the first time. Lessons not learned.

"Three months ago another rather similar incident happened, but this time in another country and another hosting provider."This is similar to the excuses we got when our pension wasn't paid (on two separate years), even several months after the days in question. They blame the payment processor instead of those who failed (e.g. forgot) to make the payment!

Three months ago another rather similar incident happened, but this time in another country and another hosting provider. There was no mention of what had happened after the Big Boss was shuffling lots of credit cards, struggling to make a payment to the provider. To quote: "xxxxx and xxxxx emailed to say that xxxxx was down but we didn't get any alerts so looked into it. Then one of their customers emailed to say they couldn't login. xxxxx asked me to restart UIs which I did and the problem was resolved. xxxxx sent some questions to ask xxxxx who said he will look into it and get back to them tomorrow. I checked the db connections and there seems to be 380 open out of a possible 1000, but I'm sure xxxxx will be able to verify this too."

Nothing was said about the failure to pay the bills. Are we meant to think nothing actually happened? Are we meant to lie to clients about this, wasting their time as they try hard to figure our the root cause?

Don't work for chronic liars. If your employer starts lying a lot, consider your options.

Recent Techrights' Posts

Linux Kernel Becoming a Slopfest - Part 6 - Seeing Who Contaminates Linux With Slop (And Also Admits It)
Today we begin looking at some culprits
2026: The Year Galleries Realised the Need to Flag or Cull Slop Images
Society needs to shun slopfarms, people who use LLM slop (for anything at all), companies that use bots (which they dub "agents"), and so-called 'coders' who volley garbage into project and software hubs
Software Freedom Day Celebrated in 5 or 6 Continent
Software Freedom Day (SFD) 2026 was big this year
Enjoy the Giving/Sharing, Not Taking
We've long supported what we believed in, even with the little money we had
 
Links 21/09/2026: "Back On My Bicycle" and American Regime's War on Media Escalates Further
Links for the day
SLAPP Censorship - Part 192 Out of 200: The Hired Guns of Garrett and Graveley Sent Us USB Sticks (One to Me, One to My Wife) Showing Lozza Talking to Garrett About Censoring/Deplatforming Techrights the Same Time Graveley Was Copy-Pasting Garrett's Lawsuit
Next year we plan to bring this matter to the Court of Appeal
SLAPP Censorship - Part 191 Out of 200: Garrett, Graveley and Lozza
They talk to and coordinate with one another
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, September 20, 2026
IRC logs for Sunday, September 20, 2026
Gemini Links 21/09/2026: Digital Hoarder, GTD, Minimalism vs Digital Minimalism, Rejection of LLMs
Links for the day
Links 20/09/2026: "Google Now Asking For Users’ Video Selfies" and Energy Prices Set to Rise
Links for the day
Links 20/09/2026: Amazon Layoffs, Flock 'Buyouts' (Silent Layoffs)
Links for the day
USCIS and Microsoft Rumours: Curbs on Lowering Salaries by Importing Cheaper Replacements?
It seems like Microsoft's mass layoffs and efforts to cheapen the workforce face obstacles
Gemini Links 20/09/2026: "Music While Working" and Radio Silence
Links for the day
Clownflare Data From Canada
We've like to think many people are attempting to install GNU/Linux over the weekend
SLAPP Censorship - Part 190 Out of 200: Plagiarism, Back Doors, and Sabotage of Linux
This can go on for a decade or longer
Linux Kernel Becoming a Slopfest - Part 5 - Kernel Dependency on Plagiarism Giant Microsoft is a Death Blow to Any Kernel
Microsoft is bringing copyright-infringing slop into Linux
GNU/Linux Has Grown a Lot Lately
Based on Clownflare
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, September 19, 2026
IRC logs for Saturday, September 19, 2026
Links 19/09/2026: Many Patents Become Candidates for Annulment and Linux [sic] Foundation Takes More Slop Money to Promote Malicious Bots
Links for the day
Gemini Links 19/09/2026: The Fundamental Human Assets, The History of Gopher's "i" Type, and ROOPHLOCH 2026
Links for the day
Links 19/09/2026: "OpenAI and Microsoft Knew They Were Starting a ‘Doom Loop’ [of Mass Plagiarism 'Normalised' by Brute Force] for the web", Calling It "Hey Hi"
Links for the day
8 Series Going on at the Moment in Techrights
4 series about SLAPPs and related matters
Linux Kernel Becoming a Slopfest - Part 4 - Outsourcing to Microsoft, Approaching 10 Gigabytes
Can we blame Microsoft for those DDoS attacks? Partly.
SLAPP Censorship - Part 189 Out of 200: A Terrible Idea to Condemn Projects for Using Slop 'Code' When Your Own Employer Does This (and Profits From Every Company Doing So) or to Call Distros 'Not Secure' While You Advance Back Doors
"I don’t want a back door. I want a front door."
Software Freedom Day 2026 is Today, Week-long Celebration in Brazil
In Brazil, Clownflare reckons about 1 in 20 laptops/desktops might use GNU/Linux already
Red Hat Lost 2,000 Staff (Net Loss)
Maybe by year's end it'll be a 20% reduction
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, September 18, 2026
IRC logs for Friday, September 18, 2026