Opinion. This is a perspective piece from the VolleyForge team, not a news report and not a product announcement. The reporting lives in our news hub: the DUPR outage and data incident — what we actually know. If you’re dealing with the outage directly, see our organizer’s playbook for running a season through it or our login and match-history guide. What follows is an argument about how the sport organizes its ratings, and we may be wrong about it.

What happened, briefly

In early September 2026, DUPR experienced a security incident and notified users by email. The email stated that DUPR does not store financial, payment, or password data on its systems. The app and website were down for roughly two to three days and were restored around September 8, 2026. The disclosure was email-only — there was no post on DUPR’s blog or website at the time of writing.

Players on r/Pickleball reported a rougher tail than that summary suggests: login and MFA loops after the restore, six-digit codes that didn’t arrive, and matches entered shortly before the outage that reportedly never rating-calculated. Those reports are not confirmed by DUPR, and we’re treating them as reports, not facts. Because the email did not say what data, if any, was accessed, players were left to infer that for themselves — and they did, loudly.

The uncomfortable part isn’t the incident. It’s the dependency.

Every service has bad days. Every service has outages, and any organization holding user data can be attacked. VolleyForge is software too; we are not standing outside this. DUPR restored service in days, and building and running the rating layer for an entire sport is genuinely hard work that most of the people complaining have never had to do.

So this isn’t a criticism of how DUPR is engineered. We have no visibility into DUPR’s systems, no information about what caused the incident, and no opinion on either. Nothing in this argument depends on those answers.

The part worth arguing about is structural, and it belongs to the sport, not to any one company: for a few days, a very large number of American pickleball players could not see their rating, could not log a match, and could not verify their own history — because there is effectively one place all of that lives. When ratings gate who you play, which bracket you enter, and whether a tournament will take your entry, a single provider becomes a single point of failure for everyone downstream of it. That is true of any provider in that position. It would be just as true if the provider were us.

Three properties worth arguing for

“Decentralize ratings” is a slogan, not a plan. Here is what we think the actual, concrete asks are — and each one is achievable independently of the others.

1. Portability: your match history should be yours, in a file

A rating is a derived number. The underlying asset is your match record — who you played, with whom, what the score was, on what date. If you can export that record in a plain machine-readable format whenever you want, then a provider outage is an inconvenience instead of an erasure, and switching or adding a system later is a data-import problem instead of starting over at zero.

Portability is the cheapest of the three to deliver and the one players can ask for right now, from any platform they use, including ours. It requires no new algorithm and no new organization. It just requires the export button to exist and to contain the whole record.

2. Transparency: you should be able to reproduce your own number

Most rating disputes are really trust disputes. A player who can follow the arithmetic from their own results to their own rating stops arguing about whether the system is rigged and starts arguing about their backhand. Transparency here means a published, versioned method — enough that a competent person with a spreadsheet and their own match list can arrive at approximately the same number, and enough that when the method changes, everyone can see that it changed and when.

We’ve written up what is publicly known about how DUPR calculates ratings and how the various rating systems compare. The broader landscape is in our explainer, how pickleball ratings actually work. Transparency is a spectrum, not a switch, and no system in this sport currently sits at the far end of it.

3. Redundancy: more than one copy of the truth

Redundancy is the least glamorous and most useful of the three. If a league’s results also exist in the league’s own system, and a player’s history also exists in a file they control, then a provider outage costs you a rating update, not a season. Redundancy doesn’t require a competitor to DUPR to exist. It requires that DUPR not be the only place a match was ever written down.

Organizers are the natural redundancy layer here, because they already have the results. Recording them somewhere durable is the single highest-leverage habit in this whole argument, and it costs nothing.

Why the open-source alternative is harder than the thread thinks

