Downloads of v


Last Update:

02 Aug 2020

Package Maintainer(s):

Software Author(s):

  • bp2008


ping traceroute

Ping Tracer | Updated: 02 Aug 2020



Downloads of v



Software Author(s):

  • bp2008

Ping Tracer

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Ping Tracer, run the following command from the command line or from PowerShell:


To upgrade Ping Tracer, run the following command from the command line or from PowerShell:


To uninstall Ping Tracer, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade pingtracer -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade pingtracer -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure pingtracer installed
    name: pingtracer
    state: present
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'pingtracer' do
  action    :install
  version  ''
  source   'STEP 3 URL'

See docs at

    Name: pingtracer,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller pingtracer
   Name     = 'pingtracer'
   Ensure   = 'Present'
   Version  = ''
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'pingtracer':
  provider => 'chocolatey',
  ensure   => '',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install pingtracer version="" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 31 Aug 2020.



This program helps to visually determine the origin of connection problems. The latency over time is shown on graphs, and each instance of packet loss is marked in red.

A common use for such a tool is to monitor your connection to a multiplayer game server so you know who to blame when you experience lag. For example, if you experience a terrible moment of lag and you see that every node beyond your router is showing elevated latency or packet loss, then the lag was on your end. Typically, a poorly performing node will affect your connection to every node after it.

I built this program for personal use, and decided to share it for free as an open source project. As such, it is light on features and polish.

Something you should be aware of is that when you attempt to "Graph every node leading to the destination", a trace route operation is performed in order to discover the hosts that will be monitored.

  • The trace route operation is not optimized for speed, and will take many seconds to complete in most cases.
  • The trace route operation attempts to contact each host (a.k.a. network node) only once. Any host that fails to respond during the trace route operation will not be monitored.
  • The trace route operation is ended if 5 consecutive hosts fail to respond. This usually indicates that the destination host was already passed by and did not respond to the trace ping.
  • Some hosts respond to the traceroute but do not respond to direct pings. Technically it would still be possible to monitor these hosts by repeating their part of the traceroute, but I assume this would be against the wishes of the owner of the host. If the owner wanted their router to be pingable, they would have enabled pinging, no?
  • I let you increase the ping rate as high as 10 pings per second (per host!) which can add up to dozens or even hundreds of pings per second. This is kind of, sort of, maybe a little bit excessive. I don't recommend actually running it that high. In fact 1 ping per second is probably all you need.


$ErrorActionPreference = 'Stop'

$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  unzipLocation  = "$toolsDir"
  packageName    = "pingtracer"
  file           = "$toolsDir/"
  checksum       = '292777976917364EA471BFED8CCDEF105761521DD90BDF0092D043B3856BFE04'
  checksumType   = 'sha256'

Write-Verbose "Unpacking"
Install-ChocolateyZipPackage @packageArgs

Write-Verbose "Searching for exe"
$files = get-childitem "$toolsdir" -include "*.exe" -recurse

# This will create a Shim for all exe and will add a line chocoUninstall.ps1 to remove it on uninstall
foreach ($file in $files) {
  Write-Verbose "Crating Start Menu enty for $($file.BaseName)"
  $newlink ="$($env:ProgramData)\Microsoft\Windows\Start Menu\Programs\$($file.BaseName).lnk"
  Install-ChocolateyShortcut -shortcutFilePath $newlink  -targetPath "$file"
  Add-Content "$toolsdir\chocoUninstall.ps1" -Value "Remove-Item `"$($newlink)`" -Force -ea ignore"

$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

. $toolsdir\chocoUninstall.ps1
md5: 70B7AF5A1493FA7593E8030F250E0F6A | sha1: CB878B322A4C4E3E39DDE96F3B370438927D9898 | sha256: 292777976917364EA471BFED8CCDEF105761521DD90BDF0092D043B3856BFE04 | sha512: 4720FF8D63BE22AD8B6AD9A6EF80DFCA9C496B8822E5EF8511CDBD0B7C843C552B5876322A69222EFF919DB4C1EF92308CE13BDDA50389E6F41296B7AD326388
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The binary can been downloaded using the official download link found at
This package has been built using Appveyor.
You can find the package source at
As well as the build logs at:

To verify the package you need to
1. Download the zip from the following
2. You can use one of the following methods to obtain the checksum
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  checksum type: sha256
  checksum32: 292777976917364EA471BFED8CCDEF105761521DD90BDF0092D043B3856BFE04

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Ping Tracer 1.8 101 Friday, July 3, 2020 Approved
Discussion for the Ping Tracer Package

Ground Rules:

  • This discussion is only about Ping Tracer and the Ping Tracer package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Ping Tracer, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus