August 31: Fly-proxy HTTP/2 routing broke due to missing Consul service rows

#August 31: Fly-proxy HTTP/2 routing broke due to missing Consul service rows (15:20UTC)

A manual cleanup/config change to our Consul service registration data briefly removed the HTTP/2 routing entries for fly-proxy on a subset of hosts. During that window, some HTTP/2-based traffic to Machines on those hosts could fail. We mitigated the issue by restarting the service-registration sync agent on affected hosts/regions to republish the missing entries, restoring normal routing.