@agusSupriono2
After reviewing the situation, it seems the issue is not with our servers but is likely related to how your trackers are determining the time.
This is a common issue with some older devices. For various technical reasons, their internal clocks can “roll over” and reset to a default starting date (an epoch date), which might be many years in the past.
When a tracker sends data with an incorrect timestamp (e.g., a date from the year 2000), our system cannot process it correctly, which is why the notifications stopped, even though the trackers themselves seem to be working.
There are two common ways to solve this problem:
Firmware Update (Reflashing): The most reliable solution is to update the firmware on your devices. Manufacturers often release updates to fix these time-related bugs. Please check the manufacturer’s website for your specific tracker models for the latest firmware and update instructions.
Configuration: It might be possible to fix this through the device’s configuration settings, for example, by manually setting the correct date and time or adjusting the time synchronization parameters.
We recommend starting by checking for a firmware update from the device manufacturer.
I hope this helps clarify the situation.
