- ripe-atlas - mailman.ripe.net

Broken traffic graphs in latest firmware (5010)
by Philip Homburg 10 Mar '20

10 Mar '20

Hi, A change in the RIPE Atlas probe code to make reporting traffic statistics optional in software probes (and disabled by default) has the unfortunate side-effect that reporting of traffic statistics is now disabled on Version 3 and Version 4 hardware probes, as well as all anchors. This change was rolled out in firmware version 5010. Unfortunately, this effect was not spotted during testing. We will roll out a new firmware release that corrects this issue in coming weeks. Philip

1 0

Reg query of code
by Adarsh Pandey 24 Feb '20

24 Feb '20

Dear Team Can we get the code of ripe atlas server Regards ADARSH PANDEY NKN

2 1

check dns64/nat64 behavior ?
by Thomas Schäfer 21 Feb '20

21 Feb '20

Hi, is there a simple way to check the reachability of IPv6 targets by probes behind NAT64? e.g. If I try to ping www.t-online.de with Adress Family IPv6 I get immediately the error " No IPv6 address found for target" instead of "measuremnet created". Same problem exists for DNS measurements. Regards, thomas

2 2

Probes were incorrectly not tagged with the stability tags
by Chris Amin 21 Feb '20

21 Feb '20

Dear colleagues, Over the past month there have been issues with the "system-ipv[45]-stable-{1,30,90}d" tags, which were not applied to many of the probes that should have had them. This was caused by accidental data format changes from a backend migration. The issue should now be fixed, so probes will have the correct tags applied. If you notice any persisting issues then please let us know! Apologies for any inconvenience. Kind regards, Chris

2 2

atlas probe down
by MAYER Hans 19 Feb '20

19 Feb '20

Dear All, Our Atlas probe with ID 35603 is down since Wednesday exactly 12:00 LT. I unplugged power and powered on, but no success. After power on some LED's are blinking. Finally the power LED stays on and the LED next to it is blinking. But I can't ping this probe. Either on IPv4 nor on IPv6. We got this probe in summer 2018. So I can't believe it's EOL. Any ideas what I can do ? Kind regards Hans --

2 2

Can I issue a traceroute measurement with multiple targets?
by Vasileios Giotsas 11 Feb '20

11 Feb '20

If I have 100 IPs to target from a single probe, is it possible to create a single measurement with 100 targets similar to how I'd do if I wanted to target a single IP from 100 probes? I've read through the Atlas API documentation and couldn't find anything like that but it looks like some of the built-in measurements do that. Thanks, Vasilis

2 2

Atlas API stream broken?
by Teun Vink 10 Feb '20

10 Feb '20

Hi, Since ~13.30h CET this afternoon our Atlas data stream subscriptions (using the ripe.atlas.cousteau python library) stopped receiving updates. Earlier today we (at 11.27h) observed some issues with the backend where we received redis errors, which were resolved at ~12.09h CET. I heard these were related to some firewall issues, could these problem be related? Regards, -- Teun Vink BIT | teun(a)bit.nl | +31 318 648 688 KvK: 09090351 | GPG: 0xFC8B25D6 | RIPE: TEUN-RIPE

2 1

Graphs and measurements are scaled by a factor of 1000
by Enrico Ardizzoni 07 Feb '20

07 Feb '20

Starting from 06/02/2020 at 6.00 AM UTC all graphs and measurements are scaled by a factor of 1000. Something went wrong on probes backend... "An error occurred while retrieving measurement data. We apologise and do our best to fix it asap!" See: https://atlas.ripe.net/probes/249/#!tab-builtins https://atlas.ripe.net/probes/12120/#!tab-builtins E. -- | ENRICO ARDIZZONI | Responsabile Ufficio Reti e Sistemi | Università degli Studi di Ferrara

2 3

Planned Atlas downtime on 29 January
by Robert Kisteleki 06 Feb '20

06 Feb '20

Dear RIPE Atlas users, Please be aware that we plan to do maintenance work in the RIPE Atlas core infrastructure two weeks from now, on Wednesday 29 January, between 9:00-12:00 CET (Amsterdam time). The RIPE Atlas website, UI and API will be unavailable in this period. The probes should remain connected and results will be collected normally, although during this period they can only be accessed real-time via the streaming service. Apologies for the inconvenience this may cause. Regards, Robert Kisteleki

2 3

Using Atlas for Monitoring of Anycast DNS
by Klaus Darilion 20 Jan '20

20 Jan '20

Hello! I want to restart this old thread and ask for available tools. For our Anycast DNS cloud, I want to measure the "performance", ie the RTT from Atlas probes. 1. Create measurements (I can do that already ;-) 2. Analyze this measurements: - fetch measurement - analyze the probe locations (ie. country, continent) - create reports with average RTT from certain countries and continents This second step I have partly in old scripts using influxdb and grafana dashboard - but that was a proof of concept with bad code. So, before starting coding from the base - are there some available scripts which can do the second part? Is https://github.com/RIPE-NCC/ripe.atlas.sagan still the way to go for measurement processing or are there meanwhile some better/smarter libraries? ie something for php? Thanks Klaus Am 20.11.2014 um 16:32 schrieb Klaus Darilion: > Hi! > > I want to monitor an Anycasted authoritative name server: > - are all nodes responding > - are all nodes in routing > ... > > > So I thought about starting a long term DNS measurement with plenty of > probes and NSID queried. Then, checking the results I should see every > possible NSID if there are for more probes than Anycast-nodes. > > Does anybody have done that (or similar) already and want to share code? > > Can the RIPE Atlas Status Checks be used for such monitoring? > > Thanks > Klaus >

4 4