@rysiek OTOH, just fixing the issue with multiple UWSGI workers might have avoided this issue. Currently everything is just one UWSGI worker and the nginx caching.
Anyhow, monitoring indicates the big spike is over and the site is reachable again. :)