Probe overview - event log - connection time only shows hh:mm:ss, not showing days

RIPE Atlas
1

Suppose I look at at probe with a URL like this
https://atlas.ripe.net/probes/xxxxxxx/overview

Looking at the Event Log, the “Connected For” column only shows the hours:minutes:seconds even if the actual time is for multiple days.
See example on screenshot - the uptime is some seven days plus eight hours or so - but you only see the “remainder”.

Is this as intended, or is there a way of getting the “days” included too.

image
image876×138 11.7 KB

2

Hi Daksol,

Thanks for reporting this. The best place to see “connected for” timings is in the network panel (at the bottom) under “Connection History”:

https://atlas.ripe.net/probes/xxxxxxx/network

The Event log, on the other hand, is meant to combine several different types of events from several different sources to simply show the timestamps of those reports in one place for debugging purposes. We will be removing the “connected for” and “disconnected for” columns from this table in the near future to avoid this confusion.

Kind regards,
Stephen
Atlas UI

1 Like
3

The issue is incorrect reporting of time - one of many, in fact. Removing the column rather than fixing the actual bug does not reflect well on the Atlas team. (I do applaud adding “events” to the normal UI. It’s always existed, but you had to know where to go to see it.) If you’re going to make previously “internal” diagnostic information public, you’re going to need to support public use of it.

4

Upate on previous post. The format of the Event log has changed since I posted back in April 2025, in that the “Connected For” column has gone. However the “Uptime” column still there, and from what I can see it is still making the same error, in that it shows only the hh:mm:ss component of the Uptime, and does not include the Days.

5

Hi Daksol,

Thanks for pointing this out, this column should also have been removed. As mentioned before, the best place to find accurate connection information is in the Network panel, not the Overview panel. The event log we show on the overview is a convenience really meant to show events (without calculation), which is what those extra columns were (erroneously) attempting to do. We may one day revisit this older, adapted code, but for now please rely on Connection History table in the Network tab, it is the most accurate info and specifically built to answer questions of this sort. We will remove the column in the event log shortly to avoid any further confusion.

Kind Regards,

Stephen
Atlas UI

1 Like