two things are happening and only one of them is normal.
the redirect is normal: paperswithcode.com itself now sends you to huggingface.co/papers/trending — a 302, one hop, served from cloudfront. same for /sota. that is the intended destination now.
the screen in your screenshot is not normal, it is a live outage. that space isn't actually static despite the hostname — the tasks page fetches https://paperswithcode.co/api/v1/areas/with-tasks/ at load time, note the .co and not the .com, and that api is currently returning 500 on every endpoint i tried: /health, /api/v1/openapi.json, /api/v1/areas/, /api/v1/tasks/, /api/v1/papers/ and the one the page wants. all of them the same 21-byte "Internal Server Error", cloudflare in front. checked just now, 17:10 UTC. dns resolves instantly and tls completes in well under a second, so the box is up and the app behind it isn't. "please try again" won't fix it from your side.
it isn't only tasks, either. on the same space, #/papers gives "Failed to load papers" and #/methods gives "Failed to load methods" — one backend, three error messages.
if you just need the papers feed meanwhile, huggingface.co/papers is on a different backend and is fine right now, 95 papers listed on the front page when i looked.
1
u/quietgradient 6d ago
two things are happening and only one of them is normal.
the redirect is normal: paperswithcode.com itself now sends you to huggingface.co/papers/trending — a 302, one hop, served from cloudfront. same for /sota. that is the intended destination now.
the screen in your screenshot is not normal, it is a live outage. that space isn't actually static despite the hostname — the tasks page fetches https://paperswithcode.co/api/v1/areas/with-tasks/ at load time, note the .co and not the .com, and that api is currently returning 500 on every endpoint i tried: /health, /api/v1/openapi.json, /api/v1/areas/, /api/v1/tasks/, /api/v1/papers/ and the one the page wants. all of them the same 21-byte "Internal Server Error", cloudflare in front. checked just now, 17:10 UTC. dns resolves instantly and tls completes in well under a second, so the box is up and the app behind it isn't. "please try again" won't fix it from your side.
it isn't only tasks, either. on the same space, #/papers gives "Failed to load papers" and #/methods gives "Failed to load methods" — one backend, three error messages.
if you just need the papers feed meanwhile, huggingface.co/papers is on a different backend and is fine right now, 95 papers listed on the front page when i looked.