Website downtime

Lately the website is showing errors. This could be HTTP error 500 or 503, or just slow in general. We have adjusted some settings and we will keep an eye on our reporting software and the logs to see if it solves the problem.
Our status page isn’t updated automatically yet, so we manually need to update it. This could mean there is some delay between the incident and the update on the status page. That’s why there was no Twitter post, since it was a couple of hours/days after the fact, and it wouldn’t serve any purpose.
Categories: ForestBlog,website