[ PROTOCOL // PUBLIC ]
SMMMeter observes technical reachability and response time. This is the complete public logic behind the signal—what we request, how often, and where it can be wrong.
Every visible panel listed on CompareSMM enters the monitor automatically. Removing a panel from the public directory disables future checks.
One due website measurement per panel per hour. A scheduler runs every ten minutes and claims at most 30 overdue panels per run, preventing large bursts.
HEAD requestThe API signal comes from CompareSMM's existing daily service-catalog synchronization. SMMMeter records its duration and outcome instead of creating a second synthetic API request.
The primary website region advances after each measurement. A panel is therefore sampled from each region over successive hours—not hit from all six regions every hour.
HTTP 200–399 / 405OPERATIONALThe endpoint answered normally or rejected only the HEAD method.
401 / 403 / 407 / 429 / 451RESTRICTEDThe site answered, but access from that route was restricted or rate-limited.
OTHER HTTP 400–499DEGRADEDThe web server responded with a client-facing error.
HTTP 500+ / NETWORK ERRORUNAVAILABLE*A second-region confirmation is required before an incident opens.
PROXY CONTROL FAILEDINCONCLUSIVEThe measurement route could not validate itself, so the panel is not blamed.
A scheduled regional probe reports unavailable.
For network errors, the proxy must first reach an independent control endpoint.
Only another unavailable result confirms and opens the incident.
Recovery is recorded when a later conclusive website response is operational, restricted, or degraded. API incidents require consecutive failed daily sync measurements, so API confirmation is intentionally slower.
Individual request results support recent logs, investigations, and detailed charts.
Compact regional availability and latency aggregates preserve long-term trends.
Embeddable SVG status is cached and supports conditional ETag requests.
Live pages use short shared caches; the static methodology uses a 24-hour cache.
Public views read cached stored measurements; viewing a page never probes a panel.
The affiliate redirect increments one panel-level counter. SMMMeter does not store a click IP, user agent, or referrer.
01 A successful HEAD response does not prove that every browser page, checkout, payment method, or downstream provider works.
02 Proxy routing, geoblocking, bot protection, maintenance, and transient network conditions can affect measurements.
03 Hourly sampling can miss short incidents. Region rotation means regional comparisons cover different moments in time.
04 API measurements reflect the daily catalog request, not order placement, refill, cancellation, or balance operations.
05 Technical availability is not a review, security audit, endorsement, or guarantee of panel quality.
06 SMMMeter is independently operated. Panel links may be affiliate links; commissions and outbound click counts do not change status calculations or ordering.