UPD: Several months have now passed since this issue was first raised through official ICPC channels.
During this period, we have corresponded with contest officials, ICPC management, and senior members of the ICPC organization, including individuals at the highest levels of the organization, seeking a technical reconciliation of the published standings. The matter was also formally raised through our team's official coach, who submitted and endorsed a request for review through the ICPC process.
While we have received procedural responses, we have not received a technical explanation addressing the discrepancy.
In particular, we are still unaware of any explanation reconciling the published contest limit and the accepted submission timestamp discussed later in this post. We are likewise unaware of any explanation for certain published extra-time values that appear difficult to reconcile with the compensation procedure.
Because this concerns a World Finals-qualifying regional and the certified published standings, we believe clarification remains important not only for our team, but for the broader competitive programming community.
If anyone familiar with DOMjudge, ICPC contest administration, standings reconstruction workflows, or similar situations has encountered a comparable case, we would greatly appreciate any insight.
Likewise, if anyone is aware of a standard technical or administrative mechanism that explains the published metadata, we would be grateful to learn about it.
At present, our objective remains unchanged: to understand how the published standings reconcile and whether a technical explanation exists for the discrepancy.
After several months, multiple follow-ups, and formal escalation through both team and coaching channels, the question remains open.
Original Post
Note: This discrepancy concerns the standings of the Rank 1 team and may therefore have implications for World Finals advancement and certified regional outcomes.
Has anyone encountered situations where published ICPC standings appeared difficult to reconcile with the compensation procedure?
This concerns the ICPC Asia Peradeniya Regional 2025/26.
Summary
The published standings for the Rank 1 team currently contain:
- Contest duration: 240 minutes
- Extra time: 28 minutes
- Contest limit: 268 minutes
- Certified accepted submission timestamp (Problem G): 272 minutes
However, 272 > 268.
The remainder of this post explains the context and why this appears difficult to reconcile.
The Context
The official contest duration for the regional was 4 hours (240 minutes).
During the contest, the judging system for Problem A was returning incorrect "Wrong Answer" verdicts on valid solutions due to a checker issue. To address this, the organizers announced an onsite extra-time compensation procedure for Problem A.
Under this procedure, the "Extra Time" value represented the amount of contest time effectively spent on Problem A before obtaining an accepted solution. This was calculated using the timestamps of a team's submissions for Problem A:
Case 1: If a team made multiple submissions for Problem A, where the second-to-last submission occurred at time T1 and the accepted submission occurred at time T2, the awarded extra time was calculated as T2 − T1.
Case 2: If a team made only a single submission for Problem A, the awarded extra time was equal to the full timestamp of that accepted submission.
For example:
- If a team submitted a valid solution to Problem A at T=30 (which incorrectly received a "Wrong Answer" verdict due to the checker issue), and their very next attempt at T=50 received an "Accepted" verdict, the team would receive 20 minutes of extra time.
- If a team's first accepted submission for Problem A occurred at T=45 with no prior submissions to the problem, the team would receive the full 45 minutes as extra time.
These "Extra Time" values were then incorporated directly into the final penalty, score, and standings calculations.
The Standings Discrepancy
After reviewing the final published standings metadata, some published timestamps and extra-time values appear mathematically difficult to reconcile with the announced operational procedure.
To illustrate the specific discrepancy in the standings for the Rank 1 team:
- Base contest duration: 240 minutes
- Extra time: 28 minutes
- Contest limit: 268 minutes (240 + 28)
- Certified accepted submission timestamp (Problem G): 272 minutes
However, 272 > 268.
The certified standings include an accepted submission for the team timestamped at 272 minutes.
Under standard DOMjudge behavior and the announced compensation rules, I have been unable to reconcile how a submission timestamped at T=272 maps onto a contest limit of T=268.
Standings referenced above:
Official ICPC Global Results: https://icpc.global/regionals/results
Referenced Standings: (Note: To independently verify this source, navigate to the Official ICPC Global Results link above, locate "The 2025 ICPC Asia Peradeniya Regional Contest," and click the globe icon in the standings column. It redirects directly to this document). https://docs.google.com/spreadsheets/d/1-utxaWV7frrWjOTRJuNoGmFtrSwXQbQN/edit?gid=1483018665#gid=1483018665
Why This Matters
Our concern is not limited to a single submission timestamp. Additional published extra-time values also appear difficult to reconcile with the announced compensation procedure.
There appear to be broader reconciliation problems in the published standings, of which the 272 > 268 discrepancy is the most visible example.
Because the extra-time values were incorporated into the final score and penalty calculations, even small reconstruction inconsistencies can affect competitive outcomes when standings margins are extremely narrow.
Over the past several months, we have exhausted the standard administrative channels and escalated this inquiry directly to ICPC Global Judging and Systems leadership. Despite the multiple follow-ups and escalation attempts, we have not yet received a technical explanation reconciling the published metadata and standings calculations.
The Ask
I am not posting this to make accusations against any team or individual organizer.
I am trying to understand whether a known technical or administrative explanation exists for this type of reconstruction discrepancy.
In particular, I would be interested in hearing from people familiar with:
- DOMjudge architecture and contest locking behavior
- ICPC regional standings reconstruction workflows
- Post-contest penalty handling
- Operational contest administration practices
Is there a standard technical or administrative mechanism in DOMjudge or ICPC operations that can explain how a certified accepted submission timestamp exceeds the contest limit?










