# network troubleshooting commands

A set of standard network commands used to diagnose connectivity and networking issues, including ping, traceroute, NSlookup, ARP, and related tools.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9

DevFeed: [The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9](<https://devfeed.tech/articles/the-ultimate-guide-to-analyzing-and-troubleshooting-critical-issues-on-red-hat-enterprise-linux-8-and-9-144332.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/11/19/ultimate-guide-to-troubleshooting-critical-issues-on-rhel-8-and-9>)

Author: Kailash Nailwal

Published: 2026-11-19T14:16:41Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [rhel](<https://devfeed.tech/topics/rhel.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [infrastructure monitoring](<https://devfeed.tech/topics/infrastructure-monitoring.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [SELinux](<https://devfeed.tech/topics/selinux.md>)

Tags: [blink](<https://devfeed.tech/tags/blink.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [business-operations](<https://devfeed.tech/tags/business-operations.md>), [core](<https://devfeed.tech/tags/core.md>), [critical](<https://devfeed.tech/tags/critical.md>), [devops](<https://devfeed.tech/tags/devops.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-linux](<https://devfeed.tech/tags/enterprise-linux.md>), [environment](<https://devfeed.tech/tags/environment.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hat](<https://devfeed.tech/tags/hat.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [observability](<https://devfeed.tech/tags/observability.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [red-hat-enterprise](<https://devfeed.tech/tags/red-hat-enterprise.md>), [red-hat-enterprise-linux](<https://devfeed.tech/tags/red-hat-enterprise-linux.md>), [troubleshooting](<https://devfeed.tech/tags/troubleshooting.md>)

### AI overview

The guide recommends disciplined, evidence-preserving triage for critical RHEL 8 and 9 outages: establish host identity and incident timing, then check CPU, memory, storage, services, networking, logs, security controls, time, resource limits, package history, and hardware for correlated symptoms. It gives commands and observables for each area, with cautions such as distinguishing load from CPU use, static swap from active paging, and ping reachability from application-port availability; it also warns against blind filesystem repairs or globally disabling SELinux. For crashes, it covers `kdump` and `coredumpctl`; for support, it recommends an incident-time `sosreport`, chronological context, logs, and relevant core dumps or SAR data. The text notes that enterprise deployments may need tailored procedures.

### Source excerpt

When a critical outage hits a production environment, time is your most crucial resource. Systems going down, unresponsive microservices, kernel panics, or sudden I/O bottlenecks can quickly jeopardize core business operations. For systems administrators, site reliability engineers (SRE), and DevOps teams managing enterprise workloads on Red Hat Enterprise Linux 8 or 9 (RHEL), having a disciplined and reproducible standard operating procedure (SOP) is what separates a blink from a catastrophe. The post The ultimate guide to analyzing and troubleshooting critical issues on Red Hat Enterprise Linux 8 and 9 appeared first on Red Hat Developer.

## 11 Networking Concepts Explained in 11 Minutes

DevFeed: [11 Networking Concepts Explained in 11 Minutes](<https://devfeed.tech/articles/11-networking-concepts-explained-in-11-minutes-97839.md>)

Original publisher: [Read original article](<https://newsletter.systemdesign.one/p/computer-networking-fundamentals-for-software-engineers>)

Author: Neo Kim

Published: 2026-10-23T16:06:14Z

Content type: article

Language: en

Sources: [System Design Newsletter](<https://devfeed.tech/sources/system-design-newsletter.md>)

Topics: [Ethernet](<https://devfeed.tech/topics/ethernet.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [MTU mismatch](<https://devfeed.tech/topics/mtu-mismatch.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [concepts](<https://devfeed.tech/tags/concepts.md>), [networking](<https://devfeed.tech/tags/networking.md>)

### AI overview

The excerpt explains how local and routed network communication works and how to investigate common connectivity issues. Ethernet carries IP packets in frames; switches learn MAC-to-port mappings and flood frames when a destination is unknown, while routers forward IP packets between networks. DHCP assigns leased addresses and settings such as the gateway and DNS servers; static addresses provide predictable assignments. Devices send remote traffic to a default gateway, and routers use static routes or OSPF to direct packets. Static routes require manual updates when paths change, while OSPF shares topology information and recalculates paths after failures, with convergence depending on detection, topology, and configuration. Wi-Fi performance varies with band, range, interference, signal quality, and retransmissions. ICMP reports errors and supports diagnostics but can be blocked or dropped and does not repair connections. Ping measures ICMP response time and missing replies; a successful ping does not establish that an application service is available. The excerpt recommends tools including `ip route`, `mtr`, `tcpdump`, and Wireshark for examining network behavior.

### Source excerpt

#195: Part 2 - Break Into Computer Networking

## Here's My Network Troubleshooting Toolbox

DevFeed: [Here's My Network Troubleshooting Toolbox](<https://devfeed.tech/articles/here-s-my-network-troubleshooting-toolbox-90793.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/network-troubleshooting-toolbox/>)

Author: Patrick Bacon

Published: 2026-10-20T12:00:47Z

Content type: article

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [dig command examples](<https://devfeed.tech/topics/dig-command-examples.md>), [network-intelligence](<https://devfeed.tech/topics/network-intelligence.md>)

Tags: [command](<https://devfeed.tech/tags/command.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [device](<https://devfeed.tech/tags/device.md>), [display](<https://devfeed.tech/tags/display.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-configuration](<https://devfeed.tech/tags/dns-configuration.md>), [dns-servers](<https://devfeed.tech/tags/dns-servers.md>), [domain-name](<https://devfeed.tech/tags/domain-name.md>), [expression](<https://devfeed.tech/tags/expression.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [network-troubleshooting](<https://devfeed.tech/tags/network-troubleshooting.md>), [network-troubleshooting-commands](<https://devfeed.tech/tags/network-troubleshooting-commands.md>), [networking](<https://devfeed.tech/tags/networking.md>), [wireguard](<https://devfeed.tech/tags/wireguard.md>)

### AI overview

The excerpt gives a practical network troubleshooting toolbox for macOS and Linux. Use `netstat -rn -f inet` on macOS or `ip -4 route` on Linux to inspect routes; `route -n get` or `ip route get` to check the route to a specific address; and `scutil --dns` or `resolvectl status` to inspect DNS configuration. For name resolution, `dscacheutil` and `resolvectl query` use the system's configured resolvers, while `dig @server` queries a chosen DNS server. It also shows `ifconfig` and `ip -4 addr` for interface addresses, `lsof` for processes using a port, and `tcpdump` with interface and packet filters to monitor traffic. The author notes these tools have more options than the examples cover.

### Source excerpt

As I mentioned in an earlier post, I've been experimenting a bit with WireGuard lately. In the process, I've been learning about a number of network troubleshooting commands, and before I forget what they all are and do, I'm going to capture them here so I (and you!) can find them again. Here's my network [...] The post Here's My Network Troubleshooting Toolbox appeared first on Atomic Spin.

## How to Test and Troubleshoot NFS Mount Connectivity on Linux

DevFeed: [How to Test and Troubleshoot NFS Mount Connectivity on Linux](<https://devfeed.tech/articles/how-to-test-and-troubleshoot-nfs-mount-connectivity-on-linux-66616.md>)

Original publisher: [Read original article](<https://blog.devops.dev/how-to-test-and-troubleshoot-nfs-mount-connectivity-on-linux-907c9bd2c7ef?source=rss----33f8b2d9a328---4>)

Author: Nirbhay Singh

Published: 2026-10-07T10:39:05Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [mount](<https://devfeed.tech/topics/mount.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>)

Tags: [connectivity](<https://devfeed.tech/tags/connectivity.md>), [developers](<https://devfeed.tech/tags/developers.md>), [devops](<https://devfeed.tech/tags/devops.md>), [file-system](<https://devfeed.tech/tags/file-system.md>), [for-system-administrators](<https://devfeed.tech/tags/for-system-administrators.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mount](<https://devfeed.tech/tags/mount.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [test](<https://devfeed.tech/tags/test.md>), [troubleshoot](<https://devfeed.tech/tags/troubleshoot.md>)

### AI overview

The guide begins NFS mount troubleshooting by checking network reachability before running NFS-specific commands. It identifies RPC Bind/Portmapper on port 111 and the NFS service on port 2049 as the primary ports to verify. The example uses separate UAT and production servers and export paths; the supplied excerpt does not include the actual connectivity commands or later troubleshooting steps.

### Source excerpt

Setting up Network File System (NFS) mounts is a routine task for system administrators and developers alike. However, when a mount fails... Continue reading on DevOps.dev "

## 7 Linux Commands Most People Discover Too Late in Their Home Lab

DevFeed: [7 Linux Commands Most People Discover Too Late in Their Home Lab](<https://devfeed.tech/articles/7-linux-commands-most-people-discover-too-late-in-their-home-lab-63519.md>)

Original publisher: [Read original article](<https://www.virtualizationhowto.com/2026/10/7-linux-commands-most-people-discover-too-late-in-their-home-lab/>)

Author: Brandon Lee

Published: 2026-10-01T12:29:01Z

Content type: tutorial

Language: en

Sources: [Virtualization Howto](<https://devfeed.tech/sources/virtualization-howto.md>)

Topics: [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [commands](<https://devfeed.tech/tags/commands.md>), [home-lab](<https://devfeed.tech/tags/home-lab.md>), [home-server](<https://devfeed.tech/tags/home-server.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-commands](<https://devfeed.tech/tags/linux-commands.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

The article explains seven Linux commands useful for troubleshooting home lab systems: ss, lsof, findmnt, journalctl, watch, ip route, and timeout. It gives examples for inspecting sockets, processes, filesystems, logs, changing system status, network routes, and limiting command runtime.

### Source excerpt

One of the primary learning exercises that I think can benefit most in the home lab is getting more familiar with Linux. Linux though, has a way of letting you... The post 7 Linux Commands Most People Discover Too Late in Their Home Lab appeared first on Virtualization Howto.

## Distributed Latency Monitoring at Black Hat

DevFeed: [Distributed Latency Monitoring at Black Hat](<https://devfeed.tech/articles/distributed-latency-monitoring-at-black-hat-8417.md>)

Original publisher: [Read original article](<https://blogs.cisco.com/security/bhusa-2026-te-latency/>)

Author: Adam Kilgore

Published: 2026-09-07T15:00:37Z

Content type: tutorial

Language: en

Sources: [Security @ Cisco](<https://devfeed.tech/sources/security-cisco-blogs.md>)

Topics: [ThousandEyes](<https://devfeed.tech/topics/thousandeyes.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [dig command examples](<https://devfeed.tech/topics/dig-command-examples.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [cURL](<https://devfeed.tech/topics/curl.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>)

Tags: [black-hat](<https://devfeed.tech/tags/black-hat.md>), [cisco-thousandeyes](<https://devfeed.tech/tags/cisco-thousandeyes.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [dns](<https://devfeed.tech/tags/dns.md>), [event](<https://devfeed.tech/tags/event.md>), [latency](<https://devfeed.tech/tags/latency.md>), [linux](<https://devfeed.tech/tags/linux.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [network-operations-center](<https://devfeed.tech/tags/network-operations-center.md>), [noc](<https://devfeed.tech/tags/noc.md>), [packet](<https://devfeed.tech/tags/packet.md>), [performance](<https://devfeed.tech/tags/performance.md>), [security](<https://devfeed.tech/tags/security.md>), [thousandeyes](<https://devfeed.tech/tags/thousandeyes.md>)

### AI overview

Black Hat's network team paired ThousandEyes dashboards and automated tests with on-demand Linux commands to monitor latency across conference rooms and troubleshoot protocol-specific problems. ThousandEyes covered HTTPS, cloud services, agent-to-agent paths, DNS, and downloads; curl broke HTTPS timing into DNS lookup, TCP connection, TLS handshake, time to first byte, and total time. Repeated curl runs can reuse cached DNS results, so the team used dig against a specified Umbrella DNS server for more consistent DNS query measurements. In one conference incident, high-volume DNS requests contributed to NAT exhaustion; protocol-specific tests and packet captures helped distinguish DNS failures from general latency or slow page loads. The article presents ThousandEyes for broad and targeted visibility, with curl and dig providing quick component-level checks.

### Source excerpt

Learn how the Black Hat NOC/SOC used ThousandEyes, Linux command-line testing, and packet evidence to monitor distributed latency, isolate DNS issues, and validate network performance during a live cybersecurity event.

## Introducing Networking Toolbox: Self-Hosted Network Tools in One Place

DevFeed: [Introducing Networking Toolbox: Self-Hosted Network Tools in One Place](<https://devfeed.tech/articles/introducing-networking-toolbox-self-hosted-network-tools-in-one-place-65793.md>)

Original publisher: [Read original article](<https://noted.lol/networking-toolbox/>)

Author: Jeremy

Published: 2025-10-19T12:27:34Z

Content type: article

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>), [Website](<https://devfeed.tech/topics/website.md>)

Tags: [dns](<https://devfeed.tech/tags/dns.md>), [http](<https://devfeed.tech/tags/http.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [self-hosted-web-tools](<https://devfeed.tech/tags/self-hosted-web-tools.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Networking Toolbox is a self-hosted web app that bundles more than a hundred network utilities, including DNS, IP, and HTTP/TLS diagnostics. It can run offline and be deployed with Docker or built from source, helping server operators and network troubleshooters avoid switching among tools.

### Source excerpt

Networking Toolbox is a self-hosted collection of 100+ network utilities that run offline, giving you quick access to IP, DNS, and HTTP tools in one simple web app.

## pyats\_ping\_tests

DevFeed: [pyats\_ping\_tests](<https://devfeed.tech/articles/pyats-ping-tests-66078.md>)

Original publisher: [Read original article](<https://github.com/automateyournetwork/pyats_ping_tests>)

Published: 2022-11-01T12:00:00Z

Content type: tutorial

Language: en

Sources: [Automate Your Network](<https://devfeed.tech/sources/automate-your-network.md>)

Topics: [Test automation](<https://devfeed.tech/topics/test-automation.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>)

Tags: [connectivity](<https://devfeed.tech/tags/connectivity.md>), [project](<https://devfeed.tech/tags/project.md>), [pyats](<https://devfeed.tech/tags/pyats.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

A starter kit for running pyATS connectivity tests. It gives setup and installation commands, instructions to clone and run the test job, and adjustable ping-count and response-time thresholds.

### Source excerpt

A connectivity test starter kit for pyATS

## Stupid Docker Tricks - Validating Outbound Connectivity from an Image

DevFeed: [Stupid Docker Tricks - Validating Outbound Connectivity from an Image](<https://devfeed.tech/articles/stupid-docker-tricks-validating-outbound-connectivity-from-an-image-28159.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/docker/2020/07/25/stupid-docker-tricks-validating-outbound-connectivity-from-an-image.html>)

Author: Fuzzygroup

Published: 2020-07-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [connectivity](<https://devfeed.tech/tags/connectivity.md>), [docker](<https://devfeed.tech/tags/docker.md>), [languages](<https://devfeed.tech/tags/languages.md>), [python](<https://devfeed.tech/tags/python.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [validating](<https://devfeed.tech/tags/validating.md>)

### AI overview

The excerpt shows how to check outbound connectivity from Ruby and Python Docker images with `docker run -it <image> ping google.com`; both `ruby:2.7.1` and `python:3.7.2` return ping replies, disproving the apparent Ruby-specific connectivity problem in this case. It explains that `-it` opens an interactive terminal and demonstrates starting `/bin/bash` in each image to check the language version and run a Hello World command. These examples illustrate using Docker images to test language versions; the excerpt does not establish broader connectivity behavior.

### Source excerpt

I recently had the odd situation where it seemed like I had outbound Internet connectivity issues under Ruby powered by Docker but not with Python powered by Docker. Here's how I disproved this: docker run -it ruby:2.7.1 ping google.com 64 bytes from ord30s26-in-f238.1e100.net (216.58.192.238): icmp_seq=1 ttl=37 time=15.2 ms 64 bytes from ord30s26-in-f238.1e100.net (216.58.192.238): icmp_seq=2 ttl=37 time=15.5 ms and docker run -it python:3.7.2 ping google.com 64 bytes from ord30s26-in-f238.1e100.net (216.58.192.238): icmp_seq=1 ttl=37 time=21.9 ms 64 bytes from ord30s26-in-f238.1e100.net (216.58.192.238): icmp_seq=2 ttl=37 time=31.3 ms The docker run command starts up an image. The -it option opens an interactive terminal underneath it and giving it a command like 'ping google.com' runs that in the terminal. One of the things that this Docker trick makes exceptionally easy is testing different versions of languages. Here's an example for Ruby: docker run -it ruby:2.7.1 /bin/bash root@4460a9daddff:/# ruby --version ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux] root@4460a9daddff:/# irb irb(main):001:0> puts "Hello World" Hello World => nil irb(main):002:0> And for Python: docker run -it python:3.7.2 /bin/bash root@3fe135f566bb:/# python --version Python 3.7.2 root@3fe135f566bb:/# python Python 3.7.2 (default, Mar 27 2019, 08:41:08) [GCC 6.3.0 20170516] on linux Type "help", "copyright", "credits" or "license" for more information. >>> print("Hello World") Hello World >>> Credit for this goes to my friend and Docker Guru / Docker Captain, Nick Janetakis. Nick teaches Docker online and I highly recommend his stuff.

## When You Can't Ping, You Dig

DevFeed: [When You Can't Ping, You Dig](<https://devfeed.tech/articles/when-you-can-t-ping-you-dig-28127.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/aws/2020/07/22/when-you-can-t-ping-you-dig.html>)

Author: Fuzzygroup

Published: 2020-07-22T00:00:00Z

Content type: article

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [dig command examples](<https://devfeed.tech/topics/dig-command-examples.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>)

Tags: [attacks](<https://devfeed.tech/tags/attacks.md>), [aws](<https://devfeed.tech/tags/aws.md>), [internet](<https://devfeed.tech/tags/internet.md>)

### AI overview

The excerpt distinguishes checking whether an Internet service is available from checking its address: ping is used for availability, while dig can look up the address for a hostname such as foo.bar.com. It notes that ping may be disabled because of ping-flooding attacks, mentioning AWS as an example. The suggested command is `dig foo.bar.com`; the excerpt does not claim this confirms that the service is up.

### Source excerpt

Normally when I'm trying to validate that an Internet service is available, well, I ping. Ping is one of those Internet bedrock protocols that I'm firmly in the camp of "SHOULD ALWAYS, ALWAYS, ALWAYS BE TURNED ON". But there are ping flooding attacks, etc so there are reasons why it isn't always a default (looking at you here AWS; staring you dead in the eyes with the 'ol stink eye). I recently realized that while it isn't example the same, if you're trying to validate something's address (as opposed to knowing if it is actually up), you can actually use dig. So instead of: ping foo.bar.com try: dig foo.bar.com

## The Web Performance Impact Of Lossy Network Conditions

DevFeed: [The Web Performance Impact Of Lossy Network Conditions](<https://devfeed.tech/articles/the-web-performance-impact-of-lossy-network-conditions-27974.md>)

Original publisher: [Read original article](<https://tech.trivago.com/post/2019-08-08-thewebperformanceimpactoflossynetworkcon/>)

Author: Tobias Baldauf

Published: 2019-08-08T00:00:00Z

Content type: article

Language: en

Sources: [Trivago](<https://devfeed.tech/sources/trivago.md>)

Topics: [Latency](<https://devfeed.tech/topics/latency.md>), [network device monitoring](<https://devfeed.tech/topics/network-device-monitoring.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [synthetic monitoring](<https://devfeed.tech/topics/synthetic-monitoring.md>), [Monitoring & Alerting](<https://devfeed.tech/topics/monitoring-alerting.md>), [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>), [Frontend observability](<https://devfeed.tech/topics/frontend-observability.md>), [Web](<https://devfeed.tech/topics/web.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>)

Tags: [alerting](<https://devfeed.tech/tags/alerting.md>), [api](<https://devfeed.tech/tags/api.md>), [arq](<https://devfeed.tech/tags/arq.md>), [automatic-repeat-request](<https://devfeed.tech/tags/automatic-repeat-request.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [bounce](<https://devfeed.tech/tags/bounce.md>), [business](<https://devfeed.tech/tags/business.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-regions](<https://devfeed.tech/tags/cloud-regions.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [dns](<https://devfeed.tech/tags/dns.md>), [extensions](<https://devfeed.tech/tags/extensions.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [network](<https://devfeed.tech/tags/network.md>), [performance](<https://devfeed.tech/tags/performance.md>), [servers](<https://devfeed.tech/tags/servers.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>), [web](<https://devfeed.tech/tags/web.md>), [web-performance](<https://devfeed.tech/tags/web-performance.md>)

### AI overview

During a cloud-service rollout, one region showed slower API responses, more user bounces, intermittent origin unreachability, and negative business metrics even though routine Synthetic and Real User Monitoring missed the outages. High-frequency object tests exposed intermittent failures; MTR tracing then found 10%-100% packet loss on middleware routers between the CDN and origin. The excerpt attributes slower responses to TCP retransmissions, while DNS and successful-connection "Connect" and "Receive" measurements appeared unaffected. Tests excluding failed connections still showed users waited about twice as long for responses, with "Wait" time rising by over 300 ms. The team worked with its CDN vendor to contact the responsible ISP, which did not respond, then mitigated the problem by routing CDN-to-origin traffic over IPv6, where tests found the unhealthy IPv4 hardware was not involved.

### Source excerpt

tl;dr: continuously monitor your CDN and origin servers on layer 3 with tools like MTR. Layer 3 issues on external middleware can have ...