# GitHub audit log streaming incident caused by configuration linked to a soft-deleted Enterprise

DevFeed: [GitHub audit log streaming incident caused by configuration linked to a soft-deleted Enterprise](<https://devfeed.tech/articles/we-are-investigating-reports-of-degraded-performance-76277.md>)

Original publisher: [Read original article](<https://www.githubstatus.com/incidents/dxthh9653wkk>)

Published: 2024-01-09T04:59:00Z

Content type: news

Language: en

Sources: [GitHub Status - Incident History](<https://devfeed.tech/sources/github-status-incident-history.md>)

Topics: [Streaming](<https://devfeed.tech/topics/streaming.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [incident](<https://devfeed.tech/tags/incident.md>), [logs](<https://devfeed.tech/tags/logs.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

## AI overview

On January 9, a configuration linked to a soft-deleted Enterprise caused a backend runtime error that stopped audit log events from streaming for some customers. The issue was mitigated by removing the configuration, and the affected events were delivered afterward. GitHub says it improved error detection and support for similar scenarios.

## Source excerpt

On January 9 between 1:06 and 5:43 UTC, no audit log events were streamed for customers that have that enabled. All events that happened during this time were delivered after the issue was mitigated. The event delivery was failing due to a data shape issue, with a streaming configuration linked to a soft-deleted Enterprise causing a runtime error for a backend service. This was mitigated by removing that configuration. Since the incident, we have improved our detection of these errors and ensured support for similar scenarios.