How to generate an MTR report

Edited

Overview

This article explains how to generate an MTR report to help troubleshoot live streaming connection and network routing problems.

Customer Support may request an MTR report to investigate the network route between your streaming location and a Lightcast ingestion point.


When to use this article

Use this article when Customer Support requests an MTR report to investigate:

  • Encoder connection errors

  • Frequent live stream disconnections

  • Buffering or unstable live streaming

  • Possible internet routing or network connectivity issues

  • Connection problems that continue after switching CDN Access Points or SRT Streaming URLs

Important: Run the report from the same network your encoder uses, preferably while the issue is occurring. If your encoder is a dedicated hardware device, use a computer connected to the same local network.


Before you begin

Before generating the report, identify the ingestion point your encoder is using.

  • For RTMP Ingestion: Use the hostname from the CDN Access Point.

  • For SRT Ingestion: Use the hostname from the SRT Streaming URL.

Do not include the full streaming URL, Stream Key, stream path, port, query string, or other private stream credentials as the MTR target. Use only the hostname.

For example, if your RTMP CDN Access Point looks like this:

rtmp://example.live.lightcast.com/in

Use only:

example.live.lightcast.com.

If your SRT Streaming URL looks like this:

srt://example-srt.live.lightcast.com:0000?streamid=example

Use only:

example-srt.live.lightcast.com.

Important: The examples above are placeholders. Always use the hostname from your own Channel's STREAM tab in the Media Cloud. Keep your stream credentials private and share them only with authorized members of your team or Customer Support when specifically requested.


How it works

An MTR report tests the network route between your location and a target hostname.

For live streaming troubleshooting, the target is usually the hostname from the CDN Access Point or SRT Streaming URL your encoder is trying to reach.

The report shows the network hops between your location and the target, along with statistics such as packet loss and response times.

Important: An MTR report helps identify potential network routing problems, but it does not directly test the RTMP or SRT streaming connection. Some networks also limit or block MTR probes, which can affect the results.

Customer Support will review the report alongside your encoder settings, streaming credentials, upload bandwidth, and other troubleshooting information to help identify the possible cause.


Instructions

Generate an MTR report on Windows

Step 1

Download and install WinMTR.

Extract the downloaded ZIP file and open the folder appropriate for your Windows system.

If your organization restricts software downloads or installation, ask your IT team for assistance.

Step 2

Open WinMTR.exe.

Step 3

In the Host field, enter the hostname you want to test.

Use only the hostname from the CDN Access Point or SRT Streaming URL. Do not enter the full streaming URL, Stream Key, stream path, port, or query string.

For example, enter example.live.lightcast.com or example-srt.live.lightcast.com.

Step 4

Click Start.

Step 5

Let the test run until at least 100 packets have been sent.

If the issue occurs intermittently, allow the test to run longer, preferably while the connection problem is happening.

You can monitor the number of packets sent in the Sent column.

Step 6

Click Stop.

Step 7

Click Export Text to save the report as a text file.

Step 8

Send the exported report to Customer Support.

Generate an MTR report on macOS

MTR is not typically included with macOS, so you may need to install it before generating a report.

The following instructions use Homebrew, a package manager for macOS.

Step 1

Open Terminal.

You can find Terminal under Applications → Utilities or search for it using Spotlight.

Step 2

Check whether Homebrew is installed by entering:

brew --version

Press Enter.

If Homebrew is installed, its version information will appear.

If Terminal reports that the command was not found, visit the official Homebrew website and follow its installation instructions.

If your organization restricts installing software or requires administrator approval, contact your IT team before proceeding.

Step 3

Once Homebrew is available, install MTR by entering:

brew install mtr

Press Enter and allow the installation to complete.

If MTR is already installed through Homebrew, you can skip this installation step.

Step 4

Enter the MTR command using the hostname you want to test.

Use this format:

sudo "$(brew --prefix)/sbin/mtr" -rwzbc 100 hostname > "$HOME/Desktop/mtr-report.txt"

Replace hostname with the hostname from your CDN Access Point or SRT Streaming URL.

For example:

sudo "$(brew --prefix)/sbin/mtr" -rwzbc 100 example.live.lightcast.com > "$HOME/Desktop/mtr-report.txt"

Do not enter the full streaming URL, Stream Key, stream path, port, or query string.

Step 5

Press Enter to run the command.

If prompted, enter your Mac administrator password and press Enter again.

Your password will not appear on the screen as you type.

Step 6

Wait for the command to finish collecting the report.

The command runs 100 test cycles and saves the results as a text file named mtr-report.txt on your Desktop.

Step 7

Locate mtr-report.txt on your Desktop and send the file to Customer Support.


What if you cannot generate an MTR report?

If you cannot download or run WinMTR or MTR, or your organization restricts network diagnostic tools, contact your IT team or Customer Support.

Customer Support may recommend an alternative network test to help investigate the connection problem.


What to send to Customer Support

When submitting an MTR report, please include:

  • Your exported MTR report

  • Channel name or Channel ID

  • The hostname tested

  • Whether you are using RTMP or SRT Ingestion

  • Date and approximate time of the issue, including your time zone

  • A brief description of the problem and whether it occurred during the test

Do not include Stream Keys, passwords, or other private credentials in your report.


FAQs

Can I use traceroute instead of MTR?

MTR is preferred because it collects network route and packet-loss information over time.

If you cannot install or run MTR, contact Customer Support for an alternative.


What if my MTR report shows packet loss?

Packet loss at an intermediate network hop does not always indicate a connection problem. Some routers limit or deprioritize MTR responses.

Customer Support will review the complete report to determine whether the results suggest an actual network issue.


Does an MTR report confirm whether Lightcast is experiencing an outage?

No. An MTR report provides information about the network route between your location and a Lightcast ingestion point.

It does not independently confirm whether a Lightcast service is operational.


Additional related resources

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.