All services / Armazem Cloud / Nov 12, 2026 / Evidence
Evidence: Armazem Cloud, Nov 12, 2026
The raw data behind this incident page: every check we ran, the regions that failed, the error codes and the user report curve. Check our work.
Our verdict: Possible problem, not a confirmed outage: it did not meet our evidence bar. How we verify outages
Download JSON Download CSV Also at /api/v1/outages/1224/evidence. Free to reuse with attribution.
Window: to . Checks from 15 minutes before the start to 15 minutes after recovery (or now). Report curve: one hour either side. Tables are in UTC.
Error codes
| Error code | Failed checks |
|---|---|
http_530 | 4 |
Passing checks with a note (counted as up, not as failures): bot_challenge ×2.
http_5xx = the site answered with that server error; timeout = no answer in time; network = the connection failed; origin_reset = the connection to the site's server was reset (HTTP 520–527) and a second fetch path got no answer either; no_status = no usable answer. Bot walls (bot_*), certificate problems on a server that answers (cert_*) and maintenance pages count as up.
Regions
- We check from: US East, US West, Europe, Asia-Pacific.
- Failing during this incident: Europe, US West.
- : Failing from Europe, US West.
Regional probes run from Cloudflare data centers in each region. We keep the latest regional result per region, plus a timestamped timeline entry when a region starts failing during an incident, so older incidents show the failing regions and when each was first seen, not every regional probe.
Report curve
No user reports for Armazem Cloud in this window.
User reports per 15-minute bucket. Counts only: no reporter identity, IP address, location or text is published. We call reports a spike at 5 or more in 15 minutes.
Raw checks
6 checks, 4 failed (first , last ).
Failed checks
| Check time (UTC) | Probe ran (UTC) | Result | HTTP | Latency | Error code | Trigger |
|---|---|---|---|---|---|---|
| Fail | 530 | 6145 ms | http_530 | scheduled | ||
| Fail | 530 | 6015 ms | http_530 | on demand | ||
| Fail | 530 | 6125 ms | http_530 | scheduled | ||
| Fail | 530 | 4127 ms | http_530 | scheduled |
All 6 checks, passes included
| Check time (UTC) | Probe ran (UTC) | Result | HTTP | Latency | Error code | Trigger |
|---|---|---|---|---|---|---|
| Fail | 530 | 6145 ms | http_530 | scheduled | ||
| Fail | 530 | 6015 ms | http_530 | on demand | ||
| Pass | 403 | 2232 ms | bot_challenge | on demand | ||
| Fail | 530 | 6125 ms | http_530 | scheduled | ||
| Pass | 403 | 2750 ms | bot_challenge | scheduled | ||
| Fail | 530 | 4127 ms | http_530 | scheduled |
Every main HTTP check of this service in the window, oldest first: the scheduled check time, when the probe actually ran, the result, HTTP status, latency and the stored error code. A failed check is a 5xx or 408 answer, a timeout or a failed connection; bot walls and maintenance pages count as passing and are noted in passing_notes.
How to check this
- Compare checks.rows with the outage page: the first and last failed checks bound the incident times we published.
- error_codes counts every failed check by its stored code; recount it from checks.rows.
- report_curve.points sum to summary.reports_in_curve; the peak is summary.peak_reports_15m.
- Disagree? Dispute it at https://damnisitdown.com/support?dispute=1224
No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.