Wagnific health probe
Uptime (last 1d): 100.000%
Operational
2026-07-26
today
Healthy · <5 min downtime · >5 min downtime · Not monitored yet
Response time
How this is calculated
Each bar is the total number of page requests in that time bucket, split by how fast they responded.Fast <100ms · Okay 100-500ms · Slow 500ms-2s · Very slow 2s+
Fast
The site responds almost instantly for typical page loads. (Today, 5,022 requests)
Fast <100ms 4,864 (96.9%)
Okay 100-500ms 158 (3.1%)
Slow 500ms-2s 0 (0%)
Very slow 2s+ 0 (0%)
HTTP status
How this is calculated
Response status codes from all page requests. 5xx = server error (bug or dependency down). 4xx = client / not-found / auth. Spikes indicate broken links or attacks. 5xx (server errors)
0
internal errors - should be zero
4xx (client errors)
0
404s, auth fails, bad requests
3xx (redirects)
0
usually login / normal redirects
2xx (success)
0
normal successful responses
Today · 0 responses
Order errors
How this is calculated
Success: unique successful orders (per orderId). Multiple orders from the same customer are counted separately.Declines: unique customer emails that attempted a payment but never had any successful order in the range. Not per-error - a customer with 100 retries counts once. If they eventually succeeded, they are not counted.
Categories:
• Card: gateway rejections (Do Not Honor, Insufficient Funds).
• 3DSecure: Stripe 3DS challenges that never returned.
• PayPal: PayPal handoffs where the user never returned (mixes real CoC declines like "Payer has not yet approved" with plain user abandonment).
7.41% decline rate
Today · 25 orders (14 card + 11 paypal)
· 25 paying customers · 2 declined customers (1 card + 1 3DS + 0 paypal)
Card orders 14
PayPal orders 11
Declined customers
latest reason per email
PHP errors
How this is calculated
All php_error events from the Wagnific runtime. Anything above zero deserves a look - each row is a bug or config drift that a real user hit. Total
0
clean window
Today
Abuse guard
How this is calculated
Requests blocked by rate-limits or bot checks. Steady low numbers are healthy - sudden spikes suggest attack traffic or a bot campaign. Rate-limit blocks
2
clients hitting request-per-window caps
Turnstile rejects
1
failed Cloudflare bot check
Today