Hey y’all! Carolina from support here!
Had a case today that I thought was worth sharing here in case someone else runs into it.
A customer reached out in a panic, saying they couldn’t access their Run and neither could their clients. From the outside it looked like a full outage.
If something like this happens to you, 9 times out of 10 it’s a DNS issue. Records get changed, the provider pushes an update, propagation is still rolling out, that kind of thing. So that’s where we always look first.
In this case it was payment. The domain registration had lapsed and the registrar suspended it. DNS was technically fine, but the domain itself was no longer active.
So next time your custom Run domain suddenly stops working, run through this short list:
-
Check DNS records on your provider (still the most common cause)
-
Wait up to 30 minutes for propagation if you changed anything recently
-
Check that the domain is still active with your registrar
-
Confirm the renewal payment actually went through
Easy to miss that last one, painful to debug if you don’t think to check it!!
Hope this tip helps others running into the same thing.
Cheers,