Skip to content
Read-only host clock uncertainty evidence inside a Railway container
bookedbot
OP

22 days ago

Our application has security waiting periods and needs verifiable time evidence. A single read-only modes=0 adjtimex query in a Linux x86_64 container returned TIME_OK, status 0x6001, maxerror 491500 microseconds, esterror 0, and discipline_offset 285338 nanoseconds (STA_NANO). Its measured read window was 3.070128 ms.

We are not claiming the actual clock is wrong by that amount. Our current application gate requires reported maximum error plus read window to be at most 250 ms, so this snapshot was rejected.

Is there a supported machine-readable source of synchronization status and conservative UTC-error bounds available inside containers with existing ordinary privileges? If kernel adjtimex is the intended surface, what behavior/bounds can be expected, including after host migration or restart? If no supported bound is available, please confirm so we can assess an independent authenticated time source.

We are not requesting clock changes, added capabilities, host changes or a paid upgrade. Please identify any official documentation or obtain platform-team confirmation; we will not treat an automated reply alone as a clock attestation.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 22 days ago


Railway
BOT

22 days ago

An adjtimex read inside your container returns the clock state of whichever host is running it at that moment. Your service can move to a different host when it redeploys, restarts, or is migrated during host maintenance, so a bound you read on one host does not carry over to the next.

We can't give you a guaranteed UTC error bound or a clock attestation in this reply. If your security gate needs a verifiable bound, your plan to check against an independent authenticated time source is the safer basis for it.


Status changed to Awaiting User Response Railway • 22 days ago


Railway
BOT

15 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 • 15 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...