PlanWire External service monitoring
Monitoring unavailable
No current verified observation. API availability is unknown.
Waiting for the external monitor.
Last 30 days
Collecting history
No observations available
Last 90 days
Collecting history
No observations available
Daily observations
Incident history
Incident history unavailable.
Incidents are based on scheduled observations, not exact outage start or end times.
What we measure
An external server, separate from PlanWire's API hosting, sends an authenticated planning query every five minutes. A successful check must return HTTP 200 and an identifiable Richmond upon Thames planning record within ten seconds.
30- and 90-day percentages appear only after the full window has elapsed and at least 99% of scheduled observations have known results. Availability is successful checks divided by successful plus failed checks. Missing checks and monitoring credential or allowance problems are unknown, shown separately, and never counted as successes.
This is sampled availability from one external location, not a continuous uptime measurement, a guarantee or an SLA. Checks more than six minutes and 30 seconds old are treated as unavailable. A failure to retrieve current observations also makes live status unavailable.
API availability is not data freshness
An available API can serve records from a council whose source has not updated recently. This check does not measure all endpoints or council sources. Inspect council coverage and freshness.