Nothing is actually pushed around the internet. When you change a record, your DNS host answers with the new value straight away. What takes time is caching: every resolver that looked the name up recently keeps its copy until the record's TTL runs out.
- Record changes (A, CNAME, MX, TXT) show up everywhere within the old TTL: usually 5 minutes to an hour.
- Nameserver changes are slower: the TLD's own servers hand out the NS records for your domain with long TTLs (48 hours for .com), which is where the "24–48 hours" advice comes from.
- Plan a move: lower the TTL to 300 seconds a day before the change, make the change, and raise it again afterwards.
- "My new record isn't showing" is often negative caching: if anyone looked up the name before it existed, resolvers cache the "no such name" answer for the SOA minimum (often an hour).
- A few ISP resolvers keep answers longer than the TTL. You can't speed those up; they catch up on their own.
The Propagation tab asks five independent public resolvers (Cloudflare, Google, Quad9, DNS.SB, Control D), marks each answer ✓ or ✗ against the value you expect, and counts down until each cached old answer expires.