Method

Observed,
not guessed.

Quospark is a public website availability observation ledger. It records what the current Quospark probe can resolve and reach, then preserves meaningful state changes.

What a check does

A check normalizes a public hostname, resolves DNS, rejects private and reserved destinations, tries HTTPS then HTTP when needed, follows up to five safe redirects, records the HTTP response and measures time until response headers begin.

What “response” means

The displayed millisecond value is HTTP response start time from the Quospark probe, not full page-load performance. HTTP 401, 403 and 429 still prove that an endpoint responded, so they are not classified as outages.

How outages are confirmed

A first network failure triggers short delayed retries. An Observed Outage is recorded only after at least two failed logical attempts. DNS and destination safety are revalidated on redirects and requests are pinned to vetted resolved addresses.

What Quospark does not claim

Quospark v1.1 uses one probe location. It does not say a site is “down for everyone,” does not diagnose a root cause, and does not turn a server response into speculation.

Indexing

One-off checks receive permanent URLs but are not automatically eligible for search indexing. Monitored hosts become indexable only after a minimum observation history is collected.