This has now been resolved. The impacted repository has been removed, preventing any further issues.

A corrupted repository on the forgejo instance has caused some degradation of performance and a little downtime, due to memory leaks, causing the service to crash, automatically recover itself, and repeat.