A reachability test tells you a customer’s link is down. PacketPulse tells you how badly, and from where — loss, jitter and voice quality from the server and from the engineer’s own device — and files the evidence against the trouble ticket, ready to attach.
STATUS SITE PACKETS MOS UP Mumbai POP Sent = 4, Received = 4, Lost = 0 4.37 UP Pune edge Sent = 4, Received = 4, Lost = 0 4.31 UP Pune edge · IPv6 Sent = 4, Received = 4, Lost = 0 4.29 DEGRADED Nagpur POP Sent = 4, Received = 4, Lost = 0 3.72 DOWN Branch router (Aurangabad) Sent = 4, Received = 0, Lost = 4 — PATH TO branch-aur.example.net (10.255.255.1) 1 10.130.235.66 0% loss 3.3 ms 2 106.208.189.193 0% loss 14.5 ms 3 117.96.31.62 0% loss 26.1 ms 4 203.0.113.9 67% loss 88.4 ms ← loss starts here 5 * 100% loss —
An engineer enters a Customer ID and a TT number. PacketPulse does the rest and keeps the result against the ticket — for the next engineer, and for the customer who asks what happened.
Latency, jitter and packet loss per endpoint, and a Mean Opinion Score estimating how a voice call would sound over that path.
A PDF carrying the Customer ID, the TT number and every packet count, ready to attach to the ticket — and the same results as CSV for your own systems.
Everything below is in the product today. Nothing here is a roadmap item.
Packet loss and RFC 3550 jitter on every result, ticket and report, and an ITU-T G.107 Mean Opinion Score banded Excellent to Poor — the language your customer already uses when they say a call sounded bad.
Recurring sweeps with availability percentages per site, and email or webhook alerts the moment an SLA target is breached. On-demand testing becomes continuous watch.
A PDF carrying the Customer ID, the TT number, UTC timestamps and every packet count — attachable to the ticket, and readable by a customer who was not in the room. The same results export as CSV in one click.
Staff sign in with existing network credentials over LDAP or Active Directory, and their directory group decides their PacketPulse role. A break-glass local account stays available to the owner.
A password and then a one-time code: emailed to the person’s sign-in address, or texted through your own SMS gateway for the people you choose. An owner’s code is always emailed, and an administrator signs out a lost phone in one step.
A site that has both is measured on both. The IPv6 result is shown and kept but not counted against the site, so a dark IPv6 path is found without changing anyone’s SLA figure.
Every result as CSV: downloaded from a ticket, pulled with an API key, or delivered on a schedule to your own SFTP or FTPS server, with the server’s key confirmed before anything is sent.
When field engineers sign in and out, where their device was — position, address and a map link — on a Check-ins list of its own. Make sharing it a condition of signing in if you need to.
Every unreachable endpoint reports exactly what was sent and what came back — the line a ticket needs, not a summary of it.
What PacketPulse records is meant to be relied on afterwards, so it is built to be checkable rather than merely stored.
Every change is hash-chained to the one before it. Altering or removing a historical entry breaks every entry after it, and the verifier names exactly where.
Every administrator’s sign-in and sign-out — device, browser, address and where they were — and every refused attempt on their account, with why. Refused changes leave no entry: the trail records what happened.
Authority is read fresh on every request. Changing someone’s role signs them out immediately rather than waiting for a session to expire.