Hi Beaverbot40,
A few hours can still be normal depending on the previous TTL, but I’d verify the authoritative DNS first instead of relying only on propagation checkers.
From a terminal, run:
1dig NS beaverbot.app +short2dig A beaverbot.app +short3dig CNAME www.beaverbot.app +short4dig A www.beaverbot.app +short5dig AAAA www.beaverbot.app +short6
The NS result is important because it tells you which DNS provider is actually authoritative. Make sure that is the same provider where you added the records. A common issue is editing records at one provider while the domain is still delegated to another provider’s nameservers.
For Vercel, the apex/root domain beaverbot.app should match the A record Vercel shows in the Domains tab, and www.beaverbot.app should usually be a CNAME to the exact target Vercel shows. www should not also have a conflicting A or AAAA record.
Also make sure both beaverbot.app and www.beaverbot.app are added to the same Vercel project. Since www.beaverbot.app is your main site, set that as the primary domain and redirect the apex to it, or vice versa.
One useful thing to share back is the output of those dig commands. You can redact unrelated records, but don’t post any registrar login details or private account info.