[FCIX] Route Servers stuck in API purgatory

[Kenneth Finnegan]

Howdy Folks,

Just wanted to drop everyone a note that our route servers are
currently still running, but they're stuck with the current
configuration they're running, so they are not able to add recently
connected peers or update any of the static prefix filters used per
peer.

This failure is due to the changes PeeringDB recently made to their
API, which requires me to update ARouteServer so that I will be able
to install a PeeringDB API key since our route servers have hit the
free API rate limit.

Unfortunately, the route servers are running on an old version of
Ubuntu and I'm stuck in Python2 purgatory on them, so fixing this is
going to take more than 15 minutes, which is about all I have to
dedicate to this problem at the moment due to personal commitments
which are taking up most of my spare time.

As always, I will reiterate that the route servers are a best effort
convenience service provided by FCIX, and we always encourage networks
to set up direct peering sessions with peers of interest and not rely
on the route servers for learning critical prefixes.
--
Kenneth Finnegan
Technical Director, FCIX