
February 21, 2026
In 2015, we won an Independent Review Process against ICANN. The IRP panel ruled that the ICANN Board had violated its own bylaws by failing to conduct due diligence on a GAC objection. It was the first ruling of its kind—a precedent that .amazon and others would later rely on.
But winning the IRP was not the end. It was the beginning of a different kind of war.
The discovery that followed revealed what the panel never reached: staff misconduct, panel corruption, and a CEO quietly rewriting endorsements. The evidence existed. It was documented. It was real.
Then the courtroom door closed.
What Judicial Estoppel Did
Judicial Estoppel is an equitable doctrine. It prevents a party from taking inconsistent positions in different legal proceedings. It is meant to protect the integrity of the courts.
In our case, it was used differently.
During the IRP, our lawyers had truthfully argued that DCA had no other forum to be heard. That was true. That is why we filed the IRP.
When we later went to court to seek damages for the harm ICANN caused—harm the IRP could not remedy—ICANN turned around and said:
“You cannot be here. You told the IRP you had no other forum. Now you are in a court. That is inconsistent. Judicial Estoppel applies.”
The first judge disagreed with ICANN. He did not believe Judicial Estoppel should apply to the fraud claims DCA had filed. He signaled a willingness to let the case move forward—to let the evidence be tested before a jury.
Then, suddenly, he retired.
A new judge was assigned. That judge agreed with ICANN. The door that had seemed open was now closed.
The timing was suspicious. DCA and its supporters noted it. But suspicion is not proof. What is proof is what happened next: the new judge applied Judicial Estoppel, and the case was stopped.
Not because our facts were wrong. Not because the evidence of misconduct was weak. Not because the fraud claims lacked merit.
We were blocked because we told the truth about the system’s limitations—and that truth became the cage.
What the IRP Could Not Reach
The IRP has a narrow scope. It exists for Board decisions. It does not exist for:
- Staff conduct
- Contracted panels
- CEO actions
- Fraud claims
- Damages
Those categories of harm have no remedy within ICANN’s accountability structure. There is no policy for them. There is no second forum. The system simply does not go there.
We had evidence of all three. Discovery put it on the record. The IRP victory was won. But the evidence never saw a courtroom.
The Question No One Could Answer
When the door closed, we asked:
If not here, where?
If not now, when?
There was no answer. Because the system had none.
ICANN’s defense was not: “Prove the misconduct didn’t happen.” It was: “You already used your one bullet. You cannot have another.”
Never mind that the IRP cannot hear fraud claims. Never mind that the IRP cannot award damages. Never mind that the very policy for a second IRP on staff misconduct does not exist. It was never written.
So there was no path. Not because the facts were against us. But because the system is designed so that once you play by its rules, you cannot appeal when the rules themselves fail you.
What Survived
The courts were blocked. The jury never sat. The evidence never heard.
But the record survived.
The IRP ruling is public. The court filings are public. The discovery exists. The documents are citable. The timeline is fixed.
And the story—fifteen years of it—is now part of the Internet governance archive, whether ICANN acknowledges it or not.
Estoppel blocks courts. It does not block history.
Why This Matters for the 2026 Round
The 2026 gTLD applicant faces the same architecture. The same procedural traps. The same jurisdictional voids.
The .africa case is not ancient history. It is the playbook.
- The IRP can be won—and still leave the core harm unremedied.
- Discovery can be obtained—and never see a courtroom.
- Estoppel can be applied—not because you lied, but because you told the truth in the wrong forum.
- Staff conduct can be documented—and never adjudicated.
- The record can exist—and be ignored by the very institutions that created it.
- The applicant who ignores these risks is not prepared. They are governance-blind.
A Note to Lawyers
For those who represent applicants in the coming round: study this case. Not just the IRP victory, but the procedural war that followed. Understand that a win in one forum can become a trap in another. Understand that staff conduct is unreachable by the IRP. Understand that evidence of misconduct, no matter how damning, may never reach a jury if your client’s own truthful statements are later used against them.
The .africa case is not a warning about losing. It is a warning about winning the wrong battle.
Plan accordingly.
The Closing
Fifteen years after the application was filed, .africa exists. It is run by others. But the record of who built it, who blocked it, and how the system protected itself—that record is not run by anyone. It is public. It is permanent. It is proof.
They closed the courtroom. They could not close the record.
#EstoppelInAfrica #LegalHistoryMatters #JudicialIntegrity #AfricaGovernance #HistoryCannotBeBlocked
Sophia Bekele
Internet Governance Pioneer | ICANN Reform Veteran
Founder, DotConnectAfrica Group and CBSegroup | 20 years shaping digital policy
This article is part of the dotAfrica Commentary Series, a living archive of analysis, precedent, and warning from the architect of the .africa domain. Read more analysis here →