400 errors causing session capture to fail for some Sites

Our engineers were able to roll back the changes that triggered this issue and this incident is now resolved. The 400 errors no longer appear on affected sites, and data collection has resumed.

Thanks for bearing with us!

On March 22, 10:00 UTC, we rolled out a change to our ingestion service, it included updates to how we compress and store page content, including the URL. These URLs are causing 400 errors in our servers which reject the page content and causes session processing to fail.

Our engineering team has identified the root cause of the problem and is actively working on a solution to resolve the issue. As of now, users might experience intermittent disruption to their sessions due to these 400 errors.

Thanks for bearing with us while we work to resolve this issue!