But as long as you're using a registrar in your own country and a TLD managed by a legal entity in your own country, you do have a path of legal recourse against both parties.
It might not be successful, but you do have far better options than relying on a third party in a country far away.
You can set concurrency limits per function on AWS, so you can apply a hard limit on your function to only have a single invocation running at the same time. That should give you a guarantee that data isn't lost without the producer noticing.
I have no idea if this is for a specific language, a framework, a plugin system .. or what. And I'm not able to say anything useful from the page or from the title of the post.
It'd be helpful to at least set the premise for those of us on the outside.
In my own experience it's not often the elected moderators that are the problem, but those with a golden tag in a specific tag. They're far too eager to close questions because they're the ones culling through a tag often - and then close the question as they quickly think "oh, it's that again".
But it often isn't, they just didn't spend enough time to see nuance.
And neither do they see that even if _they_ understand that the question linked to is the same thing, there is no way the asker can understand what the similarity is from their knowledge point of view (or why the linked duplicate question is the same question).
From the article: "- adjust timeout settings to prevent crashes". Include the details of why the timeout setting lead to crashes; what were the inputs and the cases that caused this.
This lets us decide whether the fix stays or goes the next time there is an issue in the same piece of code, or your commit broke something unrelated - the person fixing it needs to know _why_ you changed the code.
There might be alternatives that are better designed for that use case these days; pass and KeePassXC are popular ones, depending on the interface you want (pass is made for the cli as the primary interface).
I'm not sure if having a broken navigation menu at the top because of Disconnect or uBlock is a good sign, but their product seems like a decent alternative.
You'll find vendors in Germany, Spain, etc. within the EU. Not much I can say about customs - so you might want to check local recyclers. There's usually some sort of recycling program for old hardware that gets cleaned out and re-sold, but it'll all depend on your country's incentives.
Whether it's worth it will depend on what you're looking for.
You'll find them readily available on Ebay, but there are also multiple companies that specialize in refurbishing servers (which usually will allow you to configure your actual needs - but this will be slightly more expensive in my experience).
Someone just moving decommissioned servers from a data center to new users without doing anything with the equipment in between allows you to find decent deals if you're looking for something to put in a rack.
Be aware that rack servers are usually rather power hungry, so they might be expensive to run over time.
Its all about how apparent the issue is if you're running Wireshark - it does not stand out, so you have to do a lot more work to discover what is actually happening. The request is also hidden in plain sight along other requests, and those requests are what you'd expect (you'd normally expect a motd request, so this isn't out of the place).
Given that the way of circumventing the issue at hand is to delete a single local file, which is far simpler than finding the actual request and setting up fiddler or burp suite, this worked good enough.
It might not be successful, but you do have far better options than relying on a third party in a country far away.
It's always a varying grade, not either/or.