Keep the test conditions consistent
- Same Ethernet device and cable
- Quiet-time and evening timestamps
- Household traffic paused
- Router-side Wi-Fi and problem-room comparison
Evening slowdown guide
Why Is My Internet Slow at Night?
Compare the same connection during a quiet period and the evening problem window, then use Ethernet, household-load and bufferbloat checks to locate the bottleneck.
Quick issue resolution
Why Does the Internet Slow Down at Night?
Choose the evening symptom that matches your connection, then use its likely cause and immediate action before moving to the full test sequence.
Peak-time slowdown
Broadband Slow Every Night Between 7pm and 11pm
A repeated peak-time slowdown can come from provider congestion, household traffic or FTTC interference. When the same wired device slows while other home traffic is paused and several independent services are affected, the evidence points more strongly towards the provider path.
Likely cause: provider access, backhaul or peering congestion.
Immediate action: run a quiet-time broadband speed test, repeat it on the same Ethernet device during the evening problem window and keep both results.
Wi-Fi only slowdown
Ethernet Fast but Bedroom Wi-Fi Slow at Night
When Ethernet remains fast but distant rooms slow down, the broadband line is not the main bottleneck. More active devices can increase wireless airtime use and expose weak signal, poor mesh placement, interference or an overloaded repeater.
Likely cause: Wi-Fi coverage, interference or airtime saturation.
Immediate action: compare Wi-Fi beside the router and in the problem room, then reposition the router or mesh node and wire fixed devices where practical.
Loaded latency
Ping Spikes During Uploads, Backups or Game Updates
The router or upstream link may be building a large queue whenever the connection becomes busy. That queue delays gaming, calls and web traffic even when download speed still appears usable, so the problem feels like evening congestion.
Likely cause: upload saturation or bufferbloat.
Immediate action: pause background transfers and run the Bufferbloat Test to measure loaded-latency spikes.
Service-specific slowdown
Only One Streaming Service, Game or Download Is Slow
A single slow platform does not prove the whole broadband connection is congested. The bottleneck may sit with the remote service, its content-delivery network, the selected game region or one route between that service and your provider.
Likely cause: service, CDN or route-specific congestion.
Immediate action: compare another independent service and run the Packet Loss Test before replacing home equipment.
FTTC and copper interference
FTTC Slows When Streetlights, Heating or Appliances Switch On
Copper-based FTTC and ADSL can suffer additional errors when electrical equipment emits interference. A repeated evening timestamp, rising router error counts or retrains, and an unchanged problem from the master test socket provide stronger evidence than one slow speed result.
Likely cause: REIN, SHINE, crosstalk or copper line instability.
Immediate action: test from the master socket, record appliance or lighting timings and save router error or retrain evidence for the provider.
Dropout rather than slowdown
Broadband Disconnects Instead of Just Slowing Down
Changing router, DSL, PON or LOS lights indicate a different fault from ordinary evening congestion. If the router restarts, the physical line retrains or the optical signal disappears, diagnose the dropout before treating it as a capacity problem.
Likely cause: router, fibre, DSL or provider-session disconnection.
Immediate action: use the broadband disconnection guide and record the light state before rebooting.
Test first
How to Separate Household Load from Provider Congestion
Use the same device and test method each time so the comparison is meaningful.
- Create a quiet-time wired baseline.
Run the Broadband Speed Test and record download, upload, ping and jitter on the same Ethernet device during a period when the problem is absent.
- Repeat during the evening problem window.
Keep the same device, Ethernet cable and test location. A repeated change is more useful than one isolated slow result.
- Pause household traffic.
Stop console updates, cloud backups, photo sync, CCTV uploads, torrents and additional streams, then repeat the test.
- Compare Ethernet with two Wi-Fi locations.
Test beside the router and in the problem room. Fast Ethernet with weak room performance identifies a home Wi-Fi issue.
- Run a loaded-latency test.
Use the Bufferbloat Test. If ping rises sharply while the line is busy, treat queue management and upload saturation before blaming raw package speed.
- Repeat on more than one evening.
Record whether several services and wired devices follow the same pattern before escalating or switching.
Advanced checks
Technical Causes Worth Checking After the Basic Comparison
Provider access, backhaul and peering congestion
Congestion can sit at the local access node, regional backhaul or a handoff to a content network. A strong case uses the same wired device, repeated quiet and peak-time tests, paused household traffic and more than one affected service.
FTTC crosstalk and REIN/SHINE interference
REIN (Repetitive Electrical Impulse Noise) is repeated electrical interference that can raise error rates or cause recurring DSL instability on FTTC and ADSL. Faulty power supplies, heating controls, pumps and other mains-powered equipment can be sources.
SHINE (Single High Impulse Noise Event) is a larger, shorter-duration electrical impulse that can create a sudden burst of errors or force the DSL connection to retrain. If the problem repeatedly starts when particular equipment or lighting switches on, record the exact time and compare it with router error counts or retrain logs.
Crosstalk is different: it is interference between neighbouring copper pairs and usually presents as reduced DSL performance rather than one identifiable household appliance switching on. Use the repeated time pattern, master-socket result and matching router statistics together rather than relying on one speed test.
Traffic shaping or one congested content route
When only bulk downloads, one game region or one streaming service slows, compare other destinations. A route-specific problem is not proof that the entire broadband connection is congested.
Escalate with evidence
What to Record Before Contacting the Provider
Record the measurements
- Download and upload speed
- Ping, jitter and loaded latency
- Packet loss or line-error changes
- Which services and devices were affected
Strong provider evidence: the same wired device repeatedly slows during the same evening window while other household traffic is paused and several independent services are affected.
Common questions
Evening Internet Slowdown FAQs
Why does my broadband slow down every night between 7pm and 11pm?
Evening is a common peak-usage period. The slowdown can come from household demand, router bufferbloat, weak Wi-Fi under load, FTTC crosstalk, traffic shaping or provider congestion.
How do I know if night-time slow internet is Wi-Fi or the provider?
Compare direct Ethernet with Wi-Fi in the same evening window. Fast Ethernet with poor room Wi-Fi points to wireless coverage. Slow Ethernet with other devices paused points towards the line or provider path.
Can bufferbloat make internet slow only at night?
Yes. Evening uploads, downloads, streams and backups can run together. Poor queue management can make ping and responsiveness collapse even when headline speed remains usable.
Can an electrical appliance cause internet slowdowns at night?
Yes. On FTTC and older copper connections, faulty lights, power supplies or other electrical equipment can create REIN or SHINE noise that increases line errors after dark.
Should I switch provider if my internet is slow every evening?
Only after testing direct Ethernet, pausing household traffic and collecting repeated day-versus-night comparisons. If the provider route is consistently congested, comparing full-fibre and alternative provider options is reasonable.