2023 Release Notes
The release notes list the GitHub issues and a summary of what has changed in PeeringDB software releases.
Each new release has a one week beta test period on the beta server before it goes live. The beta and new releases are announced on the PeeringDB Announce Mailing List and on Facebook, LinkedIn and X.
Release 2.53.0
Beta Announcement Date: 29 November 2023
Release Date: 6 December 2023
| GitHub issue | Summary |
|---|---|
| #1362 Show connected networks, exchanges, and carriers on campus results pages | Adds an aggregated view of interconnection resources at a campus on the campus page. |
| #1247 Store language preference in the user's profile instead of cookies | Improved handling of website language preferences. |
| #1327 Improve visibility of contact data settings | Admins now see the visibility settings for their contacts alongside the set values. This makes it easier to identify and correct mistakes. |
| #1385 Keep the list of IRR up to date | As title. |
| #1432 Make dates ISO 8601 compliant everywhere in PeeringDB | As title. |
| #1252 Display dates consistently | As title. |
| #1433 Timestamps should be consistent | As title. |
Release 2.52.0
Beta Announcement Date: 25 October 2023
Release Date: 6 November 2023
| GitHub issue | Summary |
|---|---|
| #1328 Support web updates from a source of truth | Internal sources of truth, like configuration management systems, can now propose PeeringDB updates that a web user can review and either accept or deny. |
| #1374 Search to include new objects: Campus & Carrier | Support for new carrier and campus objects in v2 search, which is now the default with v1 search linked for the time being. |
| #1368 Facility data export into Google Earth KMZ | PeeringDB facility data is now exported into a Google Earth KMZ file that includes the details of the facility fields and their contents (ix, net, carrier). It is linked from the web footer and generated every day. |
| #1394 v2 search failing to find some names | Fixes a bug where names with hyphens in them were not handled properly by v2 search. |
| #1313 Improve email confirmation control - add 3 month option & maybe set new default value | Improve the design of the periodic reconfirmation control for user email addresses and add a new 3 month value. |
| #1257 Help text covers non-compliant email addresses | Non-compliant email addresses of affiliated users are now shown, making it easier to know who to contact. |
| #1164 better rdap error reporting | Improved error handling and friendlier error reporting to users. |
| #1260 Add Selenium Grid to CI testing | Improve automated browser testing for website. |
| #1380 Reset 'Social Media' to '{}' if field is null | Fixes a bug with broken page rendering for backend admin users when a social media field was set to null. |
Release 2.51.0
Beta Announcement Date: 13 September 2023
Release Date: 20 September 2023
| GitHub issue | Summary |
|---|---|
| #1364 IX Object Creation Per Policy | Automates approval of new ix objects per policy. |
| #1226 Add a "Delete Affiliation" button/option to the profile | Users can now remove an affiliation from their account. |
| #1431 add redis for caching | Improves cacheing performance. |
| #1382 Syntax checker for social media user names broken | Fixes a bug that rejected social media names that incorporated a hyphen. |
| #1401 Creating a new network not possible | Fixes a bug that stopped net creation when social media fields were sent with request. |
| #1419 replace missing Glyphicons | Use Google's "Sort by Alpha" icon in table headers. |
| #1182 Manual IX-F import request queue can get stuck | Fixes a bug that allowed users to enable IX-F imports without setting a URL. The importers also discards imports without a URL. |
| #1334 IX-F Importer: Cosmetic issue with "resolved" emails and double-slashes in URLs after the FQDN | Fixes a cosmetic issue with IX-F notification messages. |
Release 2.50.0
Beta Announcement Date: 16 August 2023
Release Date: 23 August 2023
| GitHub issue | Summary |
|---|---|
| #1352 Include carrier and campus objects in the API | carrier and campus objects were not included in the main API at first as we did not know if users would use them. They are now part of the API, making them usable by tools that rely on the API. |
| #1300 display website URL on all non-org objects | The website from org objects is now inherited by all child objects. |
| #1381 Add hover tip to describe meaning of routeserver icon | As title. |
| #1361 Add Campus and Carrier Tooltips | As title. |
| #1360 IX-F Importer: IX-F Member Data not being nullified after IX stops/changes import | Fixes a bug where the IX and participants were being mailed about import issues after the import was turned of by the IX operator. |
| #1239 Add a search field to all AC views | Better search for support tools. |
| #1027 Make the search field on cp/peeringdb_server/network/ aware of leading AS/ASN | Improved handling of variant syntax in support tools. |
| #1412 Improve performance by updating Python client code | Replace old python2 sync code with python3 code. |
Release 2.49.0
Beta Announcement Date: 12 July 2023
Release Date: 19 July 2023
| GitHub issue | Summary |
|---|---|
| #1344 Auto approval of new carrierfac objects | carrierfac objects are now approved automatically, like netfac objects. |
| #1299 Alphabetize simple search results | Exact match search now go at the top, with other results displayed alphabetically. |
| #997 Allow organizations to require affiliated users to enable 2FA | Organizations can now require their users to turn on MFA. |
| #1370 Facility Geocode not working | Fixed a bug that meant some facs did not have a geocode. |
| #1225 Evaluate ways to reduce operational costs | Operational work to support deployment directly on cloud provider infrastructure, instead of in a VM. |
| #1219 Optimize Cacheing | It is now easier to obtain and cache PeeringDB data. |
| #1404 Upgrade the django-oauth-toolkit library | Django update deferred from last month. Oauth application owners were given notice of this breaking change. |
Release 2.48.0
Beta Announcement Date: 21 June 2023
Release Date: 28 June 2023
| GitHub issue | Summary |
|---|---|
| #1311 Update Dependencies | Update all dependencies to new major releases. This year includes Django 4.2 LTS. |
Release 2.47.0
Beta Announcement Date: 17 May 2023
Release Date: 24 May 2023
| GitHub issue | Summary |
|---|---|
| #1204 Improve Search Functionality | Significant improvements to search via a new backend. |
| #1290 Add permission 'manage peering sessions' | Adds a permission for managing peering sessions, that is useful for portal enabling PeeringDB OAuth. |
| #1241 Don't allow the first and last addresses being assigned | Added a validation check to fail on network and broadcast addresses. |
| #1238 Put an Icon next to user name on https://www.peeringdb.com/org/nnnn#users if the user is using U2F | Added a U2F badge next to user name in organization user listing if the user has set up U2F 2FA |
| #1339 Tie TOTP devices and Webauthn Security Keys to the user account | Tie TOTP devices and Webauthn Security Keys to the user account so the AC can see this information. |
| #1291 Show all e-mail addresses associated with a username | All e-mail addresses associated with a user are now shown in the users tab. |
| #1372 Facility history still broken | Fixes an issue with fac history for AC use. |
Release 2.46.0
Beta Announcement Date: 12 April 2023
Release Date: 19 April 2023
| GitHub issue | Summary |
|---|---|
| #1336 Clearly show when a facility is part of a campus | Adds a small icon to show that a fac is a part of a campus. |
| #387 Replace "website" element in API/UI with social media tags | Introduces the ability to include links to social media accounts from PeeringDB pages. |
| #1333 Calling /api/carrier with parameters is broken | Fixes a bug in the API support for the new carrier object. |
| #1094 IX-F Importer: duplicate address(es) should result in rejection of JSON export and notification of IXP | Fixes a bug in handling duplicate IP addresses in IX-F imports. |
| #1249 Update MkDocs for docs.peeringdb.com | Updates the software used by https://docs.peeringdb.com |
Release 2.45.0
Beta Announcement Date: 15 March 2023
Release Date: 22 March 2023
| GitHub issue | Summary |
|---|---|
| #1295 Allow anonymous users to change languages | It is now possible to select a PeeringDB translation without logging in to the website. |
| #1281 better <title> tags | The HTML <title> tag of pages on www.peeringdb.com now shows key information from the page, like a network name or search term. |
| #749 Rename Private Peering Facilities to Interconnection Facilities in the UI | Private Peering Facilities have been renamed to Interconnection Facilities in the UI. |
| #1308 Deploy Google Analytics on www and docs | We have deployed Google Analytics to measure website traffic. |
| #1271 Implement auto-removal of stale networks according to DOTF recommendations | Stay networks are now automatically removed as per the DOTF recommendations. |
| #389 It should be impossible to save an active entity under an entity that is marked as deleted. | It is no longer possible to save an object under one that's marked as deleted. |
Release 2.44.0
Beta Announcement Date: 15 February 2023
Release Date: 22 February 2023
| GitHub issue | Summary |
|---|---|
| #1110 Add campus object | Initial deployment of a Campus object – a record to describe facilities where inter-facility cross connects are available as easily as intra-facility cross connects. |
| #1191 OAuth logins with 2FA don't complete first time | Fixes a bug that broke the OAuth flow when MFA was enabled. |
| #668 Add "self" as an object identifier, for documentation purposes | Adds a "self" object identifier to API and views for GET requests. Authenticated users going to https://www.peeringdb.com/{net |
Release 2.43.1
Release Date: 10 February 2023
| GitHub issue | Summary |
|---|---|
| #1315 issues when accepting / denying carrier presence requests | Fix permission issues when accepting or rejecting carrier facility presence requests and automatically approve them when they are from the same organization. |
Release 2.43.0
Beta Announcement Date: 18 January 2023
Release Date: 25 January 2023
| GitHub issue | Summary |
|---|---|
| #909 Add Carrier Record Type | Initial deployment of a Carrier record – a record to describe providers of high capacity links between facilities, running at layers 1 or 2. |
| #1140 API keys: disabling of user account by a PeeringDB admin does not disable access via a User API key. Also no disable mech, only revoke. | Fixes a bug where user API Keys were not disabled when their account was disabled. |
| #1220 API requests with invalid Authentication headers should notify users in some way | Requests with an invalid API key now return appropriate error codes. |
| #1130 Allow user to change account username | Users can now change their account name. |
| #970 Cache hints are needed for optimal CDN use | Adds cache hints to make CDN deployment more effective. |
| #1278 Commandline tool "Run command" button gone | Fixes a problem affecting Admins – a tool was hidden. |
| #1279 RIR status gets deleted when changes are made to the network | Improves the new process for validating networks against RIR data (see: #1280). |
| #658 Improve MTU field | MTUs now default to 1500 and there's a new dropdown list of options to select from. |
| #1282 Ops: Emails to OPERATIONS_EMAIL need to be rate-limited | Introduces a rate limit for automatic mail sent to Operations. |
| #1283 Footer "Global System Statistics" should be cached within django instance, not updated with every page load | Global System Statistics are now generated periodically instead of on each page load. |
| #1284 Ops: django needs lightweight healthcheck route that confirms database connectivity | Introduces a lightweight health check for database availability. |
| #1285 Ops: various indexes are needed | Introduces new database indexes. |
| #1288 Ops: Expose CSP_CONNECT_SRC to .env | Add configuration options for ease of operations. |
| #1296 CSRF cookie not set error from email confirmation view | Fix a bug with CSRF cookies not being set. |