We've resolved this issue by rolling back our destination configs table to a previous known good state. A change was made to the table that corrupted the table that we instantly recognized, which caused us to restore the table from our nightly backups.

During the time that the destination configs table was corrupted, data was processed and sent to our single tenant destination and object storage destinations were not active. You will notice a small hole in your data during this time period if you are using a custom destination.

There's an issue with RunReveal custom destinations that we've identified and are working towards resolving. We identified it instantly and are working to resolve the issue.