Upload notifications

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have slightly lowered the impact from Critical to Major.

We are continuing to work on a fix for this issue.

Customers with HTTP notification endpoints that support http/2 but were validating or expecting incoming HTTP header names in a case-sensitive way are experiencing issues since a recent deployment updated our outbound requests to use http/2 by default, which requires header names to be sent in lower case.

We're deploying a fix to force http1.1 for our outbound requests to help customers work around this, and also recommend that any application code which is parsing header values is updated to be case insensitive, in keeping with the relevant HTTP RFCs.

Our team has identified and narrowed down the issue related to signature and timestamp headers being omitted.

We are currently investigating the issue and looking for a solution. We have elevated a critical status for this incident. We will provide further updates.

On June 20th, 2023 5:00 PM UTC, We have identified a potential issue with our upload mechanism where the signature in the payload request may have been omitted. We will provide further updates.