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/[email protected]/
[atlas] A number of built-ins stopped?
- Previous message (by thread): [atlas] A number of built-ins stopped?
- Next message (by thread): [atlas] A number of built-ins stopped?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ernst J. Oud
ernstoud at gmail.com
Fri Dec 23 18:25:14 CET 2022
L.S. All the probes in NL that I had a look at, in a variety of different ASN’s, have no data available via the Atlas web of via the api (JSON, Magellan) for a.o. built-in measurement 1009 (ping to a.root-servers.net) and several others after December 22nd, around 18:00 hrs. UTC. When I have a look at German probes there is data available. This thus appears to be a problem with all and only Dutch probes’ data. A normal ping via a Windows command line works fine, i.e. a.root-servers.net is reachable. Creating a ping measurement via Magellan to a.root-servers.net using Dutch probes generates results, i.e. the probe infrastructure works but data storage does not, for data from probes in NL. Rather serious problem I guess. No mentioning on status.ripe.net though. Had an email conversation with Robert from the Atlas team today. No solution yet. Regards, Ernst J. Oud Met vriendelijke groet, Ernst J. Oud
- Previous message (by thread): [atlas] A number of built-ins stopped?
- Next message (by thread): [atlas] A number of built-ins stopped?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]