Skip to main content

Caching

Pathvector relies on external datasources to generate configuration, such as PeeringDB, IRR databases, and the RPKI. There are various mechanisms to cache this data to decrease latency and reduce load on these external services.

RPKI​

Networks should already be running their own RTR (RPKI to Router) server such as stayrtr or rtrtr.

IRR​

PeeringDB​

Pathvector has an internal PeeringDB cache that stores PeeringDB objects for the duration of a single pathvector generate run. This does not cache for longer than a single command invocation.

PeeringDB Local Cache​

To cache PeeringDB data persistently, you can set the global peeringdb-url option to a local PeeringDB cache server.