The AcoustID service is currently experiencing serious technical problems and will have to stay down for several day and some recent data will be lost.
If you are user of the free service, I apologize for the inconvenience and hope that I’ll be able to repair the service soon, so that you can start using it.
If you are a paying customer, supporting the open source project, you future invoices will be cancelled. When the service will be functional again, I’ll get in touch with you whether you would like to stay a customer.
Sorry for not replying, Rob, I was super busy with fixing things. This is purely a technical problem, not a financial one, which is kind of how I got into the situation. So far, I was always able to fix things just by renting more servers, but that is now no longer effective and AcoustID needs bigger changes.
The service is now partially restored, but heavily rate-limited at least for the next week or so, until I manage to separate some parts of the backend.
I’ve increased the rate limits, as things seem more stable now, but I’m seeing nowhere near the amount of traffic I was seeing before the incident, so something must be still wrong. If the service is not working for you, please let me know and I’ll try to find out why it’s not working.
Not sure if this had already been resolved before the downtime or if it is a result of the redeployment, but the issue of sometimes randomly getting empty results is now also ok again.
The service is now fully restored. You can read more about what went wrong in this blog post. More details will be posted later. You can expect some changes to the APIs, to make sure the service stays fast and a situation like this does repeat.
Thanks a lot for getting this fixed and for the insights.
I actually see the positive side of this: The problem the service ran into are a direct result of its astonishing success over the last 10 years (nearly 11 really) and the continuous growth this is causing. Thanks a lot, @lukz, for the service itself and its continued support.
I am looking forward to the changes and to see the service improve and prosper. Let me know if there is anything that should be done on the Picard side.
Thanks @outsidecontext for sharing that URL.
As service is now restored, I’ve tested that API & status URLs.
API URL: I can (quickly) search & find from (Linux) Picard
Status URL: “AcoustID services are unavailable”
From my point of view, the status webpage doesn’t seem to reflect the API status.
Hi @lukz, thanks for your work to restore the service !
FYI
The API lookup function is working fine as the submission_status function but I can see many of my submissions are still pending from before the technical issue.
Is it related to your explanation ? Does this mean we’d better stop new submissions until further noticed ?
“AcoustID is now back up, but still not in ideal condition as we were having major performance problems for the last few months, which are unfortunately no longer solvable just by adding more servers”
I’ve pushed a donation at same time
Thanks for the great work to have this service still online for soooo long (seems an eternity in digital world/age)
I’d like to donate to the project but the link to Patreon on https://acoustid.org/donate doesn’t seem to work (it redirects me to the main page on patreon.com). Is it just me?
