Dear colleagues, Over the last few days, some RIPEstat users have reported an issue with the launchpad page of the 2020 UI. The issue only affected the users of this UI. The misconfiguration was caused by an infrastructure change for which the rollout started on 12 February 2025 and was fixed on the evening of 18 February 2025. We are still investigating the situation and want to give you this preliminary update. The misconfiguration led to requests being performed in a loop, with “localhost” used as a placeholder value. This caused the user interface (UI) to misbehave. The RIPEstat 2020 UI uses a caching mechanism to store the information on the launchpad page. This means the failure was not immediately visible to users with cached data. The issue has been resolved for users that have no stored data. Meanwhile, we are investigating if there is an impact on users due to caching. As we announced earlier [0], we have been working on a single, consolidated user interface for RIPEstat. We expect to release this in the next few weeks and plan to deprecate the RIPEstat 2020 UI, and sunset it later this year. If you are still experiencing issues, we encourage you to try to clear the cache for the website, and contact us if the issues persist [1]. Kind regards, Ties de Kock RIPE NCC [0]: https://labs.ripe.net/author/adonis_stergiopoulos/streamlining-ripestat-buil... [1]: https://www.ripe.net/about-us/support/contact/contact-us/ On Wed, 19 Feb 2025 at 12:45, Raymond Jetten via ripe-list < ripe-list@ripe.net> wrote:
Hi Max,
Yes and i have opened a ticket on it, exactly the same symptoms.
Rgds,
Ray
For Internal Use Only -----Original Message----- From: Max Grobecker <max.grobecker@ml.grobecker.info> Sent: tiistai 18. helmikuuta 2025 20.52 To: ripe-list@ripe.net Subject: [ripe-list] stat.ripe.net broken?
Hello,
since at least today https://stat.ripe.net/app/launchpad seems broken. It shows my IP as being 127.0.0.1 and does an impressive amount of repetitive XHR queries to https://stat-ui.stat.ripe.net/data/network-info/data.json at a rate of over 10 req/s.
This only happens if I never logged into my RIPE account in that browser (or using a private tab). Even if not logged in but in possession of an expired session cookie, the site works perfectly fine.
Is anyone else experiencing this?
Greetings from Wuppertal Max ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-list.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/ ----- To unsubscribe from this mailing list or change your subscription options, please visit: https://mailman.ripe.net/mailman3/lists/ripe-list.ripe.net/ As we have migrated to Mailman 3, you will need to create an account with the email matching your subscription before you can change your settings. More details at: https://www.ripe.net/membership/mail/mailman-3-migration/