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 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 150 |
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://mirror.codeforces.com/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.