How It Works
Submit telemetry config, receive a pre-outage signal brief, engage a partner, resolve.
Process
Join the platform
Create an account and connect your network telemetry sources—SNMP, NetFlow, or API-accessible device stats from your existing management stack.
Receive signal briefs
OutageClockIQ processes your telemetry and delivers periodic signal briefs identifying pre-outage degradation patterns specific to your topology.
Review indicators
Each signal brief includes a tier classification, confidence interval, and recommended action items mapped to your infrastructure.
Engage implementation partners
Connect with vetted operators who have verified field experience in your region and network architecture type for follow-on diagnostics or remediation.
Resolve and iterate
Track signal outcomes over time and refine your telemetry configuration to improve relevance as network conditions evolve.
FAQ
What telemetry does OutageClockIQ read?
OutageClockIQ integrates with SNMP polling (v2c/v3), NetFlow/sFlow exports, and REST APIs exposed by common network management platforms. It does **not** require proprietary agents or network hardware replacements. If your management stack exposes standard network telemetry, the integration path is direct. Operators on platforms such as RouterOS, UBNT EdgeOS, and Cambium cnMaestro have documented successful integrations.
How is signal confidence measured?
Each signal brief includes a confidence score (0–100) derived from telemetry consistency, historical pattern match, and time-on-tool. Confidence is bounded by telemetry granularity—intervals of 60 seconds or tighter yield meaningfully higher signal fidelity. Briefs flagged as low-confidence are clearly labeled and can be excluded from automated alerting until tuned.
What happens to my network data?
Telemetry data is processed in transient compute environments and is **not** retained beyond the brief generation window. Metadata (device counts, topology labels you provide) may be stored to enable account functionality. No customer traffic content is processed. Data isolation follows a per-tenant model aligned with standard SaaS isolation practices.
How are implementation partners vetted?
Partners in the curated network undergo a structured onboarding that includes: (1) verification of relevant ISP/WISP experience via project history and peer reference, (2) technical capability assessment for the degraded signal class identified, and (3) agreement to contract terms that protect both parties. Partner tiers are labeled by experience depth so you can select accordingly.
What if the signals are inaccurate or generate false positives?
Signal accuracy improves with telemetry quality—providers with sparse polling intervals (5+ minutes) and minimal baseline history will see lower precision. OutageClockIQ surfaces the contributing telemetry sources for each signal so you can diagnose false-positive root causes. A tuning guide is available in the documentation for operators migrating from reactive monitoring workflows.
Can I use OutageClockIQ without engaging a partner?
Yes. Signal briefs are fully readable without partner engagement, and recommended action items are provided in plain operational language. Engaging a partner is an optional next step if internal NOC capability or field presence is constrained. The platform does not require partner engagement as a gateway to receiving briefs.