This was a bug that we are fixing. The system that tracks the activity to validate whether the instance was active or dormant had an issue for a few Databases and incorrectly identified them as dormant when they were active and paused them.
This isn't happening at the moment and we're continuing to monitor.
Your database will not be paused while we are ironing out this particular niggle, which will correctly report the activity, and we should have all this resolved by this afternoon.