Overview

Many industrial connectivity problems aren’t about hardware failure — they are about not knowing what’s happening on the network. Packet loss, signal fluctuation, carrier handovers, DNS timeouts, routing loops and asymmetric paths are more common than most engineers expect.

To help diagnose these issues, the Network Map feature in Teltonika’s RUTOS provides an intuitive visualisation of a router’s network path, hops, DNS resolution and latency. It is a diagnostic tool that shows how a router “sees” the external network, and can help reveal issues that simple ping tests or signal bars do not.

This article explains what Network Map is, why it exists, how it works, how to interpret it, and how it can improve your deployment outcomes.

What Is the Network Map Feature?

The Network Map feature is a network diagnostic visualisation within RUTOS that shows:

• how the router’s data packets travel from the local device to a target (e.g., cloud service)
• the sequence of intermediary hops (routers/transit points)
• response time (latency) per hop
• packet loss and route asymmetry
• DNS resolution behaviour

Unlike a simple ‘ping’, Network Map combines route discovery (like traceroute) with real-time status information, and displays it in a user-friendly format on the router’s web UI.

Why Network Map Matters

Industrial networks are different from consumer networks:

• high uptime is expected
• unpredictable RF environments complicate diagnostics
• services may be remote or behind load-balanced networks
• router logs alone don’t show path issues
• traditional tools are not practical for onsite diagnostics

Network Map helps you answer questions such as:

• Is DNS resolving correctly?
• Are requests being routed through unexpected carriers or VPNs?
• Is packet loss happening near the router or further upstream?
• Are delays occurring in the first hop or towards the service endpoint?

For industrial IoT, where downtime equals lost revenue or compliance breaches, this level of insight is deeply actionable.

How Network Map Works (High-Level)

Network Map combines three diagnostics patterns:

1. Name resolution (DNS test)
It resolves hostnames to IP before mapping — showing early if DNS is failing.

2. Path discovery (traceroute-style hops)
It uses incremental TTLs (time-to-live) to discover each router along the path.

3. Latency measurement (ping-style timing)
At each hop, it measures the round-trip time.

The result is similar to an enhanced traceroute combined with DNS checks and timing — but presented visually and with real-time refresh.

Where to Find Network Map in RUTOS

Within the RUTOS UI:

1. Log in to the router’s web interface
2. Navigate to Network → Diagnostics → Network Map (path may vary slightly by RUTOS version)
3. Enter a target hostname or IP (e.g., your cloud endpoint)
4. Run the test and review the map output

You can run this test at any time without interrupting normal WAN connectivity.

Interpreting a Network Map

A typical Network Map output includes:

Hops:
Each intermediate router or network point through which packets travel.

Response Time (Latency):
Measured at each hop — higher values indicate delay.

DNS Status:
Shows whether the domain resolved successfully before mapping began.

Colour-coded Status:
Different colours or indicators often mark timeouts, unreachable hops, or loss.

What Good Looks Like

• DNS resolves immediately
• First hop (local carrier gateway) responds consistently
• Steady, incremental latency increases
• No packet loss until the far end

This suggests a healthy data path.

What Bad Looks Like

• DNS fails to resolve — indicates DNS or APN issue
• First or second hop shows high packet loss — suggests local carrier issues
• Large latency spikes early — poor signal or cell congestion
• Route asymmetry — carrier or network load balancing causing instability

These patterns help you diagnose problems faster than trial-and-error.

When Network Map Helps Most

Network Map is useful in contexts such as:

• New deployment testing
• Before and after antenna or SIM swaps
• Intermittent connectivity issues
• Carrier routing changes
• VPN tunnel path verification
• Performance degradation checks

It is not a replacement for long-term monitoring systems but is excellent for quick, repeatable diagnostics.

Common Misinterpretations to Avoid

1. “High latency at the last hop means bad connectivity.”
Not always — cloud services sometimes prioritise traffic differently. Look at pattern, not absolute numbers.

2. “If Network Map shows a missing hop, the router is broken.”
Some network devices intentionally do not respond at certain hops but still forward traffic.

3. “Only the first hop matters.”
It matters a lot, but if later hops show consistent loss or huge variability, the problem may be distant network or peering issues.

Pairing Network Map With Other Diagnostics

Network Map is strongest when combined with:

• Signal metrics (RSRP/SINR etc.) — to correlate RF performance
• Ping plots over time — for stability trends
• APN routing checks — to confirm carrier path
• VPN path checks — to ensure tunnels are behaving

This combination gives a 360° view of connectivity health.

When Network Map Alone Isn’t Enough

Network Map does not:

• Replace long-term uptime monitoring
• Diagnose application-level errors (e.g., MQTT disconnects)
• Provide performance under load
• Show cellular bearer aggregation behaviour

For those, you need remote monitoring platforms or RMS-like long-term telemetry.

Conclusion: Why This Matters for Industrial IoT

Industrial networks aren’t simple. Static signal bars and download tests don’t tell you about:

• DNS resolution failures
• Asymmetric routing
• Inefficient path choices
• Cell-to-carrier handoff behaviour
• VPN tunnel reconnection patterns

Network Map gives visibility into these — making it a powerful diagnostic tool.

For engineers working on remote, hard-to-access assets, Network Map reduces guesswork and helps diagnose the true root cause of connectivity issues.

‍