cybre.space users: this appears to be due to the cybre.space web server taking too long to respond and returning a 504 / timeout error. if you see this happen, it might mean the server is just processing slowly and will eventually submit the post! (looking into why it's taking so long, but this should help you avoid accidentally submitting duplicates in the meantime)
@TheGibson we seem to be good on memory and the sidekiq queues are empty, weirdly. current theory is it might be a slow db connection, possibly due to disk i/o
@chr cybre's hosting has repeatedly broken in various ways more frequently than seems normal for Cloud Hosting Providers and like, don't they have SLAs or something? i don't understand
@haskal digitalocean is definitely failing their SLA, but hetzner has been basically fine til now aside from an occasional short outage that kicked something of ours over. we are unfortunately getting what we're paying for, there, though.
@chr did the issues coincide with a backup window of some kind? I used to get this kind of behaviour periodically, and it took me ages to put 2 and 2 together and realise what was going on.