MONITORING COVERAGE · CURRENT ARCHIVE

Station reporting

Last readings, reporting gaps and changes of feed.

Loading the current archive report…

What has stopped?

Publisher status is the clearest evidence we have. A station marked closed or suspended is shown separately from a station whose recent readings have not reached our archive.

Thames Water’s monitor snapshots distinguish an operator-reported offline state from historical discharge events. Each status shows its source check time. An old event, or no new event, does not by itself mean a monitor is offline.

One missing check or repeated outages?

A reported offline status is one observation. The event-history feed can provide separate offline start/stop pairs. Choose Repeated offline episodes to see entries with at least two complete pairs, their durations, months affected and intervals between starts.

Consecutive start/stop transitions form a pair. Duplicate starts, missing stops and periods crossing the edge of the imported history remain unpaired. Counts describe the imported event history, not a complete annual outage total. A gap in sensor readings alone is not labelled an offline event.

Thames Water says monitor reconfiguration, replacement or new installation can leave the map without earlier discharge records. Its status system also takes monitors offline for investigation. Operator explanation · Published incidents and changes.

Sampling is not publication

A 15-minute measurement interval does not promise a new file every 15 minutes. Our normal collector runs daily; historical imports also retrieve older batches.

SourceWhat arrivesPublication pattern
EA Flood MonitoringSensor readings and station metadataRegular updates, commonly 15 minutes; channel intervals can differ. API documentation
EA HydrologyHigh-frequency readings, daily statistics and manual measurementsTelemetry, daily updates and monthly archive releases coexist. Dipped groundwater can be much less frequent. EA publication schedule
EA Water Quality ExplorerLaboratory samplesSamples are analysed and checked before publication. Sample spacing is not a sensor reporting interval. Dataset description
EA bathing waterSamples and assessmentsSampling programmes and seasonal records; no continuous sensor heartbeat. Bathing-water profiles
Thames WaterMonitor snapshots and historical event transitionsThe two feeds have different identifiers and meanings. An event timestamp records a transition, not the last successful heartbeat.
Met Office / UK-AIRMinute weather records / hourly air observationsRecords can arrive in files or undergo later checking. A failed retrieval here is an acquisition problem until investigated.

Changes of service

10 MARCH 2026 · REGENT STREET CSO

Outfall removed from the map after being sealed

Thames Water records this removal and says the outfall was permanently sealed for the Tideway project and its permit surrendered. This is a documented physical change, distinct from an unexplained missing monitor. Operator change log.

2025 · SERVICE OUTAGES

Whole-map interruptions also recur

The same log records outages on 21–24 February and 8–10 March 2025, followed by another on 11 September. These affect the publishing service; they are not evidence that every sensor stopped measuring.

11 DECEMBER 2025 · WATER QUALITY ARCHIVE

Legacy API retired; data moved to a new service

The EA announced a replacement API with new endpoints and pagination. A downloader using the old interface could lose coverage even while sampling continued. This is a documented service migration; it is not evidence that the stations closed. EA migration notice, 27 November 2025.

Station details below include alternative feeds only where the publisher supplies an explicit link. A matching name or a nearby coordinate is not treated as proof of replacement. Reporting modes are shown for each entry and its linked feeds. These establish the first comparison point; a change of mode needs two dated definitions or an explicit publisher notice.

Our collection status

These are the latest recorded collection attempts, including historical batches. A successful batch does not mean the entire provider has been imported.

SourceLatest attemptData day requestedLast successful batch
Method, scope and limits

The month strip uses one named metric: the shortest declared sensor interval, then the most recent channel; sample-only stations use their newest metric. Green means at least one record is stored for that month. A pale cell means none is imported for that metric; it does not establish an upstream outage. The first and last dates cover all imported metrics at the station. Metadata-only entries remain visible.

“No archived readings in 30 days” is a fixed search aid, not an expected reporting deadline. Sampling, batching, seasonality, incomplete imports and source outages can all produce that result. Publisher status and the date we retained it are shown independently.

The archived first edition establishes a dated baseline. The imported outage log already shows repeated offline periods where start/stop evidence exists. Changes of identifier, reporting mode or sampling frequency need successive catalogue editions. The report does not establish a relationship between missing data and pollution publicity. That investigation needs dated changes, source explanations and a separate chronology of publicity.

Download current station catalogue (JSON) · Download the 25 September 2026 edition (JSON) · Units and references. This page reports the current archive; it is not a live monitor.

Contains Environment Agency information under the Open Government Licence; Thames Water data under CC BY 4.0; Met Office data under CC BY-SA 4.0, British Crown copyright; Defra UK-AIR under the Open Government Licence. Source records are selected and reformatted for this report.