DCAT end points failing with 502 or 503 errors?

[JimLacy]

Hi Folks-

I'm observing sporadic issues processing DCAT endpoints.  Symptoms:  with no particular identifiable pattern, I get a 502 "bad gateway" or 503 "service temporarily unavailable" error.  This is not isolated to a single Open Data/Hub site. Examples:

https://data-wi-dpi.opendata.arcgis.com/api/feed/dcat-ap/2.1.1.json

https://data-waukesha.opendata.arcgis.com/api/feed/dcat-ap/2.1.1.json

https://data-cityofmadison.opendata.arcgis.com/api/feed/dcat-ap/2.1.1.json

https://data-wisdot.opendata.arcgis.com/api/feed/dcat-ap/2.1.1.json

... it's entirely possible and likely when you click any of the above it will work.  But that's the issue... sometimes works, sometimes not.

I did open a tech support case on this, but didn't get any traction because it's an intermittent problem.  When the tech support folks happen to visit the link, it works... therefore no problem.

Wondering if anybody else has experienced this. Or even confirming if you get an error on any of the above would be helpful!

Thanks!

[ThomasHervey1]

@JimLacythanks for reaching out,
We're currently investigating a service disruption. We will post an update once we have determined the source of the issue and an expected resolution timeline. We're sorry for any inconvenience this has caused.

[ThomasHervey1 · Accepted solution]

This issue was resolved within an hour of identification. We've adjusted our alerting system to ensure that in the future we will know sooner when there is an outage and minimize downtime.

We apologize for any inconvenience this may have caused.

[JimLacy]

Nice!  Thanks so much for you/team looking into this.  I've been checking urls, and so far the DCAT stuff now seems to be behaving as expected.