There’s an active conversation on r/Pickleball right now asking what an open-source or transparent DUPR alternative would need in order to earn players’ trust. We think that’s the right question and we’re glad it’s being asked in public. We also think the answers are harder than a weekend project, and the honest version of this argument has to say so.

  • Cold start.A rating system with a few hundred casual matches in it is not a rating system — it’s noise with decimal places. Reliable ratings need volume and a connected pool of players, and the incumbent has both.
  • Verification and gaming.The hard problem was never the math; it’s stopping people from feeding the math bad results. Any open system has to answer sandbagging, invented matches, and friendly-score inflation, and it has to answer them without a paid staff to adjudicate disputes.
  • Acceptance. A rating is only worth what tournaments accept. Until event directors take it at the registration desk, an alternative rating is a hobby number, however elegant its algorithm.
  • Who runs it in year three. This is the objection we find most persuasive, and it came up repeatedly in that thread: open-source is a licensing model, not an operations plan. Someone has to pay for servers, patch dependencies, answer support email, and still be there in three years. A project that dies quietly is worse for players than a commercial service that occasionally has a bad week, because at least the commercial service has someone whose job it is to bring it back.

None of that argues against the idea. It argues for taking the boring parts seriously first — governance, funding, and verification — before anyone writes the elegant algorithm.

Where VolleyForge actually stands

We want to be exact here, because this is the paragraph where content like this usually oversells.

  • VolleyForge is not a DUPR alternative and is not a rating authority. Today, player skill on VolleyForge is self-entered — you tell us your level, and we use it to help match you into reasonable games. It is a convenience field, not a computed rating, and we describe it that way everywhere.
  • We have not built a rating engine. Not shipped, not in beta, not behind a flag. If and when that changes, it will be announced as a product, with its method published — not implied in an opinion post.
  • We are not adversaries of DUPR.We applied for DUPR’s Partner API and were declined pending a public launch, and we intend to reapply. A pickleball world where a good rating system is widely trusted and integrates cleanly with the tools organizers use is a world we want.

What we do run is the layer underneath ratings: seasons, schedules, and score submission, with standings computed from the results organizers and players enter — across leagues, tournaments, and pickup games. That layer does not depend on any third-party rating service being online, which is a design property we care about and not a marketing claim about anyone else’s uptime.

What we’re exploring — and what we are not promising

Internally we have an open question on the shelf: whether a transparent, portable rating approach is something VolleyForge should build, contribute to, or stay out of entirely. We’ve looked at it seriously enough to know that our own data volume today would not support a trustworthy rating, which is exactly the cold-start problem above. So it sits unbuilt, on purpose.

We’re telling you that because the alternative — hinting at a coming rating system to catch a news cycle — is the thing we’d be annoyed at someone else for doing. There is no VolleyForge rating system, and this post is not a pre-announcement of one.

What you can do this week, regardless of who builds what

  • If you organize:keep your own durable record of every result — a system, a sheet, a notebook, anything that isn’t only inside one vendor. Your league’s history is your asset.
  • If you play: export your match history wherever you can, and keep the file. Ask any platform you use — again, ours included — whether you can get your full record out.
  • If you’re a tournament director:decide in advance what you’ll do when a rating lookup is unavailable on entry day, and publish that policy. The worst time to invent a fallback is the morning of.

None of that requires waiting for anyone to fix anything systemic. If you just want a game tonight, browse open games near you — in Kansas City, start with the Kansas City pickleball hub.

Join the argument

We’d rather be corrected than agreed with. If you think ratings should be centralized — that one trusted number is precisely the point, and fragmentation would make the sport worse — that’s a real position and we want to hear it. If you’ve tried to build an alternative and hit a wall, we especially want to hear that.

Tell us where this argument is wrong, or read the reporting first in our running account of the outage and the neutral background in how pickleball ratings actually work.

VolleyForge is not affiliated with, endorsed by, or connected to DUPR. Statements about DUPR in this post are limited to what DUPR communicated to its users and what the service’s public status showed; player reports are identified as such and are not confirmed. We make no claim about the cause of the September 2026 incident or about what data, if any, was accessed. This piece is opinion, current as of September 10, 2026. See also our DUPR rating guide.