Service status

Availability

Availability of the /v1 API across the time we observed it, since 3 Aug 2026. We checked 99% of that period.

Every day, as a table

The same figures, for anyone who cannot use the chart above.

How this is measured

A server in Melbourne checks the address API and the website every minute. It reaches them through public DNS, the same way a customer’s software does, so the figures include the automatic switch between our Sydney and Melbourne servers for the API. A check counts as available when the address answers with a normal success or redirect response. It does not test searches. Because the checking server is separate from the Sydney primary, it can see Sydney go down. An interruption shorter than a minute can fall between two checks.

Until 19 October 2026 the record came from a different monitor that ran roughly once an hour, so earlier days have far fewer checks. The Melbourne server’s own log goes back to 14 August 2026, and those minute-by-minute results were added to the record for the days it covers. Before 14 August, days were measured only by the hourly GitHub monitor.

Each check states the service’s condition at that instant, and the time until the next check is credited to it. Availability is the share of the time we observed that was available. Where two minute-by-minute checks are more than five minutes apart, we do not know what happened in between. That time is counted neither way. It is left out of the figure and shown as reduced coverage instead. The older hourly records use a longer limit of five hours.

What this does not cover: if the Melbourne server itself is down, or cannot reach the website to save its results, nothing is recorded for that time. If the website is down at the same moment, the result cannot be saved either. While the website’s own name points at Melbourne during a switch, the checks would be Melbourne checking itself, so those minutes are not recorded. The API has its own switch to Melbourne. While that is in effect, the API check is also Melbourne checking itself, so the API is not recorded for that time. In every case the time shows as lost coverage, not as downtime, because a status page cannot prove its own total outage. Coverage is the figure that shows those periods.

Days are Australian Eastern time. The chart shows state, not height, because availability sits between 99% and 100% and a bar chart would show no visible difference. 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 we announce it anyway.

Something wrong that this page does not show? support@wattleaddr.com.au