· None of the above quite fits
· None of these quite match
· Live Radio Metadata Service down "Meadata Service Error ETIMEDOUT"
· Basic
Live Radio Metadata Service has become unstable on Roon side, sdhowing ETIMEDOUT error on all stations
The master server (that I operate) is running smoothly see https://radio-metadata.fr
For some reason, Roon’s slave server is not able to reach sources (HTTP Error ETIMEDOUT), firewall isue in your Google Cloud infrastructure ?
Hi @alec_eiffel,
Thanks for writing in! There’s a good chance you’re running into the last bits of spotty coverage from a known service outage with Cloudflare, here’s the tracking thread we’ve been posting updates to:
Go ahead and reboot your router and Roon devices and let me know if the same issue occurs. Thank you! 
Hi @alec_eiffel,
Are you still seeing these timeouts?
Yes I do, they come and go. Right now :
The issue is affecting ALL Roon users. The master server is working well see radio-metadata.fr
It looks like the Roon hosted slave server for Live Radio Metadata has become unstable. This happened in the past, it probably requires the attention of your Devops team. FYI @nathan developed it and maybe can help.
A few minutes ago, all stations using Metadata Service lost metadata.
It seems that the slave server in Roon’s cloud has crashed.
I suspect this is following an update of my master server - I’ve just added 2 stations to the service, and the sync caused the crash.
We had this behaviour in the early days (2021 ?) but until now it had worked smoothly, there’s a regression here…
EDiT: still down this morning @connor
Problem SOLVED, and it’s entirely my fault. I set a radio ID that included spaces and forgot this is not properly handled in the code 
. Metadata should resume in a few minutes. Topic can be closed…
Hello @alec_eiffel
Thank you for the update. We are great to hear that you were able to find the culprit. Enjoy your music!
