The event data ingestion lag accumulated during the outage today is caught up, and the incident is resolved.

Session recordings ingestion processing delays have caught up.

Event and data ingestion success rates are looking stable. We're monitoring

After a shaky period with elevated error rate for events and session replay events, we're observing recovery to normal levels.

As the AWS outage is not fully resolved, we're monitoring.

We will update once we know more, currently it looks like it's going in the right direction.

We observed elevated error rates for even and data ingestion - we're investigating.

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

We're are now processing destinations events and should catch up shortly

Replay ingestion has now recovered and we are no longer experiencing any session replay data loss.

AWS is still having issues with some services which is impacting replay processing but we are seeing this recover slowly

Event ingestion has fully recovered. There may be small delays on sub components such as UI autocompletion.Replay ingestion is recovering but still experiencing partial data loss. Clients are retrying so some data recovery should be possible but it is highly likely during this incident that recording data will be incomplete since the incident started.

AWS is recovering and therefore we are also managing to start recovering and scaling up our infrastructure to catch up.We are still heavily delayed across services.Session Replay ingestion is still not fully recovered although we are seeing improvements and expect it to recover soon.

AWS is having a major outage. Services build on components that are affected by the outage are having issues. Session Replay is having a major outage. Ingestion and CDP is degraded.

One of our upstream providers is having an outage, CDP / Destinations is also affected and processing is delayed.

we're working on a fix