It's a Lemmy thing. Basically latency limits the maximum number of activities that can be sent per second (they're sent like TCP: serially, and each must be acknowledged). When LW has a LOT of activities to send out, they can get backlogged if there's significant latency between LW and other federated servers.