Trust & Security Centre
Monitor access, investigate threats and protect Our Badminton services from one trusted workspace.
Security overview
Cloud Run monthly request allowance
Shared across all projects and environments on the same billing account. Test and production do not each receive a separate allowance. The date filter below does not change this monthly allowance.
Remaining allowance requires billing-account-wide usage for the applicable request SKU. Daily service logs are not a billing balance and may be incomplete. Connect a Cloud Billing export before calculating this figure; unavailable does not mean zero remaining.
This is a pricing allowance, not a hard traffic limit. CPU, memory, networking, load balancing, CDN and other services may still incur charges. Instance-based billing has different pricing.
Google Cloud Run pricing and free-tier detailsRequests by service
Loading request counts…
— recorded service requests
| Service | Total | 1xx | 2xx | 3xx | 4xx | 5xx |
|---|
All HTTP statuses, not just errors. A request passing through the BFF and another service counts once for each service. Load-balancer entries are excluded to avoid adding a second counting layer. Only retained request logs are counted; zero-traffic services are omitted.
Cloud Run Access
Environment determined by the connected service · UTC date
3xx: redirects or cached responses, not necessarily errors. 4xx: client or access failures. 5xx: critical server failures requiring investigation.
| Time | Service | IP | Method | Path | Status | User Agent |
|---|
Firebase Access
| Time | Actor | Action | Resource | IP | Result |
|---|
Threat Signals
Firebase Backup
Manually trigger a Firebase Realtime Database backup to Google Drive.
Recommended Checks
- Repeated 401/403 responses from same IP
- Unusual admin login locations or times
- High 5xx error spike on Cloud Run
- Firebase writes outside admin workflows
- Suspicious user agents or scanners
- Backup freshness and restore readiness