Updated: Mon Apr 1 18:55 UTC 2026
PeeringDB Voter's Guide for Board of Directors Election April 15th through 29th 2026 UTC
Bylaws at https://docs.peeringdb.com/gov/legaldocs/2026-01-14_PeeringDB_Bylaws.pdf define Membership:
"A corporation, limited liability company, partnership or other legal business entity may be a Member of the Corporation. Membership is determined by having both an active PeeringDB.com account and an individual representative or role subscription to the PeeringDB Governance mailing list: http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov"
Each Member may submit one ballot. We are employing Single Transferable Vote (STV) as the voting system. This means that you rank your candidate preferences from most preferred to least preferred. You do not need to rank all the candidates. A later ballot from a representative of a Member will replace a previous ballot from the same Member.
There are 5 seats on the Board of Directors, 2 of which are up for election this year. A Director term is 2 years.
The following schedule applies to Board elections:
Through April 14th 23:59:59 UTC 2026: Candidates may submit their candidacy and a maximum 300 word statement, as determined by the POSIX "LANG=en_US.UTF-8 wc -w" command, or revisions to their statement, to secretary@peeringdb.com.
April 15th 2026: A voter registration form will be sent to the PeeringDB Governance mailing list (pdb-gov@lists.peeringdb.com).
April 15th through 29th 23:59 UTC 2026: Voting. (Registrations received after April 28th UTC are not guaranteed to be processed in time for the April 29th 23:59 UTC voting deadline.)
List of Candidates:
Candidate Statements:
Brian Burke
Hey All, I am Brian Burke. I currently manage peering & interconnection strategy at AWS, but I've been in this industry for 15+ years across a few different networks.
PeeringDB is one of those things that the internet often takes for granted, but people who work in the network community think about it and use it constantly. When records are accurate and well-maintained, it makes everything easier. When it's not, you feel it. What I like about PeeringDB is that it's still fundamentally a community project. Nobody's monetizing your data or turning it into a product. It works because operators choose to participate and maintain it, and the board has kept that spirit intact. I think one of the most underappreciated things about it is that it gives every network with a publicly routable ASN, regardless of size, a place to show up, represent themselves, and be findable. A regional ISP and a hyperscaler get the same blank canvas.
I want to get involved because I care about how the ecosystem evolves. I've been close enough to the problem for long enough that I think I can be useful in future development. Thanks for your consideration!