This issue should now be resolved for all probes. We are putting some monitoring in place to ensure that it doesn't reoccur.
Apologies for the inconvenience. Cheers, Chris On Wed, 19 Mar 2025 at 14:46, Christopher Amin <[email protected]> wrote: > Hello, > > I have applied a fix to just your probe, can you check to see whether the > connection history looks accurate now? > > Cheers, > Chris > > On Wed, 19 Mar 2025 at 11:31, Christopher Amin <[email protected]> wrote: > >> Hi Anton, >> >> You're not the only one to be affected by this issue. We're investigating >> it currently and I'll send an update here once we know more. >> >> Regards, >> Chris >> >> On Wed, 19 Mar 2025 at 09:01, Anton Bobov via ripe-atlas < >> [email protected]> wrote: >> >>> >>> Hello! >>> >>> I am experiencing an issue with incorrect uptime and connection history >>> for my >>> probe (ID: 1006959 https://atlas.ripe.net/probes/1006959/network). >>> >>> I am currently running a software probe on Rocky Linux 8.10, with the >>> probe >>> version 5100. There was a power outage between 2025-03-14 04:25 and >>> 2025-03-14 >>> 05:25 (UTC), which seems to have affected the data. >>> >>> I downloaded the connection history for the specified period, and it >>> shows the >>> following entries: >>> >>> seq timestamp (UTC) event stored_timestamp (UTC) >>> ---------------------------------------------------------------------- >>> 1 2025-02-08 23:13:51 disconnect 2025-02-08 23:13:51 >>> 2 2025-02-08 23:17:18 connect 2025-02-08 23:17:18 >>> 3 2025-03-14 04:25:35 disconnect 2025-03-14 04:25:36 >>> 4 2025-03-14 05:25:06 connect 2025-03-14 05:25:06 >>> 5 2025-03-14 06:49:19 disconnect 2025-03-14 06:49:19 >>> 6 2025-03-14 06:52:46 connect 2025-03-14 06:52:47 >>> 7 2025-03-15 22:36:49 disconnect 2025-03-15 22:36:50 >>> 8 2025-03-15 22:39:17 connect 2025-03-15 22:39:17 >>> >>> However, entries [2] to [7] are missing from the connection history, and >>> only >>> [1] (last disconnect) and [8] (last connect) are displayed. >>> Additionally, this >>> period is also missing from the uptime history. >>> >>> Could this be a bug, or is there another explanation for this issue? >>> >>> -- >>> Cheers, >>> Anton >>> ----- >>> To unsubscribe from this mailing list or change your subscription >>> options, please visit: >>> https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ >>> As we have migrated to Mailman 3, you will need to create an account >>> with the email matching your subscription before you can change your >>> settings. >>> More details at: >>> https://www.ripe.net/membership/mail/mailman-3-migration/ >>> >>
----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-atlas.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/
