Why WattleDBFeaturesPricingvs SupabaseIndustriesBlogFAQContactSign inStart free
WattleDB  /  System Status

System Status

Live component health & incident history · measured from launch

All systems operational

No active incidents. Sydney primary and Melbourne backup are healthy.

Last checked —

Console & REST API
app + auto-generated PostgREST APIs
Operational
Database — Sydney primary
au-syd-1 · NEXTDC S1, Sydney NSW
Operational
Backups & DR — Melbourne
NEXTDC M2, Melbourne VIC · cross-state backups + PITR
Operational
Object storage
S3-compatible, Australian-hosted
Operational
High-availability standby
hot failover node — being added
Planned
Uptime history

Each bar is one day. We publish only what we have actually run, so the record starts at launch — we don't backfill dates from before WattleDB existed. Grey means “before launch, no service to measure”.

90 days agotoday
Since launch
—
days in service (from 12 Jul 2026)
Incidents
0
customer-impacting, since launch
Uptime commitment
99.5%
per the SLA, paid tiers
Incident history
No customer-impacting incidents have been recorded since launch on 12 July 2026. When an incident occurs, we post it here with a timeline and a plain-English post-mortem. For the availability commitment and service credits, see the Service Level Agreement.

This page reflects real operational status, not a marketing figure. Formal, continuously measured monthly uptime percentages are published here as our external monitoring record accrues. Questions about availability for a specific workload? Talk to us.