This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Data delays on RIPE Atlas
- Previous message (by thread): [atlas] Data delays on RIPE Atlas
- Next message (by thread): [atlas] [rfc-editor at rfc-editor.org: [lmap] RFC 7594 on A Framework for Large-Scale Measurement of Broadband Performance (LMAP)]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Romeo Zwart
romeo.zwart at ripe.net
Sat Sep 19 09:32:57 CEST 2015
Thanks to those who prompted me offline. :) There will of course be more info on what happened yesterday, but that will come after the weekend. Kind regards, Romeo > On 18 sep. 2015, at 21:50, Romeo Zwart <romeo.zwart at ripe.net> wrote: > > Dear all, > It took a few hours to identify the underlying problem and some more to > consume the backlog of messages that had been created in the mean time. > At the moment all backlogs have been cleared up and processing has > returned to normal. > > Again apologies for the inconvenience. > > Kind regards, > Romeo > >> On 15/09/18 13:31 , Robert Kisteleki wrote: >> Dear all, >> >> The data backend behind RIPE Atlas is experiencing some issues at the >> moment. This causes delays in processing and serving the data, meaning all >> results are delivered late. >> >> We're working on a fix. Excuses for the inconvenience. >> >> Regards, >> Robert > >
- Previous message (by thread): [atlas] Data delays on RIPE Atlas
- Next message (by thread): [atlas] [rfc-editor at rfc-editor.org: [lmap] RFC 7594 on A Framework for Large-Scale Measurement of Broadband Performance (LMAP)]
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]