Availability
- What
- Dual WAN status, failover events, session continuity
- How
- MikroTik failover script + continuous uptime monitoring
- Why it matters
- You know when a failover occurred, how long it lasted, and whether sessions were maintained.
IJA Verify — Network Monitoring
We monitor from your side of the cable.
IJA Verify is the monitoring infrastructure that makes our SLAs contractual. Four pillars. Real data. Your dashboard.
Request a demo dashboardWhy monitoring direction matters
Most ISPs monitor from the wrong end.
The industry standard is to monitor from the NOC to the customer demarcation point. That tells the provider the last mile is up. It tells them nothing about what the customer actually experiences inside their building, through the backhaul, across peering, or at the actual internet.
IJA monitors from a Raspberry Pi installed at your premises — all the way to an AWS server in London. Every test crosses the last mile, the backhaul, the peering fabric, and reaches the real internet. Not a CDN. Not a local speed test server. The internet.
This is why we can sign SLAs. We know what you experience because we're testing from where you are.
The four pillars
What we measure. How we measure it. Why it matters.
Quality
- What
- Real-time latency, packet loss, jitter
- How
- PingPlotter running continuously on the Raspberry Pi at your premises
- Why it matters
- VoIP quality, video conferencing reliability, and application performance are all directly affected by quality metrics — not just bandwidth.
Capacity
- What
- True internet throughput — not local CDN performance
- How
- Scheduled iperf3 tests to an AWS server in London
- Why it matters
- A speedtest.net result measures performance to the nearest CDN node — often inside the same country. Our iperf3 tests measure real internet throughput as experienced by applications connecting to overseas servers.
Visibility
- What
- All telemetry surfaced in a customer-facing Grafana dashboard
- How
- Zabbix telemetry collection → Grafana dashboards → customer access
- Why it matters
- You see exactly what we see. The dashboard is not a summary report — it's live data, the same data our team monitors.
Infrastructure
The stack behind the SLA.
Raspberry Pi
At your premises
PingPlotter (quality)
iperf3 (capacity tests)
Zabbix
Telemetry collection
Aggregates all data
Alert thresholds
Grafana
Dashboard layer
Live dashboards
Historical data
Your login + IJA NOC
Shared visibility
Customer access
IJA monitoring
Telemetry flows from your premises → Zabbix collection → Grafana visualisation → shared access for you and IJA NOC
Supporting operations stack
Zabbix
Telemetry collection & alerting
Grafana
Dashboard & visualisation layer
Oxidized
Configuration versioning
Centralised syslog
System event aggregation
These tools run in IJA's infrastructure. They are not customer-facing — but they are what makes the customer-facing SLA possible.
“SLAs become contractual because we react as soon as our monitoring systems alert us — not when you call to complain.”
Ready to see real data from your premises?
Request a demo dashboard. Mention IJA Verify in the form and we'll walk you through a live deployment.
Request a demo dashboardTrust and Verify.
Every key account gets a dedicated account manager and access to their own Grafana dashboard. You see exactly what we see, in real time. That's not a promise — it's a login.
Start with a network audit