Skip to content
Why does the status page show 99.48% for builds when your incident log shows Pro builds down for ~22 hours?
scottie-capturra
OP

24 days ago

I am curious as to what the status page is reporting off of?

There seems to be discrepancies between the incident logs and the reported downtime.

We are having questions from clients about our apps downtime during the Oct. 21st incident and do not know whether to quote the incident logs downtime or your published downtime in the visuals?

(Was discussed in this thread here with no response from railway: http://station.railway.com/questions/build-failed-in-all-builds-d9c109f5#nj8x)

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

The uptime bars on our public uptime dashboard are a summary for each platform component, so the Builds figure describes our build system rather than whether your apps were reachable. We can't give you a breakdown of how that specific 99.48% was calculated, so it isn't the right number to quote to clients for this incident.

For the October 21 incident, running services kept running their last successful deployment throughout, while new builds and deployments were paused until they were restored on October 22. The preliminary report has the timeline for that pause.

For your clients, the report's timeline covers the period when changes couldn't be deployed, and actual app downtime is best taken from your own monitoring or request logs, since the pause did not take running services offline.


Status changed to Awaiting User Response dizzydes90 • 24 days ago


dizzydes90

The uptime bars on our public uptime dashboard are a summary for each platform component, so the Builds figure describes our build system rather than whether your apps were reachable. We can't give you a breakdown of how that specific 99.48% was calculated, so it isn't the right number to quote to clients for this incident. For the October 21 incident, running services kept running their last successful deployment throughout, while new builds and deployments were paused until they were restored on October 22. The [preliminary report](https://blog.railway.com/p/preliminary-report-october-security-incident) has the timeline for that pause. For your clients, the report's timeline covers the period when changes couldn't be deployed, and actual app downtime is best taken from your own monitoring or request logs, since the pause did not take running services offline.

scottie-capturra
OP

24 days ago

Thanks for the clarification.

Just to confirm our understanding so we can answer client questions accurately:

  • The public status page currently shows Builds at 99.48% for October (~3.4 hours of counted downtime month-to-date).
  • The incident timeline shows new builds and deployments paused for Pro from roughly 07:24 UTC on Oct 21 until ~07:11 UTC on Oct 22 (~24 hours), with similar or longer pauses for other tiers.
  • You’ve noted that the 99.48% figure isn’t the right number to quote for this incident and that the preliminary report has the correct timeline for the pause.

Could Railway update the status page so the uptime figures and the incident timeline are consistent and everything is visible on the same page? Clients are checking the public status page directly and seeing a discrepancy with the ~24-hour pause shown in the incident log, which is making it harder for us to give them a clear picture.


Status changed to Awaiting Railway Response Railway • 24 days ago


dizzydes90
EMPLOYEE

24 days ago

Your three points are accurate. We've passed your request on to the team that owns the status page. The uptime bars and the incident entries are maintained separately, and we can't promise that the October figure for Builds will be revised retroactively.

For your clients, the incident entry on the status page and the preliminary report's timeline are the record of the deployment pause, and you can cite them directly: builds and deployments were paused, and running services kept serving their last successful deployment throughout.


Status changed to Awaiting User Response Railway • 24 days ago


Railway
BOT

17 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 17 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...