- ripe-atlas - mailman.ripe.net

Small downtime expected
by Robert Kisteleki 02 Mar '16

02 Mar '16

Dear All, Due to operational reasons we will have a short downtime of the main RIPE Atlas website at 11:00 (CET). We expect this to last less than 15 minutes. The system will continue to collect results in the meantime, so no data loss is expected. Regards, Robert Kisteleki

1 0

Ping option DF
by dave 29 Feb '16

29 Feb '16

Hi, It seems atlas sends out ping with fragmentation allowed. Why is there no option to enable DF? Thanks, Dave.

2 1

Thirteen new RIPE Atlas anchors have joined the community
by Michela Galante 18 Feb '16

18 Feb '16

Dear RIPE Atlas users, 13 new RIPE Atlas anchors have been activated during the last month and a half bringing the total number to 177. - id-jkt-as10208, hosted by PT. Millenium Internetindo in Jakarta, Indonesia and sponsored by APNIC. - ar-bue-as4270, hosted by ARIU in Buenos Aires, Argentina and sponsored by LACNIC. - de-nue-as60574, hosted by net-manager UG in Nuremberg, Germany. - uk-boh-as196745, hosted by Datacenta Hosting in Bournemouth, United Kingdom. - at-vie-as30971, hosted by nic.at in Vienna, Austria. - uk-lon-as6908, hosted by Six Degrees Group in London, United Kingdom. - nl-utc-as1103, second anchor hosted by SURFnet, in Utrecht, Netherlands. - Two anchors hosted by INX-ZA/Internet Service Providers' Association of South Africa: za-jnb-as37474 in Johannesburg and za-umr-as37668 in Umhlanga, South Africa. - ru-led-as43317, hosted by Fishnet Communications in Saint Petersburg, Russia. - nl-dro-as12414, hosted by Solcon Internetdiensten N.V. in Dronten, Netherlands - de-drs-as42699, hosted by managedhosting.de GmbH in Dresden, Germany. - fo-hyv-as15389, hosted by P/F Telefonverkid in Hoyvik, Faroe Islands. The map of all anchor locations is available at: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are the logos and links to hosting companies: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from organisations interested in hosting a RIPE Atlas anchor. We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa, in order to add more geographical diversity to the measurement data. There are more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ For any other questions, please contact us at atlas(a)ripe.net Regards, Michela Galante Measurements Community Building RIPE NCC

1 0

Detecting additional information from the probes
by Christoph Rauterberg 15 Feb '16

15 Feb '16

Ahoi everyone, I am currently trying to asses the behaviour of DNS queries between clients and authentication servers - and I would love to trace some DNS pakets between the probes and my server. I was wondering, if there is some way to get the information about the Authentication Bit of DNSSEC specified in the DNS query headers. A.f.a.i.k., the probes do something similiar/do a /dig/ lookup. /dig/ does provide information about the DNSSEC-section - and furthermore it has a very handy /+trace/ option. Can anyone maybe tell me, if there are possibilities to access the AUTH bith or even something like a trace function via the probes? Or should I open a feature request for that? Help much appreciated! :-) Best regards, Chris

2 3

can help me increase speed
by mostafa shahdadi 13 Feb '16

13 Feb '16

% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to '2.189.88.0 - 2.189.95.255' % Abuse contact for '2.189.88.0 - 2.189.95.255' is 'R.javidi(a)tci.ir' inetnum: 2.189.88.0 - 2.189.95.255 netname: DABCO descr: Dadeh Pardazan Avaye Bandar Company country: IR admin-c: PA8248-RIPE tech-c: PA8248-RIPE status: ASSIGNED PA mnt-by: AS12880-MNT created: 2015-05-25T06:22:46Z last-modified: 2015-05-25T06:31:59Z source: RIPE # Filtered person: POURIYA ARGHASH address: No 2,first Floor,Daryanavard Building,Delgosha Conjunction, address: Emam Khomeyni Street,Bandar Abbas,Hormozgan,Iran phone: +98 761 222 54 90 fax-no: +98 761 222 54 90 nic-hdl: PA8248-RIPE mnt-by: AS12880-MNT created: 2015-05-25T06:31:59Z last-modified: 2015-05-25T06:31:59Z source: RIPE # Filtered % Information related to '2.189.0.0/16AS12880' route: 2.189.0.0/16 descr: Information Technology Company (ITC) origin: AS12880 mnt-by: AS12880-MNT mnt-routes: mohsenrahimimaintainer created: 2011-07-13T14:32:16Z last-modified: 2015-03-04T10:05:36Z source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.85.1 (DB-1) Sent from my iPad

