InfraPulseThe Olympus engine · Discover & test

Test the path.
See the whole system.

InfraPulse actively probes your infrastructure — network & path latency, RTT, loss, and hop-by-hop routing, plus DNS, SIP, and service tests. Every result flows into the NKW, correlated with the real metrics, traces, and packets of the systems on both ends.

Path test · app-svc-01 → payment-gwRTT 42 ms
1edge-rtr-28 ms
2core-sw-114 ms
3fw-dmz-a31 ms
4payment-gw42 ms
fw-dmz-a CPU 94%retransmits ↑correlated to packets
What InfraPulse does

Don't wait for users to report it.

Actively tests

Active probes run continuously from the vantage points you choose — before real users feel a problem.

🛣️

Maps the path

Hop-by-hop latency, RTT, and loss show exactly where on the route delay or failure is introduced.

🔗

Correlates everything

Results join the NKW — tied to the CPU, memory, processes, apps, and packets of the systems involved.

The NIKSUN difference

An active test is only
half the story.

Standalone active-monitoring tools tell you a path is slow. They can't tell you why, because the test lives apart from your real infrastructure data. InfraPulse runs the same tests — then drops you straight into the correlated truth: the device that's pegged, the process that's hogging the link, the packets behind the loss.

  • Test result and the system state behind it, together
  • One lake — no stitching across separate tools
  • From a slow hop to the offending packet in one click
  • Internal and external vantage points
InfraPulse
LIVE
Active testDevicePackets
Active tests fused with device metrics & packets
PATH HEALTHms
1 min
Cadence
fused
With reality
⚠ hop 3 · latency
Test types

One engine, many probes.

Lead with network and path intelligence — and extend to the services your business runs on.

Network / path — latency · RTT · loss · hopsDNSSIP / VoIPHTTP / webTCP service& more
Agentic with Maya

Tests on demand —
or on Maya's initiative.

Ask Maya to run a path test to a struggling service and she'll launch InfraPulse, read the result against the rest of the lake, and tell you what's wrong. Wire it into Playbooks to test automatically when an alarm fires — and to verify the fix afterward.

You

Users say the payment page is slow — can you check the path?

M
Maya AIInfraPulse · 2.1s
Ran a path test to payment-gw. Hop fw-dmz-a added 17 ms — its CPU is at 94%, and I see matching retransmissions in the packets. Root cause is the firewall, not the app.
InfraPulseNPMObservability
Works across the platform

Pairs naturally with…

Know the Unknown

Test the path.
Know the cause.

See how InfraPulse turns an active test into a correlated, root-caused answer.