https://codeforces.com/gym/101889

source 60ac8b668c10 · match key codeforces.com/gym/101889 · all sources

live

https://codeforces.com/gym/101889

wayback

calendar of snapshots

roles

judge page

health

live checked 2026-11-03 — mentions year 2017±1 (no snapshot to compare)
live: the address still serves the contest-era content (identical or ≥75% similar to the near-contest snapshot, or mentions the contest year)

referenced by

brazil-2017 judge page · Codeforces Gym — 2017-2018 ACM-ICPC Latin American Regional Programming Contest (judge hunt 2026-11-03: name+year: '2017-2018 ACM-ICPC Latin American Regional Programming Contest' -> season start 2017)
caribbean-2017 judge page · Codeforces Gym — 2017-2018 ACM-ICPC Latin American Regional Programming Contest (judge hunt 2026-11-03: ICPC Latin America Regional 2017 is one shared problem set across all LA finals (Brazil, SA-South, SA-North, Mexico, Central America, Caribbean); gym named for the whole LA regional)
central-america-2017 judge page · Codeforces Gym — 2017-2018 ACM-ICPC Latin American Regional Programming Contest (judge hunt 2026-11-03: ICPC Latin America Regional 2017 is one shared problem set across all LA finals (Brazil, SA-South, SA-North, Mexico, Central America, Caribbean); gym named for the whole LA regional)
south-america-north-2017 judge page · Codeforces Gym — 2017-2018 ACM-ICPC Latin American Regional Programming Contest (judge hunt 2026-11-03: ICPC Latin America Regional 2017 is one shared problem set across all LA finals (Brazil, SA-South, SA-North, Mexico, Central America, Caribbean); gym named for the whole LA regional)
south-america-south-2017 judge page · Codeforces Gym — 2017-2018 ACM-ICPC Latin American Regional Programming Contest (judge hunt 2026-11-03: ICPC Latin America Regional 2017 is one shared problem set across all LA finals (Brazil, SA-South, SA-North, Mexico, Central America, Caribbean); gym named for the whole LA regional)

Snapshots (2)

One entry per time this address is known at: Wayback snapshots we captured, our live fetches, and times the catalogue declares (as_of) without a capture. Each capture is our stored copy, with its provenance.

Checks (2)

Every time this address was looked at and what came back. A check that found no content is a record of the attempt, not a snapshot.