Third party feed isn't triggering update to our page

[Philip Colmer]

Our Statuspage is configured to monitor two feeds from Auth0:

Auth0 have had an outage:

but nothing changed on our Statuspage. We've had to manually add an incident in order to reflect the fact that Auth0 is having a problem.

Why has this happened? I thought the whole point of the third party connections was to simplify the monitoring & display of issues from those third parties.

[Kevin Allen · Accepted solution]

Hi there, I can't say for sure, but if per the documentation here https://support.atlassian.com/statuspage/docs/add-a-third-party-component/: 

My third-party component is down, what happens?

Depending on the status we parse or have from the external service's status page, we will auto-degrade your third-party component accordingly.

For example, if Mailgun is reporting degraded performance for outbound delivery, Statuspage auto-degrades the component on your page as well. Once Mailgun switches their status back to operational, Statuspage auto-updates your third-party component status back to operational.

We do not send any notifications for third-party status changes to your subscribers.

Potentially, they may have flipped there's after you noticed the problem and flagged it. 

If you want to get to the bottom of this, you should definitely file a ticket with support, https://support.atlassian.com/statuspage/. 

Cheers!

[Philip Colmer]

Unfortunately, I can't file a ticket with support because we're currently on the free plan. We're on the free plan because we're still evaluating Statuspage and this failure to feed through the notification from Auth0 hasn't helped.

I hadn't realised that third-party status changes aren't fed to subscribers either. So using the third-party feed is a complete waste of time for us and now we'll have to implement our own proactive monitoring of Auth0.