2 1

Triggering traces from probes in specific cities
by Anurag Bhatia 10 Feb '16

10 Feb '16

Hello everyone, I was looking at possible command line tool to trigger traces from Atlas from given city or that area. The closest I can see is RIPE Atlas Tools - https://github.com/RIPE-NCC/ripe-atlas-tools but these let to only put source country or region. 1. Is anyone aware of how one can trigger traces via CLI from specific cities? *(I would love to do trace from a nearby city if specific city does not have Atlas coverage)* 2. In the Ripe Atlas Tools I see in documentation it refers to an argument "[--paris paris]". Is anyone aware of what does it mean? It seems to be asking for an integer value. Thanks in advance! -- Anurag Bhatia anuragbhatia.com

2 2

Feature request - externalize packet loss in ping measurement UI
by Gil Bahat 10 Feb '16

10 Feb '16

Hi, looking at the JSON data, there is a field for the amount of received packets vs the requested, but at the measurement UI it is not reflected. it'd be great if this can be displayed (e.g. 'x% packet loss' as one of the columns). Regards, Gil Bahat, Director of Online Operations, Magisto Ltd.

2 1

List of my measurements via API
by Luke Overend 09 Feb '16

09 Feb '16

Hi all, I have searched the docs and tried everything I can think of but I cannot get a list of my measurements via the API. Can anyone provide me details on how to do this? If it is not currently possible how do I go about requesting the feature? Thanks Luke Overend -------------------------------------- CloudFlare - AS13335 Network Engineer luke(a)cloudflare.com +442038136383 +447795328022 http://www.peeringdb.com/view.php?asn=13335

2 1

Revamped RIPE Atlas website launched today
by Robert Kisteleki 04 Feb '16

04 Feb '16

Dear all, We’re excited to announce that a revamped RIPE Atlas website launches today, so you can expect to see some changes when you visit atlas.ripe.net. We know that it can take some time to get used to change, but we think the new site is a big improvement over the old one and that you’ll find it quicker and easier to access the information you want. Some of the main features include proper landing pages for each section with quick links to the most relevant information, a restructured menu that includes a few new sections, including “Measurements, Maps and Tools”, “Probes and Anchors” and “Resources”, an improved dashboard overview of all of your probes and measurements under “My Atlas”, and faster data tables that you can now search. You can learn more about the revamped site and the reasons behind the change in this RIPE Labs article: https://labs.ripe.net/Members/suzanne_taylor_muzzin/the-revamped-ripe-atlas… Take some to look around and let us know what you think. We hope you’ll like what you see. Of course, we’ve done our best to ensure that all links are working properly, but if you happen to spot anything that looks wrong or broken, please let us know at atlas(a)ripe.net. Regards, Robert

1 0

API (v1) querying probes by ID
by Wenqin SHAO 03 Feb '16

03 Feb '16

Dear list, I have the impression that querying probes by ID returns unexpected results. An example is: https://atlas.ripe.net/api/v1/probe/?id=1 <https://atlas.ripe.net/api/v1/probe/?id=1> As a result, I get the entire probe list: "meta": { "total_count": 16973, "use_iso_time": false, "next": "/api/v1/probe/?id=1&limit=100&offset=100", "limit": 100, "offset": 0, "previous": null }, And ID 1 is an valid ID, which corresponds to the first entry of results: "id": 1, "type": "Probe", "is_public": false, "first_connected": "2010-10-29T15:53:03Z", "last_connected": "2016-02-03T10:02:28.407276Z", "is_anchor": false, "address_v4": null, "address_v6": null, "asn_v4": 3265, "asn_v6": 3265, "country_code": "NL", "prefix_v4": "212.238.0.0/16", "prefix_v6": "2001:980::/29", Regards, wenqin

3 4