Hello everyone,
I'm reporting a timezone parsing bug in the Web GUI's Speedtest/QoS module that affects fractional timezones, specifically IST (UTC+5:30).
When running a speed test from the router's web interface, the timestamp recorded in the history log is exactly 30 minutes behind the actual system time. It appears the Web GUI truncates the +5:30 offset to +5:00 when writing the history log.
Hardware & Firmware:
Thu Mar 19 11:32:38 GMT 2026
However, the GUI timestamp will be exactly 30 minutes behind the terminal output.
Expected Behavior:The front-end Web GUI should correctly parse the 30-minute fractional offset and display the exact same time as the underlying system clock.
Has anyone else in a fractional timezone noticed this UI truncation? I tried submitting this via Administration -> Feedback, but the router's internal feedback module seems to be broken right now.
I'm reporting a timezone parsing bug in the Web GUI's Speedtest/QoS module that affects fractional timezones, specifically IST (UTC+5:30).
When running a speed test from the router's web interface, the timestamp recorded in the history log is exactly 30 minutes behind the actual system time. It appears the Web GUI truncates the +5:30 offset to +5:00 when writing the history log.
Hardware & Firmware:
- Router: Asus TUF-AX4200
- Firmware: 3.0.0.4.388_34011
- Configured Timezone: (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi
- Set the router's System Timezone to UTC+05:30.
- Run a speed test via the Web GUI.
- Check the completion timestamp in the GUI history.
Thu Mar 19 11:32:38 GMT 2026
However, the GUI timestamp will be exactly 30 minutes behind the terminal output.
Expected Behavior:The front-end Web GUI should correctly parse the 30-minute fractional offset and display the exact same time as the underlying system clock.
Has anyone else in a fractional timezone noticed this UI truncation? I tried submitting this via Administration -> Feedback, but the router's internal feedback module seems to be broken right now.