PeeringDB URL Update (March 2022): 

Previous versions of PeeringDB allowed authenticated requests to https://peeringdb.com/api/. As of March 2022, PEERINGDB_URL must be set to https://www.peeringdb.com/api/ for authenticated requests to succeed.

Customers updated to v8.0.2 and later do not need to take any action and are not affected.

Local customers using versions 8.0.1 or earlier, and who are using Peering (or wish to start using Peering), should perform the following update(s) as applicable to their situation:

A) Existing local customers who already have their peeringdb account details saved in Provision should update PEERINGDB_URL in globals.php to:   

define('PEERINGDB_URL', 'https://www.peeringdb.com/api/');

Customers that do not already have their B) Customers who wish to begin using Peering (thus, do not already have saved peeringdb account details saved ) will not currently be able to add their account through the UI, because it via the GUI prior to v8.0.2. An attempt to do so will fail the "valid account test", which uses the a hardcoded string value.

Until a patch is availableInstead, affected users may directly save the account information using the save_account API callmust do both of the following:

B1) Save peeringdb account details using the API:

https://cloud.6connect.com[your instance]/APIv2/spec.php?family=peering#/default/save_account

B2) Update PEERINGDB_URL in globals.php to:

define('PEERINGDB_URL', 'https://www.peeringdb.com/api/');