We're trying our best...

You might have seen "Internal server error 500" lately. Were working on it!

Why is the site breaking?

Short answer: We don't know.

Long answer: It seems like key components from the front-end server (the machine that gave you this page) go missing, and restarting it doesn't bring them back. We have investigated low-effort fixes, with little to no success. We have decided to upgrade the node/next version we are working with to see if it helps. It will take a couple of days. In the meantime, we will monitor the site as closely as we can, and try and keep it alive until a permanent solution is done. 

Thank you for your patience! 

Update 26.10

We are still working on this, and might have gotten to the root of the problem, we will keep you posted! There are still some issues to solve, but we should be close to a solution now.

Update 30.10

Things are looking more stable, and we have pinpointed what goes wrong. By disabling cache revalidation on the next server, the issues have stopped. The bad news is that the site is slower. We are looking into a fix.

Back to News