u/Hairy-Supermarket120

Question: I currently have numerous cheap agents, but to make up for lack in quality i have very rigorous testing, along with normal tests, i do play write/ chromium testing, i also render every single page and route and screen shot them and upload them to github artifacts.
which i then use chatgpt mcp github connector so my smarter chatgpt can download and look at the app visually to inspect it.
Anyways all this testing adds up to about 60 minuets per pr they make, it's spread across different tests suits so it runs faster but 60 mins that would be charged
I'm currently using roughly 200k runner-minutes/ month. The included minutes only cover a fraction of that, so Cl has become a significant expense.
I've already moved some workloads away from GitHub-hosted runners, which has helped, but at this scale it's still expensive.
For anyone running similarly Cl-heavy projects, how are you keeping runner usage/costs under control?
Self-hosting? Ephemeral runners? Reducing the test matrix? Only running expensive suites after merge?

We recently updated one of our client websites to Hostinger’s nameservers after Hostinger pushed users to move over. We completed the migration within the required timeframe, followed the process, and the sites are still broken.

What makes this worse is the lack of proper communication. There was no clear warning about the level of disruption, no appropriate timeframe given for resolution, and no meaningful support for businesses that rely on these websites being live.

This is not just a minor inconvenience. I have clients whose businesses depend on their websites working properly, and this has created real damage, stress, and reputational risk on our end. It feels completely unacceptable from a company providing critical hosting and DNS infrastructure.

I am also starting to wonder whether this crosses into contractual or consumer/business protection territory, especially if businesses were effectively pushed into a migration and then left with broken services and inadequate communication.

Has anyone else experienced this with Hostinger recently?

If so, please comment below or message me. I’m considering putting together a group of affected users so we can compare evidence, timelines, screenshots, support responses, and potentially escalate this properly as a collective.

The more people who document what happened, the stronger the case becomes. Hostinger needs to take responsibility for the impact this has had on businesses and their clients.

Everyone needs to get in touch with support now about this decision, they are getting rid of a records which will be a nightmare for those with only one site on hosting but an even bigger one for developers! we have to make our voices heard before a full rollout happens, I saw the article yesterday and since then its been removed but they are still going ahead with the decision. for those like me who've been a hostinger customer for years we are all aware of the drastically raising costs and bad support but this decision is beyond reasonable and causes a load of work, if they want to change the a records they should do it for us if its so "simple"