RESTOCKWIRE / TIMING DESK
Three clocks behind
a stock alert.
A five-second checking target is only one part of the story. This evidence ledger separates how often source checks finish, how old the inventory observations are on RestockWire, and when a notification reaches a phone.
Which number answers your question?
Median time between completed checks in the shared source sample.
Measured · 30-minute sampleMedian age of the latest source-check timestamps in RestockWire’s inventory snapshot.
Measured · one snapshotTime from a real stock change to an alert appearing on a recipient’s device.
Not measured in this reportThese values have different denominators. A low inventory age is not a fast delivery measurement, and a fast source sample is not proof that a newly added member watch has the same coverage. We keep those distinctions visible so a useful measurement does not become an unsupported promise.
How often did source checks finish?
From 22:00 to 22:30 UTC on November 7, the shared source observation contained 103,636 recorded store-check completions across 368 anonymous store series. The median gap was 6.099 seconds; the 95th percentile was 7.923 seconds and the longest gap was 13.548 seconds.
The intended five-second interval and the measured result are different. Only 0.07% of this sample’s gaps were at most five seconds. This does not support calling five seconds a strict upper bound.
| Completion gap | Recorded intervals | Percentage |
|---|---|---|
| ≤ 5 seconds | 75 | 0.07% |
| > 5–6 seconds | 39,044 | 37.81% |
| > 6–7 seconds | 49,308 | 47.75% |
| > 7–10 seconds | 14,304 | 13.85% |
| > 10 seconds | 537 | 0.52% |
There were four unsuccessful checks, retained in the timing sample. A completed unsuccessful check contributes an interval but does not establish a fresh stock observation. The first completion of each series has no earlier in-window value and contributes no interval.
This source measurement is shared with PickupChecker’s report. It is not a second independent experiment or a RestockWire member-target benchmark. We publish the source scope because it explains the evidence available, not to imply a result for every subscription.
How fresh was the inventory visible to this service?
At , we read the latest recorded source-check timestamps in RestockWire’s inventory records. All 18,680 store–configuration rows had a timestamp less than sixty seconds old.
- Stores represented by inventory rows
- 467
- Median source-observation age
- 5.486 s
- 95th-percentile age
- 15.899 s
- Oldest observation
- 18.461 s
- Rows missing a check timestamp
- 0
Age means “snapshot time minus the last source-check timestamp.” It is not a measured transfer delay or the gap between two checks. This snapshot contains 467 stores with inventory records; that denominator should not be substituted for a regional store catalog count.
The reading includes ordinary inventory records, not just priority member targets. A one-time freshness snapshot can show that records were recent at that moment, but it cannot establish that they stayed that fresh all day or that a notification was delivered.
Download this timing receipt (JSON) ↗What would justify a stronger speed claim?
A RestockWire-specific claim needs a verified link between eligible member selections and the actual checks made for those selections. That verification is incomplete as of this report. Until it is established, do not read our five-second target as a proven result for a newly created RestockWire-only watch.
A phone-delivery claim would need a separate measurement from a defined stock-change observation to confirmed display on a real device. This report contains neither that test nor a competitor comparison. We therefore make no “fastest tracker,” five-second delivery or guaranteed-purchase claim from these numbers.
What this receipt establishes
- A dated source-check sample with the full interval distribution.
- A separate snapshot of source-observation ages in RestockWire inventory.
- A visible boundary around the member-target and delivery claims that remain unverified.
The source interval summary counts one logged completion per store-check cycle and compares consecutive completions within each anonymous series. Failed checks are retained; unlogged or incomplete activity cannot be reconstructed. Median and nearest-rank 95th percentile are computed over the recorded gaps. The inventory-age statistics use the timestamped rows present in the separate snapshot.
All measurements were produced by the publisher. They are not a third-party certification. Public evidence omits identities, customer choices and operational implementation details. Any later improvement requires a new dated receipt; this one should remain quoted with its original window.
Questions to ask about any stock-alert speed claim
Does a five-second check mean an alert arrives in five seconds?
No. A check interval, the age of its observation and the eventual phone delivery are separate quantities. Our figures above do not time phone delivery.
Does a recent inventory timestamp mean my exact watch is covered?
It demonstrates the age of that inventory record, not the eligibility or coverage of a particular watch. RestockWire-specific member-target verification is incomplete in this report.
Why use a shared source measurement at all?
It is real evidence about the source inventory observations. It becomes misleading only if presented as an independent site-specific or end-to-end test. This ledger explicitly keeps those scopes separate.
What should I do when I see stock?
Open the current Apple checkout for the precise configuration and confirm a pickup option. A tracker cannot reserve stock, and an observation does not mean the phone will remain available.
Look up current Duo stock · Understand alert delays · Request a correction
Reference: RestockWire, “Three clocks behind a stock alert,” November 7, 2026. Source window: 22:00–22:30 UTC; inventory-age snapshot: 22:33:57 UTC. Member-target and phone-delivery verification incomplete.