At 10:30 UTC time, we received notification that our homepage was not connecting. Upon further investigation, it turns out an automatic container reboot caused an invalid nginx config to be enabled, thus nginx was unable to start. We removed the rogue configuration and the issue is now resolved.