GenMatrix

Yup all good as of 7:17PM EST.
I'm curious to see if anything changes when WAN dies again like maybe being able to access the GUI, all previous occurrences killed GUI access.
I'm hoping it doesn't go out at all though.
I'll keep you updated.

Weird, OK so we're back up and running again now? We have seen it in the past where the WAN interface seems to stay down, though this is usually after a reset not a simple reboot. It's always fixed in the same way as you've found though, surprised it didn't work the first time. For now I don't think that's related to our original issues, though we'll keep note of it. Let us know if you experience another disconnection!

Interesting, can you think of any devices that have since been disconnected/not used as much?

Thank you, we'll take a look at this tomorrow and see if there is anything that will help us diagnose it!

Occurred Again @ 8:25 AM EST 8/19.

Happened again @ 9:53 PM EST 8/16.
I was playing Apex, wife was streaming on apple tv. Nothing else was going other than her phone probably.

Great, thanks for confirming. I've passed this information onto a developer and we'll look into it further for you.

@Netduma Liam Do you mean devices that aren't showing offline in the Device Manager section? If so, hard to tell. The catalyst to prompt me to create this post happened early in the AM (so only smart home devices really) and the first log you gathered was @ 9PM (when all the apple TV's were streaming at the same time, maybe wife was on the phone too + smart home devices) 
I have a lot of smart home devices and we are primarily an apple household. Apple TV's, iPhones and iPads. There's around 55ish devices that connect to my mesh AP.
Does this help?

I wouldn't worry too much, it's not even close to the actual port needed and there is no way they would manage to gain access. It's probably a bot just scanning the internet looking for vulnerabilities.

Hmm interesting. Alright, I've seen some devices that keep showing some DHCP entries constantly even with my the lease time set to 168 hours.
It's not all of them so I will static the ones that keep popping up and see if that helps.

I've managed to get it back online.
Just a few details to share
GUI was working fine in the instances where the router reboots either through power cycle or GUI reboot (or in this latest case, enabling of remote logging). All PC's I used stated DNS bad config on Edge browser. Defining the DNS server manually in the screen shot below allowed the internet to work on my PC but not with Auto Config.

I thought it just happened again. Lol. 
It just rebooted on it's own but I see that way just you guys on your end setting up. Will do.
I have a watchdog on on my NAS so I will know the exact time it goes down in EST and will let you know when it happens again.
I appreciate the support.

With the R2 in the DMZ, the public IP and the WAN IP will appear the same. If the R2 has another router above it and it's not in the DMZ it's show a LAN IP from the upstream router as it's WAN IP.
I've just accessed your R2 and enabled remote logging. Could you please let us know the next time you experience this issue?

Okay thanks for all that, we'll try accessing it again tomorrow and let you know!

Yup, I went to extremes to make sure I did factory reset without introducing any variables other than the PC I was using to initially configure. I let it sit for about an hour, in case it needed to run through any before plugging in my Modem cable and my other devices (AP for wifi and dumb switches)
I've enabled the setting below.

Absolutely love the the R2 and I'm sure this has been suggested before but I'd love to see an option to schedule a reboot.