Client unable to connect...

[patmcc24]

Have had this issue going on 3 hours using RadioFeed and ProScan... anyone else?

 

[patmcc24]

may have found the issue.... after running a tracert it gets lost in Chicago.... and ping times out.....

 

[patmcc24]

update again... sorry... Scannercast connects with no issues

 

[w9zro]

now mine wont connect using radiofeed

 

[see7]

Having issues as well with scannercast and audio1 server. So far tried ipconfig /flushdns, but still unable to start scannercast. Pinging audio1.broadcastify.com is working

 

[RaleighGuy]

Happening now! Have internet, but Audio1 feed won't connect to server. Anyone else having issues?

 

[nick0909]

Same issue here, looks like some rolling updates or issues, hopefully fixed soon.

 

[NJFireD1]

my feed is also down on audio1.broadcastify.com

 

[w9zro]

ok i feel better it is not just me

 

[Kelita]

Same here, my feed is down.

 

[jbeen]

Yup, my feed on audio1.broadcastify.com is offline.
The feeds connected to audio3 & audio9 are currently happy.
Looks like roughly 1/2 the Colorado feeds are down.

Josh

 

[n0nhp]

My audio3 feed is fine, audio1 is unable to connect, Hopefully Lindsay is aware and doing something about it
I can ping the server with no problem so it must be software

 

[mckinscan]

My Same doing same thing and my is on Audio 1 also

 

[gillham]

Checking in. My server won’t connect.


Sent from my iPhone using Tapatalk

 

[WD433]

Same here, just all went offline suddenly. Tried with Radiofeed, been auto-reconnecting for last 30 mins now.

Scanner and internet are fine, seems like server issue with Broadcastify.

 

[JoshuaHufford]

Same here, I'm getting an error saying the target machine actively refused the connection. There is more info I can provide from the error message if needed.

 

[n0nhp]

Lindsay is on it, he posted just seconds ago
https://forums.radioreference.com/threads/audio1-master-server-is-down-2-4-2018-7pm-cst.383183/

 

[csadoian]

I have two feeds, one is on audio1.broadcastify.com, the other is on audio3.broadcastify.com. audio1.broadcastify.com is the one that is down and has been down for a little over 40 minutes. Pretty obvious a problem with server, it probably needs to be rebooted