Inconsistent Time Zones Between Call Logs and API ...
# support
r
While reviewing the VAPI dashboard, I noticed an inconsistency in the timestamps displayed between the call logs and the API request logs. I was trying to locate a specific call and match it with the corresponding HTTP request to the API that triggered it. However, the timestamps in both listings appear to use different time zones, which makes it difficult to correlate events accurately. Could you please confirm whether this is a known issue or if there’s a setting that should be adjusted to align the time zones? https://cdn.discordapp.com/attachments/1433467006165975112/1433467006476091453/Screenshot_2025-10-30_at_9.39.18_AM.png?ex=6942c22e&is=694170ae&hm=1e66e73503e3eab6970a389c93bfc286c0bbbb82384d0cc5018a8613f3681d96& https://cdn.discordapp.com/attachments/1433467006165975112/1433467006861971523/Screenshot_2025-10-30_at_9.40.16_AM.png?ex=6942c22e&is=694170ae&hm=bd7460080278a02e7e75198483e58c492fd56326522bb01762e45386b06c2616&
v
Nice catch — that timestamp mismatch can definitely cause confusion. I can help you check if it’s just a timezone offset between the dashboard (usually UTC) and your local logs. Could you share which environment you’re viewing this from (staging or prod)? That’ll help confirm if it’s config-related or a known display issue. @rmaceissoft