Picard extremely slow right now. Service Unavailable?

[Ceyropaiax]

Hi,

Thank you for making this beautiful app. It’s been so very helpful.

I haven’t used it in a while and today I noticed that Picard has been very slow on lookup. I looked at the log and saw this:

E: 22:08:01,881 webservice._handle_reply:383: Network request error for http://api.acoustid.org:80/v2/lookup: Error transferring http://api.acoustid.org:80/v2/lookup - server replied: Service Unavailable (QT code 403, HTTP code 503)
E: 22:08:03,063 webservice._handle_reply:383: Network request error for http://api.acoustid.org:80/v2/lookup: Error transferring http://api.acoustid.org:80/v2/lookup - server replied: Service Unavailable (QT code 403, HTTP code 503)
E: 22:08:04,853 webservice._handle_reply:383: Network request error for http://api.acoustid.org:80/v2/lookup: Error transferring http://api.acoustid.org:80/v2/lookup - server replied:

Is this temporary? I’m on macOS Catalina & Picard 2.2.1

[outsidecontext]

The AcoustId service had some technical issues, see

The website is down

AcoustID just had the worst outage in its history. It should be all up and running now. Due to an unknown reason, the frontend HAProxy load balancer started acting up, using too much resources. I didn’t notice the problem until it was too late when the Docker Swarm cluster stopped working properly, load balancer on two other servers was shut down. There are too many unknowns, but I’m not going to spend too much time investigating, so I’m currently preparing a much better infrastructure for hos…

[Ceyropaiax]

Got it. Thank you so much!