Internet troubleshooting: fix slow or unstable connections

How do I troubleshoot my internet connection?

Start by checking whether the problem affects one device or every device connected to your network. This simple comparison helps separate device-specific faults from problems involving your router, modem or internet provider.

Follow these steps in order:

1. Check another device. Connect a second phone, laptop or computer to the same network. If the second device works, investigate the original device first.
2. Check your network connection. Confirm that Wi-Fi is enabled, Airplane Mode is disabled and the device is connected to the correct network.
3. Inspect your modem and router. Check their power connections, Ethernet cables and status indicators. Follow the equipment manufacturer's instructions for interpreting the lights.
4. Check for an ISP outage. Use your provider's service-status page or contact its support team.
5. Restart your network equipment. Follow the manufacturer's restart procedure. A normal restart does not have the same effect as a factory reset.
6. Test the connection again. Open a website, run a speed test or compare a wired connection with Wi-Fi.
7. Investigate the affected layer. If the problem remains, use the diagnostic tests below instead of repeatedly restarting equipment.

Microsoft Support recommends testing the same network with another device to help determine whether a connection problem is specific to one computer. (Microsoft Support)

Quick distinction

• One device fails: begin with that device's network settings.
• Every device fails: inspect shared equipment and the ISP connection.
• Wi-Fi fails but Ethernet works: investigate the wireless network.
• Both Wi-Fi and Ethernet fail: investigate the router, modem and upstream service.

Key point: Do not factory-reset your router as the first troubleshooting step. Identify the affected device or connection layer before changing network settings.

Why is my internet so slow?

Slow internet can result from weak Wi-Fi, network congestion, a limited broadband connection, faulty Ethernet equipment or an issue with the ISP. First determine whether the slowdown affects Wi-Fi only or also affects wired devices.

For a deeper walkthrough of common causes, see why is my internet so slow?

Check whether your download or upload speed is slow

Download speed measures how quickly your device receives data. Upload speed measures how quickly your device sends data. Both are commonly expressed in megabits per second (Mbps). Read more in what Mbps means.

Run a speed test and compare the result with your internet plan. Use the same device and test server when comparing measurements. Google explains that speed-test results can differ because tests use different servers and network paths. (Google Nest Help)

If download speed is low but upload speed is normal, investigate the download path and network usage. If both are low across several devices, check the router, modem and ISP service.

Check Wi-Fi signal strength and interference

Wi-Fi performance depends on the distance between a device and its access point, physical obstructions, frequency band and radio interference.

Try these checks:

• Move closer to the router and repeat the test.
• Place the router in an open, central location.
• Check whether walls, floors or large objects obstruct the wireless signal.
• Compare the 2.4 GHz and 5 GHz networks if your router and device support both.
• Check whether nearby wireless networks or electronic devices are interfering.

Google identifies distance, building materials, frequency bands and nearby wireless activity as factors that affect Wi-Fi performance. (Google Nest Help)

Check whether connected devices are using your bandwidth

Multiple devices share the available network capacity. Video streaming, large downloads, cloud backups and online games can compete for bandwidth.

Pause large downloads and temporarily disconnect devices that are not needed. Run the speed test again to see whether performance changes.

Test your internet speed over Ethernet

Connect a computer directly to the router using an Ethernet cable. Run the same speed test and compare the result with your Wi-Fi measurement.

Google documents a product-specific example in which a 100 Mbps or lower Ethernet link can limit the performance of Nest Wifi and Google Wifi equipment. Its guidance also recommends checking cable and upstream equipment ratings. These figures describe that equipment's diagnostic criteria, not a universal rule for every router. (Google Nest Help)

Key tip: A speed test measures throughput to a particular test endpoint. It does not independently explain latency, jitter, packet loss or every application's performance.

For a deeper explanation, read what Mbps means, how internet speed tests work and latency vs bandwidth.

Why does my internet keep disconnecting?

An internet connection that repeatedly drops can indicate a Wi-Fi problem, an unstable cable connection, a device fault or an interruption from your ISP. First check whether the Wi-Fi connection itself disappears or whether devices stay connected to Wi-Fi but lose internet access.

Check whether Wi-Fi or the entire internet connection drops

Watch the network icon on your device when the interruption happens.

• If the device disconnects from the Wi-Fi network, investigate the wireless signal, router or network adapter.
• If the device stays connected to Wi-Fi but websites stop loading, investigate the router's internet connection, DNS and ISP service.
• If wired and wireless devices lose access together, investigate shared network equipment or the provider connection.

This distinction prevents you from changing Wi-Fi settings when the actual fault is upstream.

Inspect your router, modem and Ethernet cables

Check that the power adapters and network cables are firmly connected. Look for loose plugs, damaged cable jackets or connectors that move easily inside their ports.

If your modem connects to a separate router, inspect the Ethernet cable between those devices. A damaged cable or unstable port can interrupt the connection even when the Wi-Fi signal remains strong.

Check Wi-Fi interference and router placement

Move the affected device closer to the router and repeat the connection test. If the connection becomes stable nearby, investigate distance, obstructions, interference or the placement of mesh Wi-Fi points.

Google's troubleshooting guidance identifies physical barriers, nearby wireless networks and other radio sources as possible contributors to poor Wi-Fi performance. (Google Nest Help)

Update the affected device or router when necessary

If the problem began after an operating-system update, investigate the network adapter driver. If the router shows recurring faults, check the manufacturer's firmware guidance.

Do not uninstall a network driver without first checking that you have a way to reinstall it. Microsoft recommends keeping a backup driver available before removing a network adapter driver. (Microsoft Support)

Record when the connection disconnects

For recurring interruptions, keep a short log:

This record gives your ISP specific evidence to investigate instead of a general report that the internet keeps disconnecting.

Key fact: A router that remains powered on does not prove that its internet connection is working. Check the device's connection status and the router's provider-facing connection separately.

Why am I connected to Wi-Fi but have no internet?

A device can connect to a Wi-Fi router without reaching the internet. Wi-Fi establishes a local wireless connection; the router must also have a working connection to the ISP for devices to access online services.

Understand the difference between Wi-Fi and internet access

Your home network has several connection stages:

1. Your phone or computer connects to the router over Wi-Fi or Ethernet.
2. The router provides local network access and routes traffic toward the internet.
3. The modem or gateway connects to the ISP's network.
4. The ISP provides a route to external internet services.

A failure at any later stage can leave a device connected to Wi-Fi but unable to browse websites. Apple Support makes this distinction in its guidance for Macs that connect to Wi-Fi but cannot access websites, email or other internet services. (Apple Support)

Check your device's IP address and default gateway

An IP address identifies a device interface on an IP network. A default gateway is the local router address that a device uses to send traffic outside its local network.

On Windows:

1. Open Command Prompt.
2. Type ipconfig and press Enter.
3. Find the active Wi-Fi or Ethernet adapter.
4. Locate the Default Gateway entry.
5. Check whether an IP address and gateway are listed.

If the device has no usable network configuration, DHCP or the device's network settings may need investigation. DHCP is the protocol that provides network configuration information to hosts. The IETF describes it in RFC 2131, published in March 1997. (IETF RFC 2131)

Check whether DNS is preventing websites from loading

DNS, or the Domain Name System, translates domain names into information such as IP addresses. A DNS problem can prevent a browser from locating a website even when other network communication works.

The IETF's RFC 1034, published in November 1987, describes the concepts and facilities behind DNS. (IETF RFC 1034)

If an IP-based test works but a domain name does not resolve, investigate DNS before changing unrelated Wi-Fi settings. You can also use the site's DNS lookup tool.

Restart your router and reconnect your device

If several devices show the same problem, restart your network equipment according to its manufacturer or ISP instructions. If only one device is affected, forget the saved Wi-Fi network and reconnect using the correct password.

Apple's Mac troubleshooting guidance also recommends checking VPN or security software, router firmware, network diagnostics and ISP service when Wi-Fi connects but internet access fails. (Apple Support)

Key point: The message “Connected” describes the device's connection to a network. It does not guarantee that the router has a working internet connection.

How do I know if my router or ISP is causing the problem?

Compare multiple devices and test both Wi-Fi and Ethernet to narrow down the fault. A problem affecting every device does not automatically prove an ISP outage because the router or modem can also affect the whole network.

Check whether all devices have the same problem

Connect a second device to the same network and test a website.

• If the second device works, investigate the original device.
• If both devices fail, investigate shared equipment and the ISP connection.
• If only devices connected to one Wi-Fi band fail, investigate the wireless configuration.

Microsoft recommends trying the same Wi-Fi network on another device to help identify device-specific problems. (Microsoft Support)

Compare Wi-Fi with a wired Ethernet connection

Connect a computer to the router using Ethernet and repeat the same test.

A wired test helps isolate wireless problems, but it does not identify every possible fault by itself.

Check your modem and router status

Look at the status indicators on your equipment and compare them with the manufacturer's documentation. The meaning of each light differs between models, so do not assume that a green indicator always confirms full internet access.

If you use a separate modem and router, check the connection between them. If your ISP supplies a combined gateway, use the provider's instructions to inspect its service status.

Check your ISP's outage information

Use your provider's official outage checker, app or support channel. If the ISP confirms an outage, repeated router resets and DNS changes will not repair the provider's network.

Google's Nest Wifi troubleshooting documentation distinguishes slow ISP service, local network congestion, modem issues and Ethernet limitations as separate possible causes. (Google Nest Help)

When does a direct modem test help?

A direct computer-to-modem test can help isolate a router fault when the modem and ISP setup support that connection method. Some providers require specific authentication, device registration or gateway configuration, so check the ISP's instructions first.

Do not bypass provider equipment or change service settings if you do not know how to restore the original configuration.

Key tip: If Ethernet works but Wi-Fi does not, focus on the wireless network before replacing the modem or contacting the ISP about a broadband outage.

How do I test my internet connection?

Use a speed test to measure throughput, ping to check IP reachability, and a DNS lookup to investigate domain-name resolution. These tests measure different parts of a connection, so interpret their results together.

Run an internet speed test

Start with a speed test to measure download and upload performance. For a useful comparison:

1. Connect your device to the network you want to investigate.
2. Pause large downloads and other high-bandwidth activity.
3. Run the test and record download speed, upload speed and latency if shown.
4. Repeat the test using Ethernet if available.
5. Compare results across devices or at different times.

A speed test measures performance to its selected test server. Google explains that server location and network congestion can change the result. (Google Nest Help)

Example interpretation

• Low download speed: investigate network load, Wi-Fi conditions and the ISP plan or service.
• Low upload speed: investigate upstream service, device activity and network conditions.
• High latency: investigate the route, congestion and distance to the test server.
• Different results between Wi-Fi and Ethernet: investigate the wireless or wired connection separately.

Ping your router's default gateway

Ping sends diagnostic messages to test whether an IP destination responds. The Internet Control Message Protocol (ICMP) provides the message functions used by traditional ping tests. The IETF specified ICMP in RFC 792, published in September 1981. (IETF RFC 792)

On Windows:

1. Open Command Prompt.
2. Type ipconfig.
3. Find the Default Gateway for your active connection.
4. Type ping followed by that gateway address.

Example:

ping 192.168.1.1

Replace the example address with the actual default gateway shown on your device.

If the router replies, the device can communicate with the gateway using ICMP. If the router does not reply, check the local connection, gateway address and device settings.

Microsoft documents this gateway-ping procedure in its Windows Wi-Fi troubleshooting guidance. (Microsoft Support)

Test an external IP address

You can also ping a known external IP address to investigate reachability beyond your local router.

ping 1.1.1.1

A response indicates that the destination returned ICMP replies through the tested network path. A lack of replies does not automatically prove that the internet is unavailable because networks and destinations can filter ICMP traffic.

Check whether DNS can resolve a website

On Windows, use nslookup followed by a domain name:

nslookup example.com

The command asks a DNS resolver to look up the domain. If the lookup fails, check the DNS server and network configuration. If it succeeds, the result confirms name resolution for that query, not that the website itself is available.

DNS is defined in the IETF's RFC 1034 and its companion specifications. (IETF RFC 1034)

Understand latency, packet loss and jitter

These measurements describe different aspects of network performance:

A ping test does not measure download speed. A speed test does not identify every cause of latency or packet loss. TCP, specified in the IETF's RFC 9293 (August 2022), is a transport protocol used by many internet applications, but successful ICMP replies do not prove that every TCP-based service works. (IETF RFC 9293)

Key fact: Use the same test destination and similar network conditions when comparing results. A single measurement is not a complete diagnosis.

For further performance testing, use the internet speed test, the ping test, the packet loss test and how speed tests work.

How do I fix internet problems on one device?

If other devices can access the internet through the same network, troubleshoot the affected device before changing router settings. Check its Wi-Fi connection, network adapter, IP configuration, VPN and firewall.

Forget and reconnect to the Wi-Fi network

A saved wireless profile can contain settings that prevent a device from reconnecting correctly.

On Windows:

1. Open Settings.
2. Select Network & internet, then Wi-Fi.
3. Open Manage known networks.
4. Select the affected network and choose Forget.
5. Reconnect and enter the correct Wi-Fi password.

Microsoft includes forgetting and reconnecting to a Wi-Fi network in its Windows troubleshooting steps. (Microsoft Support)

Check the network adapter and its driver

A network adapter is the hardware or virtual interface that connects a device to a network. A faulty or outdated driver can affect that connection.

On Windows, open Device Manager and expand Network adapters. Check whether the affected adapter shows an error. If the problem started after a driver update, consult the computer manufacturer's instructions for restoring or reinstalling the correct driver.

Microsoft advises users to keep a driver backup before uninstalling a network adapter driver. (Microsoft Support)

Check VPN and firewall settings

A VPN routes traffic through another network endpoint. Security software and firewalls can also filter network traffic. These tools can affect internet access even when the device connects successfully to Wi-Fi.

Temporarily disconnect a VPN to test whether the connection changes. Do not permanently disable firewall or antivirus protection. If the connection works only when security software is disabled, review its settings or contact its provider.

Apple specifically identifies VPN and other security software as possible causes of Mac internet connection problems. (Apple Support)

Renew the device's network configuration

DHCP assigns network configuration to devices. Renewing a DHCP lease requests updated configuration from the network's DHCP server.

On a Mac, restarting the computer can renew its assigned internet address. Apple also documents manual IP address renewal and recommends checking the router, VPN software and built-in diagnostics. (Apple Support)

On Windows, an advanced user can run these commands in Command Prompt:

ipconfig /release
ipconfig /renew
ipconfig /flushdns

These commands release and request an IP configuration and clear the local DNS resolver cache. Run them only when the device's configuration or DNS resolution is part of the problem.

Microsoft documents these commands as part of its Windows network troubleshooting procedure. (Microsoft Support)

Use built-in diagnostics when the problem continues

Mac users can open Wireless Diagnostics by holding the Option key while selecting the Wi-Fi menu, then choosing Open Wireless Diagnostics. The tool analyses the wireless environment and provides detected issues and possible solutions. It does not change network settings. (Apple Support)

Windows users can start with the built-in network troubleshooter and the adapter status in Settings.

Key tip: Use device-level resets only after simpler checks. Microsoft describes Windows Network reset as a last troubleshooting step because it removes installed network adapters and restores their settings to defaults. It can also require VPN or virtual networking software to be reinstalled. (Microsoft Support)

How do I identify where my internet connection is failing?

Use a sequence of tests to narrow the problem from the device to the local router, external network, DNS and application. This process is called fault isolation: identifying the part of a system responsible for a problem by comparing test results.

The five-layer connection check

1. Device. Check whether one device or multiple devices are affected.
2. Local connection. Compare Wi-Fi with Ethernet and test communication with the default gateway.
3. Router and ISP. Inspect router status, modem connection and provider outage information.
4. IP and DNS. Test external IP reachability and domain-name resolution.
5. Application. Check whether the browser or affected application can connect to its service.

What do different test results mean?

These outcomes guide the next test; they do not prove a single cause. ICMP replies can be filtered, and a website can fail even when a device can reach an external IP address.

What if an IP address works but a website does not?

Test DNS resolution with nslookup or the DNS lookup tool. If the domain resolves, check the browser, application and destination service. If the domain does not resolve, investigate the configured DNS resolver and device network settings.

Application traffic uses more than basic IP reachability. TCP, for example, provides transport-layer communication used by many internet applications. The IETF's RFC 9293 specifies TCP and was published in August 2022. (IETF RFC 9293)

What should you record when internet problems keep returning?

Create a short fault log before contacting your provider:

• Exact date and time of the interruption.
• Whether one device or all devices were affected.
• Whether Wi-Fi, Ethernet or both failed.
• Modem and router status indicators.
• Gateway ping and external test results.
• Speed-test results and the test server used.
• Whether restarting the equipment restored access.
• Whether the ISP reported an outage.

This record helps the ISP compare your symptoms with equipment and service events. It also prevents repeated troubleshooting from starting without evidence.

Information gain: The five-layer check connects each test result to a next action. Instead of telling every reader to restart the router, it helps them decide whether to investigate the device, local network, router, ISP, DNS or application.

When should I contact my internet provider?

Contact your ISP when the connection remains unavailable after basic local checks, when multiple devices lose access together, or when your tests point to a provider-side problem. Give the provider specific observations and test results rather than reporting only that the internet is slow.

Signs that the problem may be outside your home network

Contact your provider when:

• The ISP reports an outage in your area.
• Multiple devices lose access over both Wi-Fi and Ethernet.
• The router shows a provider-facing connection fault.
• The connection repeatedly drops after local cables and equipment have been checked.
• Wired tests remain below the service performance you expect.
• The problem continues after the provider confirms that no general outage exists.

These signs do not independently prove an ISP fault. A defective modem, router or local network can also affect every connected device.

What information should you give your ISP?

Prepare this information before opening a support ticket:

Do not share passwords or sensitive account credentials in public forums. Use the provider's official support channel for account verification.

What should you do if the problem keeps returning?

Ask the ISP to investigate recurring interruptions rather than repeatedly restarting the equipment. Provide your fault log and request a service reference or ticket number so you can follow up with the same evidence.

Key point: Stop changing local network settings when the evidence points to an upstream service problem. Give the ISP the test results needed to investigate the connection.

Which internet troubleshooting fixes should I avoid?

Avoid factory resets, unnecessary DNS changes and equipment purchases before identifying the fault. A troubleshooting action should address a specific suspected cause, and you should verify the result before moving to another change.

Do not factory-reset your router as the first step

A normal restart turns equipment off and back on. A factory reset returns the router to its original configuration and can erase saved settings.

A factory reset can remove:

• Wi-Fi network name and password.
• Custom router configuration.
• ISP connection settings.
• Port forwarding and other network rules.
• Custom DNS and security settings.

Use a factory reset only when the manufacturer's or ISP's instructions recommend it and you have the information needed to restore the connection.

Do not change DNS without identifying a DNS problem

Changing DNS servers does not repair weak Wi-Fi, a damaged Ethernet cable or an ISP outage. First test whether domain-name resolution is failing.

DNS is responsible for translating domain names into network information. It does not increase the physical capacity of a broadband connection. (IETF RFC 1034)

Do not assume a new router will fix every slow connection

A new router will not automatically fix an ISP outage, a faulty modem, a device-specific problem or congestion on the provider's network.

Compare Wi-Fi and Ethernet first. Replace equipment only when testing or manufacturer/ISP guidance identifies an equipment limitation or fault.

Do not treat one ping or speed test as a complete diagnosis

Ping measures responses to diagnostic messages. A speed test measures performance to a selected endpoint. Neither test independently proves that every website or application works.

Use multiple tests and interpret their results together. The IETF's ICMP specification explains the role of control messages in IP networks, while its TCP specification describes a separate transport protocol used by applications. (RFC 792; RFC 9293)

Key tip: Change one setting at a time and repeat the original test. This makes it easier to identify which action improved or worsened the connection.

Sources and references

1. Microsoft Support — Fix Wi-Fi connection issues in Windows. Supports device comparison, gateway ping, forget/reconnect, driver and network commands.
2. Google Nest Help — Speed and connection troubleshooting. Supports speed-test interpretation, ISP vs local congestion and Ethernet limits.
3. Google Nest Help — Improve Wi-Fi. Supports distance, materials, bands and interference factors.
4. Apple Support — If your Mac can't connect to the internet. Supports Wi-Fi-connected-but-no-internet diagnosis, VPN and DNS checks.
5. IETF — RFC 2131: Dynamic Host Configuration Protocol (March 1997). Supports DHCP configuration.
6. IETF — RFC 1034: Domain Names — Concepts and Facilities (November 1987). Supports DNS concepts.
7. IETF — RFC 792: Internet Control Message Protocol (September 1981). Supports ICMP and ping.
8. IETF — RFC 9293: Transmission Control Protocol (August 2022). Supports TCP as distinct from ICMP reachability.