Summary

  • PeeringDB's current Bylaws give a qualifying legal entity membership through an active account plus a governance-list subscription. Each unaffiliated member has one vote; entities under common control share one vote. The public 2026 record shows 137 voters, but not the eligible electorate or affiliate groupings.
  • Members elect the Board, while the Board holds broad corporate, financial and final-appeal authority. Daily record approval, data disputes and product choices are delegated to committees, organization administrators and a small volunteer core.
  • The arrangement is a defensible private-association mandate, not authority over ASNs or address space. Its accountability gap is narrower and testable: PeeringDB publishes rules and votes cast, but not enough aggregate data to reproduce the electorate or measure how delegated decisions are reviewed.

Two credentials create membership

PeeringDB is a Washington nonprofit corporation, organized in 2015 and reporting itself as tax-exempt under section 501(c)(6). Its Bylaws do not make an ASN, an IP allocation, a sponsorship payment or a data contribution the legal ticket to membership. A corporation, limited liability company, partnership or other legal business entity may become a member when it has both an active PeeringDB.com account and an individual representative or role subscription to the governance mailing list.

The distinction matters because PeeringDB's voter HOWTO uses a simpler phrase: an organization should have data in PeeringDB and join the governance list. That is sensible operational guidance for a database community. It is not the text that defines the corporate franchise. The Bylaws do. Adding one valid record must therefore not be described as automatically creating a vote.

The formal franchise is otherwise broad. PeeringDB has one class of members. Subject to the affiliate rule, each member entitled to vote has one vote on each issue. Members representing at least a quarter of eligible members can call a special meeting; ten per cent establishes a meeting quorum. Dues, if PeeringDB introduces them, require majority member approval. Amendments to the article that gives the Board financial and operational power, and to the amendment article itself, require a two-thirds member vote.

These are not decorative rights. They authorize directors and protect several constitutional choices from ordinary Board amendment. But access to a ballot does not reveal the electorate by itself.

One member, one vote—after affiliation is resolved

The affiliate clause compresses corporate groups. Entities that directly or indirectly control one another, are controlled by the same person, or are under common control receive one vote in total. The principle blocks a conglomerate from multiplying votes simply by creating or enrolling subsidiaries. It also creates a classification task: somebody must decide where control begins and which accounts belong in the same voting group.

The public 2026 election report records 137 voters and three abstentions. It does not state how many members were eligible, how many ballot credentials were issued, how many affiliation groups were formed, or how disputed groupings were resolved. A governance-list subscriber count would not fill the gap. Lists may include individuals and duplicate representatives, while affiliated legal entities share a corporate vote.

PeeringDB's draft Board minutes of 8 June 2026 acknowledge low participation relative to membership and difficulties experienced by some voters. They also identify duplicate organizations as a complication. The Board discussed a voting banner, wider outreach and a simpler process. It recorded no decision.

This is an accountability limit, not evidence of ballot manipulation. An outsider can verify votes cast and the published counting rounds. The outsider cannot calculate turnout or reproduce the affiliate-adjusted denominator from the captured record.

The ballot and the Board

The Bylaws permit between three and seven directors. PeeringDB currently lists five: Livio Morina, Brian Burke, Isabel Odida, Marco Marzetti and Alexandre Corso. Directors normally serve two-year terms. A limit added in 2024 prevents a person from being elected more than five times over eleven consecutive elections, excluding the initial 2015 election. The April 2026 member meeting was the first election affected by that limit; Aaron Hughes and Job Snijders had termed out.

The 2026 ballot used Single Transferable Vote for two seats. Ten candidates appeared in the first round. The quota was 45. Brian Burke reached it in round seven; Marco Marzetti was recorded elected in round nine. The final report shows 50 exhausted votes after redistribution and 137 total voters.

One legal-text question remains open. Section 3.3 says directors may be persons elected by a majority vote of all members entitled to vote. Section 3.4.2 permits an April election “in such manner as the Board of Directors shall determine.” The published election used an STV quota of 45 rather than a simple majority of 137 voters, much less an unpublished eligible electorate. The captured materials do not explain how PeeringDB reconciles the clauses.

That ambiguity does not prove the election invalid. The Board may rely on its authority to determine the manner, another resolution may supply the interpretation, and legal terms do not always map mechanically onto a multi-seat tally. A published procedure or legal explanation would settle the question more credibly than an accusation.

Once elected, the Board's authority is broad. It manages the corporation, may incur and pay obligations without a member vote, and may adopt rules for use of PeeringDB's services and facilities. It can terminate a membership and service connections by a two-thirds vote under the stated minor- and major-infraction procedures. Most Bylaws provisions can be amended by a majority of directors in office. The Board is also the final appeal body in the published Admin and Product Committee structures.

The members grant corporate authority. They do not vote on every record, support ticket or release.

The record is governed in the queue

