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] Result delivery issues - 2021-05-11
- Previous message (by thread): [atlas] Result delivery issues - 2021-05-11
- Next message (by thread): [atlas] Result delivery issues - 2021-05-11
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Stephane Bortzmeyer
bortzmeyer at nic.fr
Tue May 11 11:41:05 CEST 2021
On Tue, May 11, 2021 at 09:37:51AM +0200, Robert Kisteleki <robert at ripe.net> wrote a message of 11 lines which said: > The RIPE Atlas result storage backend started experiencing issues today at > around 3am (CEST). The team is working on resolving the issue; we'll provide > an update when more information is available. Is it also for this reason that measurements only get very few probes? {'is_oneoff': True, 'definitions': [{'description': 'DNS resolution of dnsdist.org/AAAA', 'af': 4, 'type': 'dns', 'query_argument': 'dnsdist.org', 'query_class': 'IN', 'query_type': 'AAAA', 'set_do_bit': True, 'udp_payload_size': 4096, 'set_rd_bit': True, 'protocol': 'UDP', 'use_probe_resolver': True}], 'probes': [{'requested': 100, 'type': 'area', 'value': 'WW', 'tags': {'include': ['system-ipv4-works', 'system-resolves-a-correctly', 'system-resolves-aaaa-correctly']}}]} But measurement #30113470 only got 6 probes.
- Previous message (by thread): [atlas] Result delivery issues - 2021-05-11
- Next message (by thread): [atlas] Result delivery issues - 2021-05-11
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]