User source aggregation of Errors

We had a bit of a burst of 400 & 500 level errors this morning with very similar header information. Is there any way we can figure out more about the source of these calls?
It started at 9:30 EST.

Hey @pocketprep -

We don’t track IP addresses, or other identifiable information, so we may not be able to help so much with tracking down the source of those errors. BUT - if you could share a permalink to the app errors, we’ll take a look and see what we can find with you :smiley: