{"id":30897,"date":"2025-09-11T16:54:55","date_gmt":"2025-09-11T16:54:55","guid":{"rendered":"https:\/\/blog.lacnic.net\/?p=30897"},"modified":"2025-09-11T16:54:56","modified_gmt":"2025-09-11T16:54:56","slug":"peeringdb-new-features-and-updates","status":"publish","type":"post","link":"https:\/\/blog.lacnic.net\/en\/peeringdb-new-features-and-updates\/","title":{"rendered":"PeeringDB new features and updates"},"content":{"rendered":"\n

This is PeeringDB\u2019s third half yearly update. These reports are an opportunity to step back and look at the broad sweep of change. You can find our previous half yearly reports here:<\/em> <\/em><\/a>one<\/em><\/a>,<\/em> <\/em><\/a>two<\/em><\/a>.<\/em><\/em><\/p>\n\n\n\n

PeeringDB\u2019s board approved a 50 percent increase in spending on development and operations work in 2025 from the 2024 level. All our committees have access to these development and operations resources. This means we can get more development work done each month and put more effort into operations improvements.<\/p>\n\n\n\n

<\/a>Last six months<\/em><\/em><\/h2>\n\n\n\n

<\/a>Comparison in Search<\/strong><\/h3>\n\n\n\n

Users can now compare networks at facilities. This new feature was initially released in July and we\u2019ve already had two great suggestions for improvements to it.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You can now compare networks on our site and export the results. In this example is a comparison between some networks in Per\u00fa.<\/em><\/p>\n\n\n\n

Based on the initial feedback we will add comparisons based on exchanges (IXPs) to augment the existing facility (data center) comparison. We\u2019ll also show the countries where facilities are based and make the columns sortable.<\/p>\n\n\n\n

<\/a>Web UI<\/strong><\/h3>\n\n\n\n

We have started deploying our new web UI to users. We are using a staged approach. We\u2019ve started by deploying to PeeringDB volunteers and we\u2019ll next start opting in 20 percent of users, who will be able to opt out of UI testing.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The new PeeringDB front page \u2013 before refinements are applied<\/em><\/p>\n\n\n\n

The goal of our web UI refinements is to make better use of the screen space we know that 80 percent of visitors have. We\u2019ll also be adjusting the design to render better on the phones used in 20 percent of visits.<\/p>\n\n\n\n

We have to do this as we\u2019ve been adding columns to let users show things like BFD support. In some cases this has led to some elements obscuring others. One example is long IPv6 addresses being obscured.<\/p>\n\n\n\n

We are working on refinements identified during the first stage of deployment. When those are deployed we\u2019ll start opting users into the new design, allowing them to opt out if they prefer the old design.<\/a><\/p>\n\n\n\n

MFA Mandate<\/strong><\/h3>\n\n\n\n

Anonymous use has not gone away and will remain.<\/p>\n\n\n\n

But if you want to authenticate, whether to get more queries or to make changes to data you control, you now have to have a second factor. That means:<\/p>\n\n\n\n