Is it a bug? And I feel it often happened these days (about in this month), emmm... UPD:It has been fixed.
| # | User | Rating |
|---|---|---|
| 1 | Benq | 3676 |
| 2 | Kevin114514 | 3659 |
| 3 | jiangly | 3640 |
| 4 | turmax | 3450 |
| 5 | tourist | 3382 |
| 6 | strapple | 3360 |
| 7 | Um_nik | 3354 |
| 8 | squareOf105 | 3348 |
| 9 | maroonrk | 3312 |
| 10 | idontwannadothis…e | 3191 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 155 |
| 2 | nik_exists | 151 |
| 3 | maspy | 149 |
| 4 | AmShZ | 145 |
| 5 | Um_nik | 143 |
| 6 | Errichto | 139 |
| 7 | BledDest | 136 |
| 8 | adamant | 134 |
| 9 | maroonrk | 132 |
| 10 | cry | 130 |
Is it a bug? And I feel it often happened these days (about in this month), emmm... UPD:It has been fixed.
| Name |
|---|



MikeMirzayanov Can you help us fix the problem? Or it is updating now and the problemset is hidden?
I am having this issue as well. I cannot access the problemset or contest pages for at least the last few hours.
In the meanwhile, you can still access problems by appending "/problems" to end of contest URLs!
For example, http://codeforces.me/contest/875/problems
Thanks. can we submit solutions too?
Unfortunately, we can't.
I am facing this issue too , I think this issue is going on since ROUND 466. I hope they fix this soon.
Submissions page is also not opening.
I can't see the no. of problems i have solved in a contest(2 out of 6 solved).
Even if I try to enter some contest in the contests page it is giving error in addition to problem set and the submissions page . Hope this will be fixed soon .
Zlobober rng_58
Same error
The greatest questions of all time, vol. 2:
...
143. Who killed Kennedy?
144. Why did NursuItanTolshybek mention Zlobober and rng_58 when Codeforces problemset was not working.
...
Your and rng_58 profile wasn't worked when Codeforces problemset wasn't worked
Your point no. 143 launched me onto the Wikipedia page describing the conspiracy theories. Damn, I had no idea about this and always thought some random person shot him but looks like strings were being pulled elsewhere.
Fixed, thanks. It was a hardware issue. I'm working on prevention of such cases.