Based in Amsterdam, NL
Likes on articles
About the author
Based in Amsterdam, NL
I'm a system architect/research coordinator at the RIPE NCC, where I work in the science group. I'm a chemist by training, but have been working since 1998 on Internet related things, as a sysadmin, security consultant, web developer and researcher. I am interested in technology changes (like IPv6 deployment), Internet measurement, data analysis, data visualisation, sustainability and security. I'd like to bring research and operations closer together, ie. do research that is operationally relevant. When I'm not working I like to make music (electric guitar, bass and drums), do sports (swimming, (inline) skating, bouldering, soccer), and try to be a good parent.
Links & Social
While at this point it is still unclear what exactly happened at Facebook this morning (27 January), we collect data on the Internet control plane (BGP) and data plane that allows us to provide some insight into what happened with Facebook's connectivity to the rest of the Internet.
As the RIPE Atlas network continues to grow, it's useful for ambassadors and potential probes hosts to easily see where we already have probes deployed and where we'd like more probes installed. We created a few useful maps to help with this.
Under ARIN's Number Resource Policy Manual (NRPM) Section 4.10, the IPv4 address block 23.128/10 is reserved for allocations and assignments dedicated to facilitate IPv6 deployment. The maximum allocation size is a /24; the minimum allocation size is a /28. There has been much discussion on the NAN…
The World Cup is one of the most watched events on the planet, and we've been looking at traffic changes at Internet Exchange Points during the matches in Brazil at World Cup 2014. The final part of our analysis is now available, with a look at what happened during the final four matches of the tou…
Engineers from the Wikimedia Foundation and the RIPE NCC recently collaborated on a project to measure the latency of Wikimedia sites for users worldwide. Together, we identified ways to decrease latency and improve performance for users around the world.
In RIPE Atlas we see latencies to Google's 184.108.40.206 DNS resolver service drop in Turkey. We expect this is due to hijacking of the 220.127.116.11 service. Our measurements show a timeline of these events. Note that even when the Twitter ban had been lifted, RIPE Atlas still saw fake 18.104.22.168 DNS service…