Three outage days can look like a month of lost visibility
All 738 failed attempts in the fixed August panel occurred on 13, 20 and 28 August.
- Published
- 2026-09-02
- Revised
- 2026-09-02
- Author
- Cleotic Research
- Method
- comparison-v1.1
failed August attempts
Denominator: 16,864 fixed-panel attempts
contained every panel failure
Denominator: 13, 20 and 28 August
failures outside those dates
Denominator: 15,232 fixed-panel attempts
Three dates account for every panel failure
738 failed attempts were concentrated on 13, 20 and 28 August. Excluding the same day numbers from both months leaves 15,232 August attempts and no failures in the four-model panel.
United Kingdom / August 2026 / Denominator: 16,864 scheduled attempts across the fixed four-model panel / Method: comparison-v1.1
View chart data as a table
| Date | Attempts | Successful | Failed | Failure rate |
|---|---|---|---|---|
| 2026-08-01 | 544 | 544 | 0 | 0.0% |
| 2026-08-02 | 544 | 544 | 0 | 0.0% |
| 2026-08-03 | 544 | 544 | 0 | 0.0% |
| 2026-08-04 | 544 | 544 | 0 | 0.0% |
| 2026-08-05 | 544 | 544 | 0 | 0.0% |
| 2026-08-06 | 544 | 544 | 0 | 0.0% |
| 2026-08-07 | 544 | 544 | 0 | 0.0% |
| 2026-08-08 | 544 | 544 | 0 | 0.0% |
| 2026-08-09 | 544 | 544 | 0 | 0.0% |
| 2026-08-10 | 544 | 544 | 0 | 0.0% |
| 2026-08-11 | 544 | 544 | 0 | 0.0% |
| 2026-08-12 | 544 | 544 | 0 | 0.0% |
| 2026-08-13 | 544 | 164 | 380 | 69.9% |
| 2026-08-14 | 544 | 544 | 0 | 0.0% |
| 2026-08-15 | 544 | 544 | 0 | 0.0% |
| 2026-08-16 | 544 | 544 | 0 | 0.0% |
| 2026-08-17 | 544 | 544 | 0 | 0.0% |
| 2026-08-18 | 544 | 544 | 0 | 0.0% |
| 2026-08-19 | 544 | 544 | 0 | 0.0% |
| 2026-08-20 | 544 | 296 | 248 | 45.6% |
| 2026-08-21 | 544 | 544 | 0 | 0.0% |
| 2026-08-22 | 544 | 544 | 0 | 0.0% |
| 2026-08-23 | 544 | 544 | 0 | 0.0% |
| 2026-08-24 | 544 | 544 | 0 | 0.0% |
| 2026-08-25 | 544 | 544 | 0 | 0.0% |
| 2026-08-26 | 544 | 544 | 0 | 0.0% |
| 2026-08-27 | 544 | 544 | 0 | 0.0% |
| 2026-08-28 | 544 | 434 | 110 | 20.2% |
| 2026-08-29 | 544 | 544 | 0 | 0.0% |
| 2026-08-30 | 544 | 544 | 0 | 0.0% |
| 2026-08-31 | 544 | 544 | 0 | 0.0% |
The monthly rate hid an incident pattern
The fixed four-model panel recorded 738 failures in August. The failure rate reached 69.9% on 13 August, 45.6% on 20 August and 20.2% on 28 August. Every other day in that panel completed without a failed request.
Removing the same day numbers from July and August leaves 15,232 August attempts, no failures and only 3 attempts without captured text. The primary content findings keep the same direction in that sensitivity view.
Reliability belongs in the visibility report
If missing answers are treated as brand absences, an outage becomes a false visibility decline. If failed attempts are silently removed, the report hides where its evidence is weaker. The remedy is to publish collection success and usable-answer yield beside the content measures.
A matched-day sensitivity is useful when an incident is concentrated on known dates. It does not reconstruct the missing answers, but it tests whether the conclusion depends on the affected collection window.
What marketers should do
- 01Separate failed collection, empty successful responses and genuine no-brand answers.
- 02Show daily or run-level reliability beside monthly visibility.
- 03Use a matched-day sensitivity when incidents cluster on specific dates.
- 04Never impute a failed answer as either visible or absent.