[SOLVED] packet loss at night

[qazujmf100]

i have a strange packet loss which gets strong at night and in some dayed it leds to dsl disconnect for a 1 asecond and reconnets
its starts like from 8 pm and keeps growing the dsl diconnecteing occurs around 12 am and it stops after 2 hours some days ihae only packet loss
and here is the trace i did to google


C:\Users\basyoni>TRACERT www.google.com

Tracing route to www.google.com [172.217.19.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 18 ms 18 ms 197.133.96.3
3 17 ms 18 ms 18 ms 172.31.139.1
4 71 ms 72 ms 68 ms host-81.10.87.165.tedata.net [81.10.87.165]
5 53 ms 57 ms 57 ms 10.37.123.237
6 * 110 ms * 7-2-37.ear1.Marseille1.Level3.net [212.73.253.57
]
7 108 ms 110 ms 111 ms 72.14.202.76
8 * * * Request timed out.
9 * * 226 ms 66.249.95.54
10 238 ms 241 ms 250 ms 108.170.252.227
11 223 ms 227 ms 211 ms 216.239.35.209
12 * 227 ms 218 ms 216.239.48.37
13 215 ms 229 ms 217 ms 216.239.54.32
14 249 ms 253 ms 259 ms 172.253.51.199
15 103 ms 94 ms 96 ms 72.14.237.85
16 92 ms 95 ms 94 ms 108.170.253.49
17 237 ms 236 ms 226 ms 209.85.245.203
18 278 ms 277 ms 285 ms ham02s17-in-f4.1e100.net [172.217.19.68]




and here is another one :

C:\Users\basyoni>TRACERT www.google.com

Tracing route to www.google.com [216.58.213.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 18 ms 18 ms 197.133.96.3
3 18 ms 18 ms 18 ms 172.31.139.25
4 23 ms 24 ms 23 ms host-81.10.87.101.tedata.net [81.10.87.101]
5 82 ms 82 ms 78 ms 10.37.123.217
6 * 281 ms * xe9-0-2.catania7.cat.seabone.net [93.186.129.10
]
7 * * 86 ms etrunk1.milano1.mil.seabone.net [93.186.129.199

8 301 ms * * 72.14.216.154
9 * * * Request timed out.
10 133 ms 134 ms 130 ms 108.177.3.78
11 106 ms 106 ms 111 ms 108.170.245.89
12 75 ms 80 ms 77 ms 72.14.233.132
13 89 ms 87 ms 89 ms 72.14.234.10
14 92 ms 93 ms * 172.253.50.101
15 141 ms 139 ms 135 ms 216.239.57.219
16 90 ms 92 ms 93 ms 108.170.253.49
17 181 ms 177 ms 185 ms 209.85.251.207
18 179 ms 168 ms 175 ms ham02s15-in-f4.1e100.net [216.58.213.196]

Trace complete.


thank you all

 

[failboat]

There looks to be congestion. It's hard to say where it's at though. See if you can monitor your bandwidth usage from the router. If it shows a bandwidth graph for up and down and if either are close to what you pay for then it's congested on your side.

Someone at home might have a cloud backup scheduled for that time.

Do the test to an ip in your same area.

 

[bill001g]

You are going to have to do a lot more testing to find it. Tracert tends to be to simplistic to find many problem. You could try pathping but it does not run long enough to really test. Most times you must run the ping commands yourself from multiple windows at the same time.

Be very careful in interrupting packet loss to intermediate hops. The equipment many times is configured to prioritize actually passing traffic to responding to ping and tracert. If for example in your second trace all traffic was actually being dropped in hop 9 you would see no traffic to the hops past it.

The big problem you are going to have I suspect is the problem is not in your ISP. The first couple hops show no issues which means it is not your PC or your connection to the ISP.

Also from what I can tell you are located in Egypt which has a history of poor connectivity both because of capacity issues with the fibers leaving the country and government censorship. I have not kept up on if the government is still blocking some traffic, there were capacity issues with the firewalls they were using to do this. If your problem exists in these areas there is not much you can do to get it fixed. It tends to be somewhat simpler to get fixed when it is the connection to your house causing the problem....this will be hop2 in your trace.