About the author
Vesna Manojlovic is Community Builder at RIPE NCC.
Vesna joined the RIPE NCC as a Trainer in 1999. In 2003, she took responsibility for developing and delivering advanced courses, such as RPSL, Routing Registry, DNSSEC and IPv6. In 2008, she lead efforts to establish IPv6 RIPEness as a measure of IPv6 deployment among LIRs. In 2011, she joined the Science Division as Manager of the Measurements Community Building team; in 2015 she moved to Communications Department as Senior Community Builder, with a focus on organising hackathons.
Vesna gives presentations at many technical conferences and workshops, and enjoys visiting hackerspaces.
Vesna received a Batchelor of Sciences Degree in Computer Science and Informatics from the School of Electrical Engineering, University of Belgrade. She has three children.
I like the related article in Atlantic ("I Spent Two Years Trying to Fix the Gender Imbalance in My (STEM) Stories") from February 2018, and a quote: "Crucially, I tracked how I was doing in a simple spreadsheet. I can’t overstate the importance of that: It is a vaccine against self-delusion. It prevents me from wrongly believing that all is well." https://www.theatlantic.com/science/archive/2018/02/i-spent-two-years-trying-to-fix-the-gender-imbalance-in-my-stories/552404/
A follow-up article about the Reverse DNS statistics by RIR team: https://blog.apnic.net/2017/05/25/investigating-status-reverse-dns/
Thanks, Stephane! In addition to Stephane's tools being updated to enable this new measurement, Hugo Salgado "patched" the "official" CLI toolset, and since then the new version has been published by Chris Amin: https://github.com/RIPE-NCC/ripe-atlas-tools/ So now there are multiple ways to measure latency towards your web server using command-line tools!
“Hi Vesna, thanks for covering this! Does the Country Jedi have to be installed from GitHub to use? Or is there an online portal? I am not sure how to get it to work, but I want to share it with people (and encourage them to use it). I liked Mirjam's presentation at the CEE Peering Days, and I think it could be really useful. Feel free to ping me on another platform too.”
Hi Michael, thanks for your interest! Yes, IXP-Country-Jedi is available both as an installed version, and as an "online portal" - however, it is still a prototype! You can find the latest data per country here: http://sg-pub.ripe.net/emile/ixp-country-jedi/latest/ For example, Serbia: http://sg-pub.ripe.net/emile/ixp-country-jedi/latest/RS/ The additional "Per AS report" is only available for Greece, for now: http://sg-pub.ripe.net/petros/ixpcountryjedi/2017-04-01/GR/perasn/index.html And the code on GitHub is here: https://github.com/emileaben/ixp-country-jedi I hope you have fun using it, and thanks for pointing people to our tools! Cheers, Vesna
This is a pair of frequent questions: 1) I have too many credits - who can I give them to? 2) I need more credits - who wants to give me some? Usually, people post their offers & requests to either "firstname.lastname@example.org" mailing list, or on Twitter, with a hashtag #RIPEAtlas or mentioning the user @RIPE_Atlas So please check and use either one of those. Thanks! Vesna
“CAIDA wrote a blog post about the hackathon results: https://blog.caida.org/best_available_data/2016/11/11/the-remote-peering-jedi/”
... and two more mentions: Euro-IX Newsletter http://us7.campaign-archive2.com/?u=99dcdddc67f83b726fa293b31&id=4dcbc6b909&e=c4430325ce & #37 Weekly Internet Infrastructure Updates from Christian Koch: http://us12.campaign-archive1.com/?u=d732e9c6adbea385abc856c8d&id=950ca992ef
CAIDA wrote a blog post about the hackathon results: https://blog.caida.org/best_available_data/2016/11/11/the-remote-peering-jedi/
Geert Jan, thank you for helping us to grow RIPE Atlas in the "not so easy" parts of the world! As for your questions, we considered them, and I would like to separate two aspects: - We are indeed distribute probes (also thanks to ambassadors like you) to all parts of the world. However, probes are still predominantly deployed in the parts of the Internet that is already covered pretty well - maybe that's due to the nature of the ”network effect”. - This specific article was not looking into the numbers of probes that were lost, postponed, or for other reasons *never connected*. All probes in the analysis and the graphs above were connected at some point in their lifetime, and then either continued to live or "died”. We will continue to observe RIPE Atlas probe distribution, deployment and lifetime, and we will publish an update when there are any new developments.
Showing 38 comment(s)