On Feb 21 at about 17:00 UTC several components of our service begun experiencing problems. The root cause was an internal component running wild, which consumed all available local disk space, preventing normal operation, and also automatic recovery. The service was restored to partial capacity at Feb 22 8:20 UTC, and to full capacity at 8:43 UTC.