Live Intelligence Feed
What Just Happened?
The complete real-time event log of your scan — every engine action, network change, API call, and security flag as it happens.
Understanding Every Signal
What each live feed metric tells you about this specific scan session.
Session Metadata
Backend Health
Reflects whether IntelReap's backend responded correctly during this scan. Healthy means all backend calls succeeded. Unhealthy means at least one failed — which typically results in missing geolocation enrichment, incomplete VPN detection data, or no AI summary for the affected canvas. When Backend Health is Unhealthy, the live feed's error count will show where the failures occurred.
Total Events, Critical Events & Warning Events
Total events is the complete count of all log lines generated during this session — every engine start, completion, API call, and status update combined. Critical events are high-severity findings: WebRTC leaks, VPN or TOR detection, failing security checks, major backend errors. Warning events are lower-severity signals that may still be worth investigating.
API Calls Made & Error Count
IntelReap makes two or three backend calls per full scan: IP identity, proxy intelligence, and optionally AI summary. More than three calls indicate a retry after a failed first attempt. Error count shows how many of those calls failed — a non-zero count here directly explains any missing data in the other panels.
Last Network Change & Scan Start Time
Last network change records if your connection switched during the session — Wi-Fi to mobile data, or a network reconnection. Scan start time anchors all the timestamps in the event log above, so you can read the log sequentially and understand how long each phase of the scan took relative to session start.
AI Summary Source & AI Last Updated
AI Summary Source shows which layer generated the AI Analysis text visible under each canvas — Groq (fast cloud LLM), Gemini (fallback LLM), or Script (the instant built-in generator that runs even when both LLM services are unavailable). AI Last Updated is the timestamp of the most recent AI generation, so you can tell whether the summaries are fresh to this session or carried over from an earlier one.
The Event Log Itself
Reading the log
Each event line shows a timestamp, a category tag (SYSTEM, NETWORK, SECURITY, API, SCORE, DEVICE, PERFORMANCE, VPN, AI), and a message. The colour of the category tag indicates severity: cyan for informational system events, amber for warnings, red for critical findings. The log streams in real time as the scan runs — on a fresh page load, watching it populate gives you a live view of the scan's six-phase execution sequence.
Phase sequence visible in the log
A complete scan runs six phases. Phase 1 runs all 13 engines in parallel. Phase 2 renders Canvas 1 and 2 as soon as IP data is ready. Phase 3 renders Canvas 3 and 13 as proxy and fingerprint data arrives. Phases 4 and 5 render the remaining canvases and generate AI summaries. Phase 6 calculates the global score and renders Canvas 11. This entire sequence, with timestamps, is visible in the live feed log.
Why a Transparent Scan Log Matters
Every conclusion has a traceable source
Most intelligence tools show you results without explaining how they got there. The live feed exists so that every flag, score, and summary in IntelReap's other 12 panels can be traced back to a specific logged event — you can see exactly when a security flag was raised, which API call returned which result, and how long each engine took to run. Nothing is a black box.