L.S. If for some reason this api error bug takes longer to resolve and the data is important for you, a work around is to download this data from ripestat. Click on the link on your builtins page for the larger graph and click the download button top right. Use this download link to download future data by changing the start and end time in the URL.
Reason I use the data from the first hop latency is that my CentOS probe in a VMware Player VM on Windows 10 (bridged) takes 2-3 ms. for the first hop. To get more realistic data for other measurements I subtract this first hop latency data from data of other measurements. Wrote some Freebasic code for this and created my own graphs using the good, old, trusted application ploticus. >From the host Windows 10 PC first hop is max 0.5 ms. so the VMware software >bridge is not very efficient to get a connection going. If the CentOS VM is >kept busy, the first hop is much faster. It is as if Windows and/or VMware >suspends/sleeps the thread of the bridge when not active. I searched but did >not find any more reports let alone solutions for this weird first hop >phenomenon in VMware/Windows environments. Regards, Ernst J. Oud -- ripe-atlas mailing list [email protected] https://lists.ripe.net/mailman/listinfo/ripe-atlas
