today dropouts are back 

today it is working again, thank you!

 nieroster wrote:
 

Sorry. Looks like European listeners are temporarily being routed back to our US servers. Checking on that. Should be good again shortly.

After it worked perfectly for some hours, it started to drop out again now.

Yes, last 1h also working on my side..... sorry for the inconvenience from my side........ well this means for all of us...... let us send the deserved trophy-fee to RP...... :-) :-)

 raoul2 wrote:
 

Then I am more than happy for you.... :-)..... yes, it works much better than in the last days. But I had drop out after 15 minutes. I will continue to try..... how it works....

 nieroster wrote:
 

 raoul2 wrote:
 

For me it's still working without dropouts

Uppps. It seems, I was to fast.

I still have dropouts. They are coming later. But there are..... sorry, guys.....

 BillG wrote:
 

Wooooooow. Bill & Rebecca. You are geniouses..... You did it (using nike-words..... :-) I promised to send additional RP-fees, when you have sorted out the technical issues. And, I will.

I kindly send out this message to all of us, pushing you to solve the issue, and mentioning how much they love RP, etc. I think, these people should not only talk about it, but also follow me now, and also sending an "appreciation-Fee" to RP. If you do so. Please talk about it in this forum. Maybe it will motivate others of us, to follow......

Cheers.
Raoul from Switzerland

It's working seemlessly again!
Thank's a lot!

 raoul2 wrote:
 

Our new European server should be online later today (tomorrow at the latest) and should fix the issues.

Hello Everybody

I don't know, what happened with the RP-Music-Distribution in Europe. But there seems to be a problem. Changed settings at a crucial server, outdated certificates, or what ever. The drop outs don't seem to be limited to bluesound. We all know that Bill is trying to do his best, but maybe he has limited resources to find the issue.

This is the point, where I want to start an initiative. I say, that I will pay an additional USD 20 for 6 months Radio Paradise as soon as the problem is fixed. If many of us would follow me, Bill would be motivated / incentiviced  - and can explore maybe more ressources - to dig more into the problem.

Please join me in promising additional USD 20 to RP, when Bill will have fixed all the streaming issues for Europe. The quality and the future of RP justifies this additional money.....

Looking forward hearing news from you out there......


raoul (from Switzerland)

 raoul2 wrote:
 
The issue is network congestion & latency between our US-based servers and Europe, due primarily to the massive increase in people working from home.

We're configuring a server in Germany to handle Bluesound, Sonos, & phone app listeners in Europe. Should be online within the next day or so. No changes necessary at your end.

I am not a network specialist. But is it correct, that all your suggestions cannot be applied by using Bluesound, because you cannot change vpn and other solutions for Bluesound. One has no access to such changes with the bluesound components. 

RB still not working with Bluesound in Switzerland at the very moment...... dropouts on all RP-Streams.....

Is there a chance for a fix in the future, or will it stay like this? 

raoul

 BillG wrote:
 

thanks BillG !

I will test it if you have activate the new server!

And thanks for your great radiostation in  this times !

Robert

 nieroster wrote:
 
Ich versuche es mal auf deutsch:

Kannst du mal einen VPN Server benutzen, die gehen meistens wirklich über IPV4?
Versuche mal den Stream im Browser abzuspielen, dort hatte ich die selben Probleme, lag also nicht am Bluesound!

Ich nehme auch an, selbst wenn du deine Modem auf IPV4 umstellst benutzt dein Provider ein  IPV6 durch das ein IPV4 Adresse gestackt wird?
Probiere mal

https://www.wieistmeineip.de/ipv6-test/

Vielleicht kann ich dir ja doch noch helfen?
Die unterscheidlichen IP adressen liegen an den AMAZON Server, die anscheinend in Seattle liegen, Amazon benutzt mehrere.

Wie gesagt, beides hat bei mir funktioniert:
VPN zwischenschalten, oder Umstellung beim Provider auf reines IPV4 (das machen die eigentlich nur noch bei business, da zu wenig IP4-Adressen frei sind)!

Thanks a lot Bill!

We are adding a new server in Germany, dedicated to European FLAC listeners. Should be active within a couple of days & will hopefully solve the problems. 

Why can't I deactivate IPv6 myself? I have set up a 6in4 tunnel on my router, which I can esily deactivate.

Here are the ping results:
C:WindowsSystem32>ping -6 radioparadise.com

Ping wird ausgeführt für radioparadise.com <2600:9000:20ac:0:15:bb0f:1a80:93a1> mit 32 Bytes Daten:
Antwort von 2600:9000:20ac:0:15:bb0f:1a80:93a1: Zeit=49ms
Antwort von 2600:9000:20ac:0:15:bb0f:1a80:93a1: Zeit=52ms
Antwort von 2600:9000:20ac:0:15:bb0f:1a80:93a1: Zeit=54ms
Antwort von 2600:9000:20ac:0:15:bb0f:1a80:93a1: Zeit=57ms

Ping-Statistik für 2600:9000:20ac:0:15:bb0f:1a80:93a1:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 49ms, Maximum = 57ms, Mittelwert = 53ms

C:WindowsSystem32>ping -4 radioparadise.com

Ping wird ausgeführt für radioparadise.com <99.86.243.3> mit 32 Bytes Daten:
Antwort von 99.86.243.3: Bytes=32 Zeit=12ms TTL=244
Antwort von 99.86.243.3: Bytes=32 Zeit=8ms TTL=244
Antwort von 99.86.243.3: Bytes=32 Zeit=6ms TTL=244
Antwort von 99.86.243.3: Bytes=32 Zeit=6ms TTL=244

Ping-Statistik für 99.86.243.3:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 6ms, Maximum = 12ms, Mittelwert = 8ms

What I've noticed is that I seem be be using a different server than you do.

 robertft wrote:
 
What are the results of a ping and traceroute?

For me:
Ping wird ausgeführt für radioparadise.com <54.192.87.88> mit 32 Bytes Daten:
Antwort von 54.192.87.88: Bytes=32 Zeit=25ms TTL=245
Antwort von 54.192.87.88: Bytes=32 Zeit=20ms TTL=245
Antwort von 54.192.87.88: Bytes=32 Zeit=16ms TTL=245
Antwort von 54.192.87.88: Bytes=32 Zeit=14ms TTL=245

Ping-Statistik für 54.192.87.88:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),

tracert radioparadise.com
1 private
2 private
3 10 ms 10 ms 9 ms 213.51.198.69
4 14 ms 13 ms 12 ms asd-tr0021-cr101-be153-10.core.as9143.net <213.51.158.50>
5 20 ms 12 ms 15 ms nl-srk03a-ri1-ae51-0.aorta.net <213.51.64.198>
6 15 ms 26 ms 16 ms 52.46.167.242
7 15 ms 15 ms 14 ms 52.93.113.30
8 14 ms 15 ms 15 ms 150.222.107.13