Over the past couple of days, Visualizer saw repeated automated attacks that intermittently triggered 503 errors. The service recovered on its own within ~30 seconds each time, but there were brief windows of unavailability. I’ve applied several hardening fixes based on what these attempts revealed. I don’t see evidence of data access, and I’ll continue to monitor closely.

visualizer.coffee recovered.

visualizer.coffee went down.

visualizer.coffee recovered.

visualizer.coffee went down.