Console Incident #16014
Issue with Database Usage metrics in Firebase Console
Incident began at 2016-08-03 16:43 and ended at 2016-08-24 23:59 (all times are US/Pacific).
|Aug 26, 2016||13:03||
A fix was rolled out on August 24th at 4pm US/Pacific. We’ll continue to monitor for any discrepancies.
|Aug 23, 2016||13:22||
Some projects may be missing usage data since the 20th. We have a fix in the works which should be deployed soon.
|Aug 22, 2016||13:07||
The issue with Firebase Realtime Database where Database Usage metrics were not reported accurately should have been resolved for all affected projects as of August 20th. Again, please be aware that the fix may result in an increase in your usage; rest assured this is okay and intended. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to prevent or minimize future recurrence.
|Aug 19, 2016||14:12||
We’re testing a potential fix for the issue. More information will be posted once we have confirmed the results. Again, please be aware that the fix may result in an increase in your usage; rest assured this is okay and intended.
|Aug 03, 2016||16:43||
There is an issue where Database Usage metrics in the Firebase Console are not reported accurately. The reported usage may appear lower than actual usage. We have a fix in progress, which is likely to come out sometime next week. The fix may result in a jump in your usage; rest assured this is okay and intended.