I can confirm I’ve resolved this with a couple of client MX devices by ensuring that at least the secondary DNS is google (8.8.8.8). Sometimes the local or ISP DNS does not quickly resolve the cloud so MX cannot connect to the cloud. When using 8.8.8.8, it can find the cloud faster. You might be able to turn that back off once the connection to the cloud is reached. Don’t let downstream devices properly connecting distract you into thinking all is good - there is a difference between administration dashboard & payload routing.
... View more