Forced ~15 minutes maintenance of the historical data

Resolved

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Began at: