4 months ago
Hi
I'm a little confused about something. I live in South Africa - rationale for the mention below.
Upon deploying a GitHub project, the timestamps on my deploy logs are current while the info containted in the build/deploy logs seem to be about 2 hours behind.
Am I seeing/experiencing this due to a legitimate timezone delay or is it a "Pro" or "Paid" feature to have immediate/current build/deploy log times?
Pinned Solution
4 months ago
The time might be listed in UTC. South Africa is UTC+2, so times would appear to differ by 2 hours.
Edit: typo
5 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
4 months ago
The time might be listed in UTC. South Africa is UTC+2, so times would appear to differ by 2 hours.
Edit: typo
4 months ago
The Servers are in UTC (being closest). I'm UTC +1 and my logs are also always 1 hour behind. It shows server-time. Hope that helps :)
4 months ago
hey kavish85,
Adding on to the other two answers here:
The servers and build system do run in UTC internally, but the Railway dashboard doesn’t show raw server time. Both the Build Logs and Deploy Logs are converted into your local timezone before being displayed. This means:
* The build system uses UTC under the hood
* But the timestamps you see in the UI are shown in your local time
* If your runtime logs use a different timezone (e.g., UTC+2), you may see a mismatch
So the difference you’re seeing isn’t a delay or a paid feature, it’s just two different systems using different timezones for their log output.
Status changed to Solved noahd • 3 months ago