My guess is that the account suspensions are an automated monitoring process and not someone sitting in a NOC monitoring activity. Think of that automated moni

My guess is that the account suspensions are an automated monitoring process and not someone sitting in a NOC monitoring activity. Think of that automated monitoring like a circuit breaker in an electrical panel. If you plug an air compressor into a 15 amp circuit and it pops the breaker, once you flip the breaker back on would you run the compressor again? No? Then why would you think it ok perform the same activity that tripped up the automated system? The OP seemed to be aware that spooling up 10 VMs to do whatever he did was what got him booted, so... why didn't he reach out to DO to find out exactly what alarms he tripped and then take action to either get his account whitelisted or modify his process to ensure it didn't trip the automated alarms again? He just got his account unbanned (flipped the circuit breaker) and fired his job back up (turned the compressor back on).