PeeringDB describes itself as a registry of information. Organizations and their administrators create and maintain network, exchange and facility records and can delegate granular permissions. That is the distributed side of the system: the people closest to a network are expected to keep its data current.

The central side appears when a record is new, disputed, inconsistent or abandoned. The Admin Committee's approval guidelines use checks such as WHOIS or RDAP email-domain matching. Some facility applications may require attestations from three existing users. An RPKI challenge is described as work in progress, not a universal control. Empty facilities can be removed after 90 days when the published conditions are met.

The Data Ownership Policy gives Admin substantial corrective power. Data may be altered, deleted, hidden, overridden or flagged for quality reasons. Network–exchange and facility disputes can be mediated by Admin. A minimal-disruption principle protects already published, conflicting data from abrupt removal unless the relevant party, automation rule or mediated resolution supports the change.

The Committee charter supplies the decision chain. Members are selected by the Chair and Vice Chair after a trial, reviewed quarterly and removed after three months of unexplained inactivity. Contested matters go to a simple majority, with the Chair casting a double vote to break a tie. A dispute can pass from Chair to Vice Chair and then to the Board, whose decision is final. The text seeks unanimity but also gives the Chair the final decision on any matter.

Those are delegated powers, not proof of arbitrary decisions. Their practical weight comes from workload. The April 2026 member minutes say approximately four core volunteers handle 1,100–1,300 new Admin tickets a month. The same record says volunteer applications were paused during 2025. Queue access, experience and continued availability therefore affect how quickly formal rights become usable decisions.

The charter names 20C as the main service contractor with which Admin may communicate directly. That is the only reason this article links the existing 20C, LLC directory entry. The link does not show that 20C owns PeeringDB, controls its Board or decides every ticket.

Product control follows another delegation

The Product Committee operates under a Board-approved charter. Volunteers apply to the Board; committee members serve renewable two-year terms; the committee elects its officers; and the Board may add or remove a member at any time. Proposals receive a shepherd and stakeholder review. The process seeks consensus, allows a five-day negative-vote period, and, if consensus fails, uses a vote with at least 50% quorum and no more than 25% opposition. The Board is the final destination for a dispute.

This process is more continuous than an annual director election. The 2026 member meeting reports ten main releases and six point releases from May 2025 through March 2026, 102 tickets closed and more than 30 confirmed bugs resolved. Mandatory MFA was among the changes. Those are PeeringDB's own activity counts, not independent proof that the right work was prioritized.

Operations adds a further execution layer. The same meeting minutes acknowledge lower availability than prior years, monitoring gaps, some contracted work, a transition to containers and the need to recruit volunteers. A Board can authorize; a committee can prioritize; a contractor or volunteer still has to keep the service running.

Who pays, and who gains

PeeringDB reported no employees and 42 volunteers on its 2025 Form 990. Its formal 2025 accounts record USD 317,545.21 in contributions and USD 262,476.66 in expenditure. Software development and maintenance cost USD 116,043.36, the Product Manager USD 58,500, and online services USD 40,837.52. Year-end assets were USD 518,458.01 with no listed liabilities.

The member-meeting minutes rounded Product Management differently, to about USD 54,000. The financial statement is the precise source; the discrepancy should not be silently harmonized.

Sponsors supply the revenue that supports the common service. Draft June minutes say some sponsors were asking PeeringDB to accept terms and conditions that it had historically declined to sign. The Board discussed the issue and reached no recorded decision. Nothing in the captured evidence shows a sponsor changing a ballot, record or roadmap. Funding exposure is real; capture is unproved.

Volunteers pay in time and continuity. Organization administrators pay in record maintenance. Networks, exchanges, facilities and downstream tools bear the cost of stale, disputed or unavailable data. The beneficiaries are similarly distributed: operators receive a shared directory and API; active legal entities receive a corporate vote; directors receive corporate authority; committee participants influence recurring decisions; applications avoid rebuilding every bilateral record.

Lock-in without a legal monopoly

PeeringDB cannot allocate or revoke an ASN or IP prefix. RIR registration, RPKI, WHOIS or RDAP and PeeringDB records serve different functions. A PeeringDB entry may help an interconnection team find and evaluate a counterpart; it does not transfer number-resource authority.

Its power comes from adoption. Historical records, user permissions, API and OAuth integrations, dependency relationships, Admin knowledge and routine use make a common dataset expensive to reproduce. The Data Ownership Policy itself recognizes that deleting one record can disrupt dependent records. Exit remains legally possible, but a credible substitute has to rebuild provenance, permissions, dispute history and integrations, not merely copy a table.

That is institutional lock-in: the service becomes a coordination point because many independent users have arranged work around it. The appropriate accountability standard is therefore tied to the control PeeringDB actually exercises—membership, Board authority, record administration, product decisions and service continuity—not to a public mandate it has never claimed.

Sources