Why WattleDBFeaturesPricingvs SupabaseIndustriesBlogFAQContactSign inStart free
WattleDB  /  System Status

System Status

Component status & declared incidents · days in service from launch

No incidents declared

We have not declared an incident affecting the Sydney primary or the Melbourne backup.
Console & REST API
app + auto-generated PostgREST APIs
In service
Database — Sydney primary
au-syd-1 · NEXTDC S1, Sydney NSW
In service
Backups & DR — Melbourne
NEXTDC M2, Melbourne VIC · cross-state backups + PITR
In service
Object storage
S3-compatible · served from Sydney · backup copy in Melbourne · not covered by the SLA
In service
Warm standby — Melbourne
NEXTDC M2 · database replicas kept in step · promotion is manual, not automatic failover · not covered by the SLA
Partial

“In service” means the component is deployed and we have not declared an incident against it. These rows are maintained by our operators when we declare or resolve an incident; they are not a continuous automated probe, and this page does not poll anything when you load it.

Days in service

Each bar is one day since launch. This strip shows days in service, not measured availability — we do not yet run external uptime monitoring, so a coloured bar means “WattleDB was running that day and no incident was declared”, not a measured percentage. 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
declared as 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.

We do not yet publish continuously measured uptime. This page records the incidents we have declared and the components we have deployed; the strip above shows days in service, not measured availability. We are standing up external uptime monitoring, and when it is running we will publish formal monthly uptime percentages here and say plainly which month they start from. Until then, treat the 99.5% figure above as the commitment we make in the SLA, not as a measurement. Questions about availability for a specific workload? Talk to us.