Some kind of issue has been going on for the past couple weeks when trying to import my music using Beets and I didn’t previously have any issues like this.
I can access musicbrainz.org via my web browser just fine, but my Beets install regularly spits back Error: MusicBrainz not reachable in release search with query... and then cancels my music import. I’ve got my config file to only do one API query per second, so I don’t know what the issue is.
Any help is most appreciated.
I don’t use beets, but the site has been acting very weird for me the past week. It’s mostly been very slow to load pages. Sometimes Picard fails to fetch album data too.
I don’t know what’s the exact error code so I cannot say for sure, but I suspect it’s the current AI DDOS affecting you. Most requests fails and need to be retried, but it seems beets don’t do that and just error out.
So stay calm and keep hating AI.
Thanks for the idea actually. I had ChatGPT write me a plugin that wraps the MusicBrainz calls into a helper that will auto-retry after x number of seconds if it fails. 
The what? Someone’s DDoS’ing Musicbrainz? Why?
@FeloniousMonk13, good question.
What do bot authors want to obtain?
Or is the AI scanning us on its own initiative?
Maybe other taggers using MBID are burdening our microsystem?
Scroll down to the report from Zas in the meeting notes:
He is literally fighting a flood of bots using MusicBrainz to acquire knowledge on music. The problem is they work really heavy handed and hammer the site with their bots. It is the same for many websites. They suffer under a barrage of bots overloading the ability of websites to keep up.
IA is a nuisance at many levels. And only a nuisance.
IA is AI in French, sorry.
I meant AI sucks in many ways and is only a big nuisance for Earth and its inhabitants.
HOW DARE YOU INSULT THE INTERNET ARCHIVE?!
/j
We have to go back to the caves, hunt some animals and sit by the fire.