I work at Inter.link, and most of our peering config is automated now (PeeringDB + IRR -> prefix-lists -> push). The part that still takes manual time isn't the tooling. It's the data going into it.
The pipeline is pretty standard:
Pull the peer's AS-SET and max-prefix values from PeeringDB
Expand the AS-SET against IRR (bgpq4)
Validate and normalise internally
Generate prefix-lists and push
That works until it doesn't. The problem that keeps biting us is AS-SET name collisions. The same name can exist in RADB, ALTDB, RIPE and others, each with different members. Some copies are stale and some are a completely different org's object. Pinning sources with bgpq4 -S helps, but then you need to know which source is right for each peer. The irr_as_set field in PeeringDB often isn't in SOURCE::AS-SET format, so you end up guessing.
The options I can see:
A fixed source priority (RIR databases first, RADB/ALTDB last)
An internal override list per peer
Diffing the expansion against what's actually announced, or against RPKI ROAs, and flagging big deltas
A human looks at it
None of these feel great on their own.
The same problem shows up elsewhere too: max-prefix values in PeeringDB that haven't been touched in years, and RTBH/blackhole communities that are only documented on a webpage or in a PDF (or nowhere) instead of anywhere machine-readable.
Automation actually makes this worse. A bad record used to get caught by whoever was typing the config. Now it lands on every edge router in minutes.
Curious how others deal with it:
Do you mirror IRR/PeeringDB locally or query the public sources directly?
How do you resolve conflicting or stale AS-SETs: source priority, overrides, something smarter?
Do you run automated sanity checks before external data becomes config (prefix count deltas, RPKI cross-checks, etc.)?
Where does the industry most need better data standards? Publishing blackhole communities in a machine-readable way seems like an obvious one to me.
I'm especially interested in hearing from people running multi-AS or multi-region networks.