Keep the owner and package path clear
A DDoS event can create pressure to change firewall rules or service settings quickly. Tor Project’s 0.4.9.17 notice asked relay operators to install a release with updated defenses and said more changes could follow.
Each relay should have an owner, a supported update source and a way to check whether the process has returned to service. If a provider manages the host, record how to request an emergency update.
Use a controlled response
Check the official Tor release notice before changing IPv4 or IPv6 rules. Apply the supported software update, confirm the process version and monitor circuit load and network health. Avoid broad network changes that can disconnect the relay or affect unrelated services.
Keep logs and health metrics during the event. Note the time of package update, restart, service recovery and any changes made by the hosting provider.
Plan for follow-up releases
Subscribe to Tor Project release channels and assign someone to review new notices while the incident continues. Track which relays have updated and which need supplier action.
This process applies to relay operators. Users of Tor Browser should use its own update channel and should not perform relay server changes unless they also manage a relay.
