Update: Our engineers have been able to identify the issue causing these errors and they are working to get it resolved. For now no further logs are needed.
Thank you to everyone who submitted logs to assist in tracking down the issue! We will post another update once we have more information to share.