Redesigning the RIPE Atlas Measurement Detail Page
• 7 min read
We're switching to a new back-end solution for storing RIPE Atlas measurement metadata. Here's a detailed look at how those back-end changes have impacted front-end design.
Articles
Likes on articles
• 6 min read
You may have noticed that, as of this past week, RIPE Atlas is looking different. To explain what's changed and why, here's a quick update on our latest efforts in rolling out the new design we've been working on for our services.
• 8 min read
The ISOC African regional bureau has been organising hackathons at the last three editions of the Africa Internet Summit. This year we were given the opportunity to lead a track there at: "Measuring DNS and DoH". This is a report on the event and it's valuable and contributory outcome.
• 2 min read
How can you quickly figure out if a network you are using is dropping invalid Resource Public Key Infrastructure (RPKI) BGP announcements? You can do so by opening up a browser and visiting our RPKI test web page.
• 3 min read
Based on RIPE Atlas measurements, we can illustrate if paths between different networks in a given country stay in that country. We can also provide sketches of interconnections between networks in that country. In this article we look at the situation in Bosnia and Herzegovina.
• 6 min read
This post describes the result of an internship of a month of integrating an experimental data analysis method into RIPE Atlas.
Showing 5 article(s)
hi John, The code is release and it lives here: https://github.com/density215/rpki-web-test (sorry for the late reply)
“Unfortunately the test fails for me with the following message: "testing valid ROA...[error (what does that mean?)]![passed]" https://img.pbb.lc/id/N4A1VRYFq6muEsbs”
Hi Milan, what happens is that the test receives an error instead of a timeout for the request over the invalid path. The test doesn't exactly know what to do with that, hence the error message you're seeing. The CORS warning is not relevant here, that just tells us that the error response doesn't have the right headers (very common). I've seen instances where the invalid path is not dropped (so no response, so the test goes to timeout) but actually rejected with an error response. This may be the case with the response you're seeing (I am not sure, maybe if you expand the `events` object in the console and then expand the `invalidAwait` event in there, you would see a more elaborate error message). The trouble is that I've no clue what thing generates this rejection (middlebox? firewall?). As a consequence the test is not sure what to do with it.
“How I can correct location of ip address? For example 79.132.98.138 have wrong location 'Samara, Russia'. This is 'Ulyanovsk, Russia'.”
hi Konstatin, You can click the location in the 'IP LOCATION' window and then you'll get a new window where you can edit the location. There's a bug in the autocomplete, so the input will only autocomplete if you fill out the country afresh (so wipe the country and then select Russian Federation again). Then autocomplete for city will also work. I've already set 79.132.98.138 to Ulyanovsk for you ;-)
Showing 3 comment(s)