Service status
MEASURED OVER 7.1 DAYS · NOT AN SLAMeasured from what the service produced, not from a separate monitor. Every figure states the window it came from.
Source outages
How many city-readings each upstream failed to deliver since metrics collection began. Eight of the eleven arrive through one aggregator, so an outage there shows up across eight rows at once.
| kweather | 7 |
Verdict mix
Cumulative counts since metrics collection began. verified means measurements corroborated the published value; mixed means they were split; single_source means only one measurement could be read.
| verified | 86 |
| mismatch | 39 |
| mixed | 38 |
| single_source | 4 |
What these numbers are not
The service has been running publicly for 7.1 days, so every percentage here comes from that window and not from a long record. A high figure over a short window is weak evidence, and we would rather say so than let the number stand alone.
This is a measurement, not a service level agreement. Nothing on this page commits us to an availability target or entitles anyone to a credit. Availability commitments for insurance or hedging use are agreed separately with KWeather.
On-time runs are derived from the gaps between anchored snapshots: collection runs hourly and a successful run leaves one snapshot, so the spacing of those rows is the record. A gap wider than 90 minutes counts as one missed slot per hour skipped.