One thing I want to clarify since some readers may interpret the issue differently:
My concern is not simply that a submission appeared after the original 240-minute contest duration.
The reconstruction question arises specifically because the published compensation metadata itself appears to imply an adjusted contest limit of 268 minutes for the affected team, while the certified standings simultaneously contain an accepted submission timestamped at 272 minutes.
So the issue I am trying to understand is whether there exists some standard DOMjudge or ICPC operational mechanism that can reconcile these two published values.
To make independent verification easier, the specific reconstruction discrepancy can be found in the published Google Sheet used for finalizing the standings:
https://docs.google.com/spreadsheets/d/1-utxaWV7frrWjOTRJuNoGmFtrSwXQbQN/edit?gid=1483018665#gid=1483018665.
The 272-minute submission appears under the Problem G column for the Rank 1 team, while the corresponding 28-minute compensation value appears in the “Extra Time” column.
As outlined in the context above, this produces a reconstruction scenario where the final certified submission timestamp exceeds the published contest limit derived from the compensation procedure (240 + 28 = 268).
i didnt pay much attention to the storyline or anything above but the general issue itself, icpc regionals and natioanals have an insane amount of checker / statement issues i dont understand how a simple team of teens making a codeforces round does an infinitely better job than current icpc cordination and setting teams
Totally agree on the systemic issues. Just to give the quick TLDR of the post since it's a bit of a dense read: the organizers published a contest limit of 268 minutes, but the final certified submission is timestamped at 272 minutes. So the final standings currently contain a submission timestamp that appears to exceed the contest limit.
last year in the syrian icpc nationals (which was split into 3 sites, in Homs, Latakia, and Damascus for unimportant reasons) submissions in Latakia and Damascus weren't open for like 15 minutes at the start and throughout the contest had a long delay, my team lost about 45 minutes penalty because one of our submissions got WA because of an int overflow which we immediately corrected, but we didn't find out until 45 minutes after submission because the queue was so slow.
I guess there's a reason why you don't split a competition into 3 simultaneous sites :p
That's a rough experience. While it's a different issue, it highlights the same underlying problem: once contest administration affects competitive outcomes, teams deserve a clear explanation of how the final standings were determined.
In your case, the cause of the issue seems clear: judging delay. In our case, the challenge is that we still do not understand how a final submission timestamp can exceed the contest time limit.
Its probably just an minor export issue, don't worry