From midnight 1 January until approximately noon 2 January there were no built-in measurements running. This is due to an overlooked fact where
Happy new year to all RIPE Atlas users! It seems we've given a little break to our probes so they can celebrate the new year too ... the built-in measurements had a pre-defined end date of 2020-01-01. The system dutifully observed this date and did not schedule these measurements any more. We fixed this setting on Thursday, 2 January and the system returned to normal operations shortly thereafter. As a consequence, there's a gap in the delivered measurement results for built-in measurements (i.e. IDs < 1 million). Results for the User-Defined Measurements were not affected. Please accept our apologies for the inconvenience this can cause. Regards, Robert Kisteleki
On Fri, Jan 03, 2020 at 12:04:37PM +0100, Robert Kisteleki <robert@ripe.net> wrote a message of 22 lines which said:
an overlooked fact where the built-in measurements had a pre-defined end date of 2020-01-01 [...] We fixed this setting on Thursday, 2 January
What is the new date? Before or after the Y2038 bug? :-)
On 2020-01-03 12:10, Stephane Bortzmeyer wrote:
On Fri, Jan 03, 2020 at 12:04:37PM +0100, Robert Kisteleki <robert@ripe.net> wrote a message of 22 lines which said:
an overlooked fact where the built-in measurements had a pre-defined end date of 2020-01-01 [...] We fixed this setting on Thursday, 2 January
What is the new date? Before or after the Y2038 bug? :-)
2147126400 == Fri Jan 15 01:00:00 CET 2038 So just *slightly* before! :-) Cheers, Robert
participants (2)
-
Robert Kisteleki -
Stephane Bortzmeyer