One of the Broadcastify Calls servers appears to be down

[mtindor]

About 35-40 minutes ago my ingest machine lost connection with Broadcastify. I fired up SDRTrunk again and it says it cannot connect to Broadcastify -- 502 Bad Gateway.

Just an FYI. Not sure who all it affects. But it affects my AEP and Ohio MARCS (JEfferson) ingest feeds.

m

 

[norwichfeeder]

Same. Also I cannnot connect to any of my regular feeds with any app.

 

[morrisr3nd]

I'm still connected. I provide a feed.

 

[norwichfeeder]

I'm still connected.

I was too, till I reset my feed PC.

 

[ChrisABQ]

What server are you on?

 

[louisik1]

I'm still connected.

When I received the offline notification I checked my system and sdrtrunk still showed as connected and still showed that calls were being sent to it, but no calls were being listed at my calls node page. I disconnected from the calls node and reconnected and now it won't connect it just keeps trying.

I'm sure they are aware and working on it, no worries.

 

[morrisr3nd]

audio3.broadcastify.com

 

[norwichfeeder]

Appears to be a server issue. Scanner Radio app not connecting but I can listen to my feeds on a PC though.

 

[norwichfeeder]

Only a small handful of my listeners can reconnect after I rebooted. No scanner radio apps will connect to any of my 5 feeds. But can listen on the website.

 

[bubbablitz]

If you go through the broadcastify.com site, you can listen that way. I checked different feeds and they all worked.

 

[norwichfeeder]

If you go through the broadcastify.com site, you can listen that way. I checked different feeds and they all worked.

Yeah this is an issue with all scanner apps and some calls nodes. Once you disconnect they won't reconnect.

 

[norwichfeeder]

I only relized this was an issuse when I stopped sacnner radio pro to make a phone call. Then I try to reconnect scanner app after the call. None of my scanner app will connect to any server. Even my own. I reset my own feed PC and my reg feeds are connecting, web browser only, but my CALLS nodes are down. They show error. No one using a scanner app, of any kind , seems to be able to reconnect to my feeds.

 

[Kingscup]

I am receiving a “502 Bad Gateway” error upon upload to the Calls system.

 

[wordmoss]

It appears to be an AWS outage. Multiple sites are having issues.

 

[norwichfeeder]

I may take all my regular feeds offline until this is fixed, I can imagine all my listeners , that use scanner apps are pulling their hair out right now.

 

[norwichfeeder]

Has anyone notified @blantonl ??

 

[mtindor]

Has anyone notified @blantonl ??

@blantonl has assured us many many times that he knows when something is wrong well before we are aware. So I do not attempt to reach out to him directly. I just wait until services are restored. Good time for system maintenance on my end anyway.

 

[kwnj]

AWS is having issues, might be related to that. Our systems at our work went down about 3PM ET.

 

[norwichfeeder]

Yup. We sit and wait.

 

[HarryWilly]

AWS is having degraded service. Probably the cause.