// article
Guide to Checking All Internet Connections in One Place
How to monitor and troubleshoot all your internet connections from a single view: covering speed tests, ping diagnostics, traceroutes, network monitoring tools, and common connectivity fixes.
Guide to Checking All Internet Connections in One Place
Your office has a fiber connection for primary internet, a cable backup for failover, and a point-to-point link connecting the satellite office across town. When something goes wrong (slow VoIP calls, laggy cloud apps, a branch office that can’t reach headquarters), you need to figure out which connection is the problem without checking each one separately.
Centralized network monitoring gives you one dashboard showing the health of every connection your business depends on. Instead of running speed tests on each line and comparing results manually, you see bandwidth, latency, and uptime for all connections at a glance.
Here’s how to set that up and use it to keep your network healthy.
Why Centralized Monitoring Matters
Most businesses rely on more than one internet connection without realizing how much complexity that creates for troubleshooting.
Typical multi-connection setups:
- Primary fiber or cable internet for the main office
- Backup connection (different ISP or technology) for failover
- Point-to-point link between office locations
- Mobile hotspot or LTE backup for emergency connectivity
- Wi-Fi networks for employees and guests (running on the same underlying connections)
When a user reports “the internet is slow,” which connection is the problem? Is it the primary line, the backup that kicked in because the primary failed silently, the point-to-point link to the other office, or just congestion on the guest Wi-Fi network?
Centralized monitoring answers that question in seconds instead of the 30-60 minutes it takes to check each connection manually.
Start With Physical Inspection
Before running any diagnostic software, check the physical layer. A surprising number of network problems trace back to hardware you can see and touch.
Physical inspection checklist:
- Ethernet cables: Look for damage, kinks, and loose connectors. A cable that “mostly works” can cause intermittent packet loss that’s hard to diagnose from software alone.
- Connectors: Ensure every cable clicks firmly into its port. A connector that’s 90% seated can work fine until someone bumps the desk.
- Power supplies: Verify modems, routers, and switches are plugged into surge-protected outlets and powered on with normal indicator lights.
- Wireless equipment: Check antenna positioning and ensure nothing new has been placed in front of access points (filing cabinets, whiteboards, monitors).
Physical inspection takes 10 minutes and eliminates the most common (and most frustrating) category of network issues.
Speed Tests: Measuring What Each Connection Delivers
A speed test measures download speed, upload speed, and latency on a specific connection. Run tests on each of your internet connections to establish baselines and detect degradation.
How to test effectively:
- Test during peak hours (mid-morning, early afternoon) when your network is under real load, not at 6 AM when the office is empty
- Test each connection separately by connecting directly to that line’s modem or router
- Compare against your plan: If your fiber plan promises 500 Mbps and you’re getting 150 Mbps, something is wrong
- Test both upload and download: VoIP and video conferencing depend heavily on upload speed, which is often the bottleneck
Key benchmarks:
- Download speed within 80% of your plan’s advertised rate
- Upload speed matching the plan (especially important for symmetrical fiber)
- Latency under 20ms for fiber, under 50ms for cable
For businesses running VoIP, consistent upload speed matters more than peak download speed. Business internet services designed for voice traffic prioritize the stability and symmetrical speeds that VoIP requires.
Ping Tests: Detecting Latency and Packet Loss
A ping test sends small data packets to a destination and measures how long they take to return. It reveals two critical metrics: latency (how fast packets travel) and packet loss (how many never arrive).
What ping results tell you:
- Consistent low latency (under 30ms to your VoIP provider): Connection is healthy
- Latency spikes at certain times: Network congestion during peak hours
- Steady high latency: Possible ISP routing issue or distance problem
- Packet loss above 0%: Connection instability that will affect VoIP and video quality
Run extended ping tests (30-60 minutes) to catch intermittent issues that a quick 10-ping test would miss. This is especially useful for diagnosing “sometimes the calls are fine, sometimes they’re not” problems.
Traceroutes: Finding Where Problems Happen
When ping tests confirm a problem but don’t show the cause, a traceroute maps the path your data takes and shows latency at each hop along the route.
How to read traceroute results:
- First few hops: Your local network (router, switches). High latency here means an internal problem.
- Middle hops: Your ISP’s network. High latency or packet loss here is your ISP’s responsibility.
- Later hops: The broader internet between your ISP and your destination. Problems here may require your ISP to adjust routing.
Traceroute data is valuable when contacting your ISP about performance issues; it shows exactly where the problem is occurring, which speeds up resolution.
Network Monitoring Software: The Full Picture
Manual tests work for troubleshooting specific incidents. For ongoing visibility across all connections, network monitoring software tracks performance continuously and alerts you when something degrades.
What monitoring software provides:
- Real-time dashboards showing bandwidth usage, latency, and uptime for every connection
- Automated alerts when a connection drops, latency spikes, or bandwidth usage hits a threshold
- Historical data showing trends over days, weeks, and months, useful for planning upgrades
- Device-level visibility showing which devices are consuming the most bandwidth
Monitoring options by business size:
- Small offices (under 20 people): Router-built-in monitoring or free tools like PRTG (limited sensors) provide basic visibility
- Mid-size offices (20-100 people): Dedicated monitoring platforms that track multiple connections, VLANs, and devices
- Multi-location businesses: Centralized monitoring across all sites with alerting for location-specific issues
When paired with business telephone services, network monitoring ensures your VoIP system gets priority bandwidth and alerts you before call quality degrades.
Troubleshooting Common Connection Issues
Slow speeds on one connection
Check: Speed test against plan specs, cable integrity, router/modem health. Common fix: Restart the modem, check for firmware updates, contact ISP if speeds are consistently below plan.
Intermittent connectivity
Check: Extended ping test for packet loss, physical cable inspection, Wi-Fi interference. Common fix: Replace suspect cables, move to wired connection for critical devices, update router firmware.
One location can’t reach another
Check: Point-to-point link status, traceroute between locations, VPN tunnel status. Common fix: Restart point-to-point equipment, verify VPN configuration, check if ISP maintenance is affecting routing.
VoIP quality issues on specific connections
Check: Bandwidth usage during call times, QoS configuration, jitter and latency metrics. Common fix: Enable or reconfigure QoS to prioritize voice traffic, separate VoIP onto its own VLAN, upgrade connection if bandwidth is saturated.
1stConnect provides unified communication tools that include monitoring features, helping you identify whether call quality issues originate from your network or further upstream.
Connection Types and What to Monitor for Each
| Connection Type | Key Metrics to Watch | Common Issues |
|---|---|---|
| Fiber | Latency, uptime, symmetrical speeds | Provider outages, equipment failure |
| Cable | Peak-hour speeds, upload bandwidth | Shared bandwidth congestion, asymmetric speeds |
| DSL | Speed consistency, latency | Distance from exchange, line quality |
| Point-to-Point | Latency, packet loss, signal strength | Weather interference, alignment drift |
| LTE/5G Backup | Signal strength, latency, data caps | Coverage gaps, throttling after data limits |
Monitor each connection type for its specific vulnerabilities rather than applying the same tests uniformly.
FAQs
How often should I check my internet connections?
Automated monitoring should run continuously with alerts for issues. Manual speed tests and physical inspections should happen monthly, or immediately when users report problems.
What’s the most common cause of slow internet at a business?
Bandwidth saturation during peak hours: too many devices and applications competing for the same connection. QoS configuration and connection upgrades are the typical solutions.
Do I need different monitoring for each type of connection?
The same monitoring tools work across connection types, but you should set different alert thresholds. Fiber should maintain under 10ms latency, while LTE backup might acceptably run at 30-50ms.
How do I know when it’s time to upgrade my internet connection?
When your peak-hour usage regularly exceeds 70% of available bandwidth, when VoIP or video quality degrades during busy periods, or when speed tests consistently show performance below your plan’s specs after troubleshooting.
Can I monitor connections at multiple office locations from one place?
Yes. Cloud-based monitoring platforms let you track all locations from a single dashboard. This is especially valuable for businesses with branch offices connected by point-to-point links or VPN tunnels.
Ready to get full visibility into your network? Start with reliable business internet services, pair them with business telephone services that depend on that connectivity, and keep everything connected with 1stConnect.