Roon Service Outage 4/16/20

I’m also in Sweden. Noticed this for the first time today a similar behaviour. Signed out of Tidal in Roon, but can’t sign back in.

I experience the same in Switzerland right now. It throws a 502 server error.
Playing directly from Tidal works, only roon seems not be able to login.
Login via the browser to Tidal works as well.

This is the site that throws the error

Seeing the same in the U.S. Tidal app on my Mac and iPhone will play, but Roon can’t log in. Can’t restart my core now, busy with work, but I’ll give it a try shortly and report back.

Hello All,

We are aware of a service outage at this time and we’re looking into it, please see here for any updates:

Appreciate everyone’s patience while we work on getting this resolved!

1 Like

That describes exactly what I see here.

I live in France and I use Qobuz with my iPad and Roon ROCK.
As of tonight, I no longer have access to Qobuz. Am I an isolated case ?
Here is a screenshot :

Hi @Guillaume_GSCHWIND,

Please see:

Thank you :+1:

Been listening this morning and went to change to a new artist and neither Tidal nor Quobz load with any content- both say “failed to load content”- both Tidal and Quboz work fine outside of Roon. My library within Roon works (as I’d expect). I see this has happened previously many times based on Forum questions.

What’s up? Frustrating , it’s still buggy for me at times. Yes, I"m using a hard wired Nucleus.


Core Machine (Operating system/System info/Roon build number)

Linux Debian

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Ping is working, internet is working, but communication with Roon server are KO

Description Of Issue

04/16 19:12:39 Trace: [metadatasvc] REQ [2]
04/16 19:12:39 Warn: Error in web request NetworkError (The remote server returned an error: (502) Bad Gateway.)
04/16 19:12:39 Warn: [metadatasvc] FAIL [2] (155ms) NetworkError


Core Machine (Operating system/System info/Roon build number)

SonicTransporter (2.5)
/Roon build number 1.7 / Build 528


Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Hardwired LAN via Cisco switch to Fritzbox router and Deutsche Telekom 50 Mbit/s.

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Sonictransporter- Ethernet - Linn Klimax DSM - Linn Akubarik Active

Description Of Issue

My Qobuz subscription was renewed on April 7 and has worked flawlessly until today. I have no access to Qobuz through Roon. I have tried logging out and in of Qobuz, rebooting Sonictransporter, restarting the Roon server on SonicT and restarting the Roon app as well as checking for app updates.
I have full access to Qobuz via their app but no Qobuz access via Roon.

I’m pretty sure this is related to the Service Outage 4/16/2020 [Under Investigation] and is affecting all of us right now.

1 Like


I’m unable to login in to Tidal from roon opens a page with the above title. I’ve rebooted core and remotes. Can access Tidal via bluesound and Tidal apps.


There’s a problem. Hold tight


Would Roon consider using to create a page for outages, etc?


1 Like

I think that the fact that this thread is currently invisible and unlisted is contributing to the number of duplicate problem reports that users are posting to the support forum.

The “Service Outage” locked thread (with just a single post) has fallen pretty far down the list of support threads, and this one is not visible or even searchable for users.

This thread is where separate threads on the same subject have been moved to so as not to have multiple similar posts in the #support category. It is not designed to be viewed generally.

The “service outage” post is pinned to the top of the #support category and will stay there unless unpinned by the user. This can happen either explicitly by tapping the “unpinned” flag at the bottom, or implicitly if you have set automatic unpin in your preferences.

I think Roon shouldn’t Close a post if the issue is still going on. Makes people think Roon thinks the issue is fixed, ie. ‘issue closed’.