Thank you, Richard, for already updating the values in the PeeringDB record!
😉
https://www.peeringdb.com/net/11380
For those interested in outsourcing keeping track of this to a computer rather than a meatbag, extracting the values via the PeeringDB API is straightforward:
curl -sH \
"Authorization: Api-Key $YOUR_PDB_API_KEY" \
"https://www.peeringdb.com/api
/net?asn__in=53679" \
| jq -r '.data[] | "\(.asn) \(.info_prefixes4) \(.info_prefixes6)"'
Which outputs:
53679 250000 150000
You can modify the value of
?asn__in for multiple ASNs in one call, e.g., for MICE and SeattleIX respectively:
?asn__in=53679,33108
will return:
33108 250000 100000
53679 250000 150000
Hmm. Looks like SIX needs to update the IPv6 value in PDB! <g>
Finally, I have a couple of simple python scripts for working with the PDB API. If anybody would like these, help with creating a PDB API key, or really anything PDB-operationally, ping me off-list and I'll
be happy to help.
AK
AS16970
(wearing the "your friendly local PDB admin committee member" hat)
From:
Richard Laager <rlaager@micemn.net>
Date: Thursday, March 5, 2026 at 2:53 AM
To: "mice-announce@lists.micemn.net" <mice-announce@lists.micemn.net>, MICE Discuss <mice-discuss@lists.micemn.net>
Subject: MICE Route Server Max Prefix
We, like SeattleIX, recommend that everyone increase their MICE route server max prefix settings:
IPv4: 250,000 prefixes
IPv6: 150,000 prefixes
--
Richard Laager
Chief Manager, Director
Midwest Internet Cooperative Exchange LLC