Service status
Availability
Availability of the /v1 API since 3 Aug 2026 (2 days recorded so far).
2 days are based on incomplete monitoring and are counted as unavailable — see the method below.
Every day, as a table
The same figures, for anyone who cannot use the chart above.
| Date | Availability | State | Monitoring coverage |
|---|---|---|---|
| 4 Aug 2026 | 5.08% | Below commitment | 5% |
| 3 Aug 2026 | 20.00% | Below commitment | 20% |
How this is measured
The API is probed every five minutes from outside our infrastructure — deliberately not from the servers being measured, because a monitor running on a machine cannot report that machine going dark.
Because the prober writes its results back to us, an outage shows up as missing samples, not as recorded failures. We therefore measure each day against the number of checks that should have happened, and count anything missing as unavailable. That means a period when our own monitoring was interrupted is counted against us rather than quietly excluded — the figure above can understate our availability, and by design it will never overstate it.
Days are Australian Eastern time. The chart shows state rather than height because availability sits between 99% and 100%, where a bar chart would show nothing a reader could see; the exact figure for every day is in the table.
Planned maintenance
Our maintenance window is Sundays 01:00–05:00 Australian Eastern time. Work that could interrupt the API is scheduled inside it wherever possible, and Enterprise customers are notified by email at least 48 hours beforehand. The quarterly G-NAF dataset refresh runs inside this window; it is designed to swap the index in place without downtime, and is announced regardless.
Something wrong that this page does not show? support@wattleaddr.com.au