Status
System status
The components we monitor and report on. Live incident history is published on this page.
Every component below has a synthetic check that runs from outside our network; the check results drive the provider-hosted page and our on-call rotation. Incidents are declared within 15 minutes of a confirmed customer-facing impact and updated at least every 30 minutes until resolved.
Control plane
- MonitoredPublic API (api.databasezy.com)Provisioning, lifecycle, catalogue
- MonitoredCustomer portal (app.databasezy.com)Sign-in, instance management, billing
- MonitoredDocumentation (docs.databasezy.com)Static, served from the CDN
- MonitoredBilling and checkoutStripe-hosted checkout and invoices
Data plane
- MonitoredGateway us-eastTLS termination and routing for every engine
- MonitoredFree cell us-eastFree-tier instances
- MonitoredStandard cell us-eastPaid shared instances
- MonitoredBackups and restoreScheduled backups, PITR, verified restores
Engines (synthetic checks per engine, per cell)
- MonitoredPostgreSQLv18
- MonitoredMySQLv8.4
- MonitoredMariaDBv11.8
- MonitoredValkeyv9.1
- MonitoredRedis (compat)v7.2
- MonitoredlibSQL / SQLitev0.24
- MonitoredDuckDBv1.5
- MonitoredFerretDB (MongoDB-compatible)v2.7
- MonitoredMongoDB (Percona Server)v8.0
- MonitoredTypeDBv3.13
- MonitoredCouchDBv3.5
- MonitoredMeilisearchv1.54
- MonitoredQdrantv1.19
- MonitoredWeaviatev1.39
- MonitoredInfluxDB 3v3.12
- MonitoredQuestDBv10.0
- MonitoredClickHousev26.8
- MonitoredTimescaleDBv18
Subscribe and history
Subscribe to incident notifications by email, RSS or webhook on the provider page, or ask in the portal to have status updates sent to your org's security contact. Post-incident reviews are published within 5 business days for every incident with customer impact.
- Uptime commitments per plan are in the pricing page and the SLA reference.
- Maintenance windows are announced at least 7 days ahead and never during your region's business hours.
- Security-relevant incidents follow the process on the security page.