Waiting for provider data
Checking03:00 Istanbul · 00:00 UTC
Resets at the start of next month
Cloudflare
Workers, D1 & game rooms · account-wide
Firebase
Hosting transfer & retained releases · project-wide
Firebase shows the last manual import. Google requires billing for this project’s server-side metrics access, so live refresh stays disabled to preserve Spark. Refresh these readings from this Mac with npm run usage:firebase in the dashboard folder. Firebase usage ↗
Daily history
UTC calendar days · today is partial
Select a day to inspect its usage.
Daily values & timestamps
Read the numbers
Cloudflare usage refreshes only when you click Update. Firebase uses manual imports. There are no scheduled checks or automatic refreshes. Each manual check reads the latest three days to catch late reports, with a five-minute pause between checks to limit overhead.
Cloudflare analytics can use sampling. Durable Object invocations are shown as a conservative upper bound. Missing or failed data is never replaced with mock values.
Storage is retained capacity and has no reset. Its graph shows recorded levels or reported daily peaks, rather than bytes added each day.
Hard platform limits
Maximum allowed by the configured plan. Actual consumption is shown separately in the last column.
| Resource | Maximum allowed | Your measured use |
|---|---|---|
| Workers CPUPer invocation | 10 ms | Not collected here |
| Workers memoryPer isolate | 128 MB | Not collected here |
| D1 storagePer database | 500 MB | Waiting for measurement |
Authentication setup: Google sign-in with standard Firebase Authentication. This describes the login method; no usage count or Identity Platform allowance is shown.
Limits reference the Free and Spark plans configured for this project. A plan label is not a live billing verification. Cloudflare limits ↗ · Firebase limits ↗