All services / Narvar / Nov 5, 2026 / Evidence

Evidence

Evidence: Narvar, Nov 5, 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: Vendor-reported issue: only the company's status page flagged it; our checks and user reports did not confirm an outage. How we verify outages

Download JSON Download CSV Also at /api/v1/outages/886/evidence. Free to reuse with attribution.

0 of 251Checks failed in the window
0 of 4Regions failing
—Most common error code
0Peak user reports in 15 min

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

No failed checks with an error code in this window.

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: none recorded.

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 Narvar 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

251 checks, 0 failed.

All 251 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200368 ms—scheduled
Pass200169 ms—scheduled
Pass200535 ms—scheduled
Pass200796 ms—scheduled
Pass200824 ms—scheduled
Pass200381 ms—scheduled
Pass200254 ms—scheduled
Pass200405 ms—scheduled
Pass200421 ms—scheduled
Pass200239 ms—scheduled
Pass200599 ms—scheduled
Pass200417 ms—scheduled
Pass2001061 ms—scheduled
Pass200528 ms—scheduled
Pass200407 ms—scheduled
Pass200477 ms—scheduled
Pass2001339 ms—scheduled
Pass200641 ms—scheduled
Pass200412 ms—scheduled
Pass200738 ms—scheduled
Pass200536 ms—scheduled
Pass200312 ms—scheduled
Pass200291 ms—scheduled
Pass200409 ms—scheduled
Pass200355 ms—scheduled
Pass200673 ms—scheduled
Pass200222 ms—scheduled
Pass200460 ms—scheduled
Pass200586 ms—scheduled
Pass200311 ms—scheduled
Pass2001274 ms—scheduled
Pass200318 ms—scheduled
Pass200328 ms—scheduled
Pass200726 ms—scheduled
Pass200922 ms—scheduled
Pass200692 ms—scheduled
Pass200877 ms—scheduled
Pass200215 ms—scheduled
Pass200993 ms—scheduled
Pass200798 ms—scheduled
Pass200246 ms—scheduled
Pass200251 ms—scheduled
Pass200494 ms—scheduled
Pass200529 ms—scheduled
Pass200563 ms—scheduled
Pass200453 ms—scheduled
Pass200482 ms—scheduled
Pass200607 ms—scheduled
Pass200813 ms—scheduled
Pass200546 ms—scheduled
Pass200639 ms—scheduled
Pass2001241 ms—scheduled
Pass200533 ms—scheduled
Pass200593 ms—scheduled
Pass200295 ms—scheduled
Pass200291 ms—scheduled
Pass200552 ms—scheduled
Pass2001367 ms—scheduled
Pass200476 ms—scheduled
Pass200657 ms—scheduled
Pass200643 ms—scheduled
Pass200253 ms—scheduled
Pass200421 ms—scheduled
Pass200578 ms—scheduled
Pass200573 ms—scheduled
Pass200477 ms—scheduled
Pass200907 ms—scheduled
Pass200308 ms—scheduled
Pass2001211 ms—scheduled
Pass200359 ms—scheduled
Pass200227 ms—scheduled
Pass200453 ms—scheduled
Pass200805 ms—scheduled
Pass2001161 ms—scheduled
Pass200635 ms—scheduled
Pass200918 ms—scheduled
Pass200431 ms—scheduled
Pass200344 ms—scheduled
Pass200533 ms—scheduled
Pass200303 ms—scheduled
Pass200501 ms—scheduled
Pass200569 ms—scheduled
Pass200880 ms—scheduled
Pass200345 ms—scheduled
Pass200349 ms—scheduled
Pass200214 ms—scheduled
Pass200321 ms—scheduled
Pass200552 ms—scheduled
Pass200618 ms—scheduled
Pass2001112 ms—scheduled
Pass200540 ms—scheduled
Pass200623 ms—scheduled
Pass2001059 ms—scheduled
Pass200458 ms—scheduled
Pass200450 ms—scheduled
Pass200406 ms—scheduled
Pass200259 ms—scheduled
Pass2001188 ms—scheduled
Pass200577 ms—scheduled
Pass200511 ms—scheduled
Pass200346 ms—scheduled
Pass200741 ms—scheduled
Pass2001110 ms—scheduled
Pass200472 ms—scheduled
Pass200562 ms—scheduled
Pass200463 ms—scheduled
Pass200588 ms—scheduled
Pass200382 ms—scheduled
Pass200505 ms—scheduled
Pass200922 ms—scheduled
Pass200730 ms—scheduled
Pass200691 ms—scheduled
Pass200278 ms—scheduled
Pass200445 ms—scheduled
Pass200360 ms—scheduled
Pass200916 ms—scheduled
Pass200622 ms—scheduled
Pass200299 ms—scheduled
Pass200394 ms—scheduled
Pass200584 ms—scheduled
Pass200492 ms—scheduled
Pass200530 ms—scheduled
Pass200454 ms—scheduled
Pass200812 ms—scheduled
Pass200367 ms—scheduled
Pass200640 ms—scheduled
Pass200493 ms—scheduled
Pass200342 ms—scheduled
Pass200617 ms—scheduled
Pass200442 ms—scheduled
Pass200456 ms—scheduled
Pass200451 ms—scheduled
Pass200566 ms—scheduled
Pass200183 ms—scheduled
Pass200147 ms—scheduled
Pass200301 ms—scheduled
Pass200282 ms—scheduled
Pass200568 ms—scheduled
Pass200261 ms—scheduled
Pass200290 ms—scheduled
Pass200440 ms—scheduled
Pass200660 ms—scheduled
Pass200482 ms—scheduled
Pass200424 ms—scheduled
Pass200390 ms—scheduled
Pass200503 ms—scheduled
Pass200330 ms—scheduled
Pass200527 ms—scheduled
Pass200413 ms—scheduled
Pass200441 ms—scheduled
Pass200512 ms—scheduled
Pass200597 ms—scheduled
Pass200495 ms—scheduled
Pass200208 ms—scheduled
Pass200598 ms—scheduled
Pass200395 ms—scheduled
Pass200594 ms—scheduled
Pass200647 ms—scheduled
Pass200535 ms—scheduled
Pass200367 ms—scheduled
Pass200505 ms—scheduled
Pass200373 ms—scheduled
Pass200353 ms—scheduled
Pass200550 ms—scheduled
Pass200380 ms—scheduled
Pass200651 ms—scheduled
Pass200271 ms—scheduled
Pass200472 ms—scheduled
Pass200352 ms—scheduled
Pass200327 ms—scheduled
Pass200594 ms—scheduled
Pass200564 ms—scheduled
Pass200634 ms—scheduled
Pass200628 ms—scheduled
Pass200733 ms—scheduled
Pass200347 ms—scheduled
Pass200495 ms—scheduled
Pass200483 ms—scheduled
Pass200581 ms—scheduled
Pass200483 ms—scheduled
Pass200276 ms—scheduled
Pass200512 ms—scheduled
Pass200466 ms—scheduled
Pass200534 ms—scheduled
Pass200551 ms—scheduled
Pass200513 ms—scheduled
Pass200397 ms—scheduled
Pass200477 ms—scheduled
Pass200436 ms—scheduled
Pass200686 ms—scheduled
Pass200432 ms—scheduled
Pass200606 ms—scheduled
Pass200595 ms—scheduled
Pass200448 ms—scheduled
Pass200647 ms—scheduled
Pass200556 ms—scheduled
Pass200652 ms—scheduled
Pass200392 ms—scheduled
Pass200509 ms—scheduled
Pass200520 ms—scheduled
Pass200406 ms—scheduled
Pass200514 ms—scheduled
Pass200693 ms—scheduled
Pass200556 ms—scheduled
Pass200610 ms—scheduled
Pass200463 ms—scheduled
Pass200355 ms—scheduled
Pass200412 ms—scheduled
Pass200178 ms—scheduled
Pass200533 ms—scheduled
Pass200604 ms—scheduled
Pass200363 ms—scheduled
Pass200487 ms—scheduled
Pass200512 ms—scheduled
Pass200374 ms—scheduled
Pass200351 ms—scheduled
Pass200479 ms—scheduled
Pass200626 ms—scheduled
Pass200653 ms—scheduled
Pass200711 ms—scheduled
Pass200437 ms—scheduled
Pass200453 ms—scheduled
Pass200480 ms—scheduled
Pass200561 ms—scheduled
Pass200578 ms—scheduled
Pass200373 ms—scheduled
Pass200640 ms—scheduled
Pass200326 ms—scheduled
Pass200593 ms—scheduled
Pass200611 ms—scheduled
Pass200275 ms—scheduled
Pass200656 ms—scheduled
Pass200414 ms—scheduled
Pass200465 ms—scheduled
Pass200357 ms—scheduled
Pass200318 ms—scheduled
Pass200381 ms—scheduled
Pass200344 ms—scheduled
Pass200729 ms—scheduled
Pass200492 ms—scheduled
Pass200610 ms—scheduled
Pass200642 ms—scheduled
Pass200574 ms—scheduled
Pass200469 ms—scheduled
Pass200520 ms—scheduled
Pass200562 ms—scheduled
Pass200334 ms—scheduled
Pass200544 ms—scheduled
Pass200479 ms—scheduled
Pass200442 ms—scheduled
Pass200634 ms—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=886

No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.

← Back to the incident · Methodology · Dispute this report