Index of /datasets/peeringdb

      Name                    Last modified      Size  Description
Parent Directory - 2010/ 2010-12-01 21:00 - 2011/ 2011-12-01 21:00 - 2012/ 2012-12-01 21:00 - 2013/ 2013-12-01 21:00 - 2014/ 2014-12-01 21:00 - 2015/ 2015-12-01 21:00 - 2016/ 2020-02-21 16:03 - 2017/ 2017-12-01 21:00 - 2018/ 2018-12-01 21:00 - 2019/ 2019-12-01 21:00 - 2020/ 2020-12-01 22:00 - 2021/ 2021-04-01 22:00 - README.txt 2020-02-21 16:33 1.8K v1/ 2020-02-21 15:59 - v2/ 2021-04-20 16:01 -
This dataset is a repository of daily snapshots of historic PeeringDB data.
The repository consists of two parts, version 1 and version 2.

The old v1 format is available from July 29, 2010 through March 13,
2016 as sql and sqlite files. The new v2 format is available from May 27,
2016 to March 10, 2018 as sqlite files, and from March 11, 2016 onwards
as json files.

----------------------

peeringDB v2 sync stopped working Jan 22, 2017 due to a schema change
and the previous version of the peeringdb python module was not able
to handle it. 

The sync process was dying midway through the process, so all the
changes from the master copy would not be synced to our local copy.

Discovered Aug 8, 2017.

Updated python peeringdb module and django-peeringdb module, which
seems to have fixed it. However, files from Jan 22, 2017 to Aug 9,
2017 will not have an up-to-date database. 

Fixed Aug 15, 2017.

-------------------------

The sync process started breaking again Oct 10, 2017. This fixed
by upgrading python-peeringdb or django. The
python-peeringdb module hadn't seen much dev activity so it seemed
like this was not going to get fixed. 

The files from Oct 10, 2017 to March 11, 2018 are bascially not
updated, i.e., they are the same as october 9, 2017. 

On March 11, 2018, a new script was rolled out that downloads the whole
DB using the new RESTful API. The script downloads the API spec, and
then all the data from each endpoint. It creates a master json file
with the API spec and data for all the endpoints. 

Regular downloads using this method started March 11 ,2018. 
------------------------------------------------------------------
There is an August 28 - September 6 2019 gap when the data was not
updated due to the error resulting from the OS upgrade on the
machine collecting the data. 
------------------------------------------------------------------