[SOLVED] Having issue with fiber internet speed is rx power causing issue? Or ISP server?

Jan 18, 2022
12
0
10
0
Having issue with fiber internet with model number HG8546M. This problem occur when i upgraded my plan from 25 mbps to 50 mnps. i got 65 download upload 75 mbps which is more than i subscribed plan and there is no issue arrived at the time of 25 mbps i am getting 24 up and 26 down and there is no any issue after i purchase fist line . Problem arrived after i have subscribed to 50 mbps plan which is the upgrade plan from 25 to 50 mbps and Problem is like time slot problem i get continue speed of my subscribed till 46 to 47 minutes that is 65 up and 75 down which is more than i subscribed after that i don't get download speed it cap to 4 mbps and do not go up and again but there is no change in upload speed i have to on off the router to function normal . This problem resolved after i downgrade the plan to 35 mbps where is get 51 up and 52 down but is subscribed 35 mnps plan but getting 51 up and 52 down instead of 35 mbps i contacted them and confirmed they saying your plan is downgrade to 35 mbps and now your net running well but after continue running well for 2 weeks same problem occurred after i switch off and switch on the router HG8546M but ISP saying we don't have issue but they saying let's change the device first we sending you high end device as there is no any issue in your optical power and if changing device also not help we will close current a.c and provide you new account.we don't have done any throttle to you. Checked all the speed test connection from router lan to laptop.
Is higher RX power causing issue?
Info of Optical:

Current Value
Reference Value
Optical Signal Sending Status:AutoAuto
TX Optical Power:2.31 dBm0.5 to 5 dBm
RX Optical Power:-16.93 dBm-27 to -8 dBm
Working Voltage:3301 mV3100 to 3500 mV
Bias Current:11 mA0 to 90 mA
Working Temperature:33 ℃-10 to +85 ℃
 
These new fancy routers with optical interfaces are very interesting. They actually tell you what numbers are within the valid range. You can see all you values are withing the recommended range. I wish other technology did this it would be easier than people have to look up what "good" values are for their router.

In general any actual problem with the fiber cable would cause packet loss and not slowness. Indirectly data loss will cause less throughput but the loss tends to be very obvious.

I strongly suspect this is something in how the ISP is limiting the speed you buy. When you look the specs up on your router it is using one of the very common GPON methods. It is actually running data over the fiber at 2.5gbit down and 1.25gbit up. This is the total network bandwidth that is shared by you and your neighbors on the same fiber segment.

Without some artificial limiter your speedtst should show 1gbit up and down with the gigabit ethernet ports causing the limit. The problem is the limiters, ie traffic shapers, are using complex math to get the rates. The data actually is sent to your house at 2.5gbit and they use a method to calculate a "average" value over time.

For simpler math lets say it sends at 1gbit on the fiber. So if you were to buy a 100mbps plan they could send data for 1second at 1gbit and then send nothing for 9 seconds. You average speed over 10seconds would be 100mbps. This is a extremely over simplistic example. The problem is massively more complex
when the rate they are trying to limit to is far different. I mean a 2.5g actual rate is huge compared to 25mbps.

There is very little you can do in any case. Most times this limitation is done in the ISP office. In theory it could be done in the router but I don't see that feature in the specs and hackers could bypass is so most ISP would not trust it.

I will assume you have tried multiple device in your house to be really sure it is not the end device but I strongly suspect this is some setting the ISP traffic shaper. These are extremely complex boxes to get configured correctly.
 
These new fancy routers with optical interfaces are very interesting. They actually tell you what numbers are within the valid range. You can see all you values are withing the recommended range. I wish other technology did this it would be easier than people have to look up what "good" values are for their router.

In general any actual problem with the fiber cable would cause packet loss and not slowness. Indirectly data loss will cause less throughput but the loss tends to be very obvious.

I strongly suspect this is something in how the ISP is limiting the speed you buy. When you look the specs up on your router it is using one of the very common GPON methods. It is actually running data over the fiber at 2.5gbit down and 1.25gbit up. This is the total network bandwidth that is shared by you and your neighbors on the same fiber segment.

Without some artificial limiter your speedtst should show 1gbit up and down with the gigabit ethernet ports causing the limit. The problem is the limiters, ie traffic shapers, are using complex math to get the rates. The data actually is sent to your house at 2.5gbit and they use a method to calculate a "average" value over time.

For simpler math lets say it sends at 1gbit on the fiber. So if you were to buy a 100mbps plan they could send data for 1second at 1gbit and then send nothing for 9 seconds. You average speed over 10seconds would be 100mbps. This is a extremely over simplistic example. The problem is massively more complex
when the rate they are trying to limit to is far different. I mean a 2.5g actual rate is huge compared to 25mbps.

There is very little you can do in any case. Most times this limitation is done in the ISP office. In theory it could be done in the router but I don't see that feature in the specs and hackers could bypass is so most ISP would not trust it.

I will assume you have tried multiple device in your house to be really sure it is not the end device but I strongly suspect this is some setting the ISP traffic shaper. These are extremely complex boxes to get configured correctly.
 
Jan 18, 2022
12
0
10
0
Pinging facebook.com [31.13.79.35] with 32 bytes of data:
Reply from 31.13.79.35: bytes=32 time=78ms TTL=54
Reply from 31.13.79.35: bytes=32 time=79ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=71ms TTL=54
Reply from 31.13.79.35: bytes=32 time=72ms TTL=54
Reply from 31.13.79.35: bytes=32 time=72ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=71ms TTL=54
Reply from 31.13.79.35: bytes=32 time=72ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=71ms TTL=54
Reply from 31.13.79.35: bytes=32 time=72ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=72ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54
Reply from 31.13.79.35: bytes=32 time=70ms TTL=54

Ping statistics for 31.13.79.35:
Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 79ms, Average = 71ms
Control-C
^C
C:\Users\Dell>
 

kanewolf

Titan
Moderator
C:\Users\Dell> ping -t goole.com

Pinging goole.com [217.160.0.201] with 32 bytes of data:
Reply from 217.160.0.201: bytes=32 time=285ms TTL=50
Reply from 217.160.0.201: bytes=32 time=276ms TTL=50
Reply from 217.160.0.201: bytes=32 time=281ms TTL=50
Reply from 217.160.0.201: bytes=32 time=272ms TTL=50
Request timed out.
Request timed out.
Reply from 217.160.0.201: bytes=32 time=271ms TTL=50
Reply from 217.160.0.201: bytes=32 time=334ms TTL=50
Reply from 217.160.0.201: bytes=32 time=314ms TTL=50
Reply from 217.160.0.201: bytes=32 time=333ms TTL=50
Reply from 217.160.0.201: bytes=32 time=277ms TTL=50
Reply from 217.160.0.201: bytes=32 time=271ms TTL=50
Reply from 217.160.0.201: bytes=32 time=275ms TTL=50
Reply from 217.160.0.201: bytes=32 time=275ms TTL=50
Request timed out.
Reply from 217.160.0.201: bytes=32 time=274ms TTL=50
Reply from 217.160.0.201: bytes=32 time=271ms TTL=50
Reply from 217.160.0.201: bytes=32 time=278ms TTL=50
Reply from 217.160.0.201: bytes=32 time=275ms TTL=50
Reply from 217.160.0.201: bytes=32 time=272ms TTL=50
Request timed out.
Reply from 217.160.0.201: bytes=32 time=271ms TTL=50
Reply from 217.160.0.201: bytes=32 time=272ms TTL=50
Reply from 217.160.0.201: bytes=32 time=273ms TTL=50
Reply from 217.160.0.201: bytes=32 time=271ms TTL=50
Reply from 217.160.0.201: bytes=32 time=270ms TTL=50
Request timed out.
Request timed out.
Reply from 217.160.0.201: bytes=32 time=278ms TTL=50
Reply from 217.160.0.201: bytes=32 time=277ms TTL=50
Reply from 217.160.0.201: bytes=32 time=276ms TTL=50
Reply from 217.160.0.201: bytes=32 time=271ms TTL=50
Request timed out.

Ping statistics for 217.160.0.201:
Packets: Sent = 33, Received = 26, Lost = 7 (21% los
Approximate round trip times in milli-seconds:
Minimum = 270ms, Maximum = 334ms, Average = 280ms
Control-C
^C
C:\Users\Dell>
I think you have some other issue. I don't know if that IP is actually google.com or not. It is NOT listed as a google.com address on this website -- https://www.lifewire.com/what-is-the-ip-address-of-google-818153 You might have some malware or other hijacking software that is causing your problem.
 
Jan 18, 2022
12
0
10
0
Pinging google.com [172.217.166.46] with 32 bytes of data:
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=67ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113

Ping statistics for 172.217.166.46:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 69ms, Average = 65ms
 

kanewolf

Titan
Moderator
Pinging google.com [172.217.166.46] with 32 bytes of data:
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=67ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113

Ping statistics for 172.217.166.46:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 69ms, Average = 65ms
At least that is a google IP address and it is stable. You have a DNS problem or a malware problem if sometimes "google.com" resolves to a bogus non-google IP address.
 
Jan 18, 2022
12
0
10
0
These new fancy routers with optical interfaces are very interesting. They actually tell you what numbers are within the valid range. You can see all you values are withing the recommended range. I wish other technology did this it would be easier than people have to look up what "good" values are for their router.

In general any actual problem with the fiber cable would cause packet loss and not slowness. Indirectly data loss will cause less throughput but the loss tends to be very obvious.

I strongly suspect this is something in how the ISP is limiting the speed you buy. When you look the specs up on your router it is using one of the very common GPON methods. It is actually running data over the fiber at 2.5gbit down and 1.25gbit up. This is the total network bandwidth that is shared by you and your neighbors on the same fiber segment.

Without some artificial limiter your speedtst should show 1gbit up and down with the gigabit ethernet ports causing the limit. The problem is the limiters, ie traffic shapers, are using complex math to get the rates. The data actually is sent to your house at 2.5gbit and they use a method to calculate a "average" value over time.

For simpler math lets say it sends at 1gbit on the fiber. So if you were to buy a 100mbps plan they could send data for 1second at 1gbit and then send nothing for 9 seconds. You average speed over 10seconds would be 100mbps. This is a extremely over simplistic example. The problem is massively more complex
when the rate they are trying to limit to is far different. I mean a 2.5g actual rate is huge compared to 25mbps.

There is very little you can do in any case. Most times this limitation is done in the ISP office. In theory it could be done in the router but I don't see that feature in the specs and hackers could bypass is so most ISP would not trust it.

I will assume you have tried multiple device in your house to be really sure it is not the end device but I strongly suspect this is some setting the ISP traffic shaper. These are extremely complex boxes to get configured correctly.
what should to know now? is it fault from isp side?
 
Jan 18, 2022
12
0
10
0
How could anyone but you answer that question ?
You deleted your post of a bad address resolution for google.com. I think that one of your problems. Have you done virus and malware scans?
Have you manually overridden your DNS settings to use google DNS ? -- https://developers.google.com/speed/public-dns/docs/using
sorry i type mistake address while ping . i installed kaspersky internet security in my machine . as time slot pass 56 minutes my ping is different . as there is time out issued occurred.

Reply from 172.217.166.46: bytes=32 time=101ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Request timed out.
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Request timed out.
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=70ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=70ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=66ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=71ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=70ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=70ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=66ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=134ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Request timed out.
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=72ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=78ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=70ms TTL=113
Reply from 172.217.166.46: bytes=32 time=74ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=65ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=63ms TTL=113
Reply from 172.217.166.46: bytes=32 time=64ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=70ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=92ms TTL=113
Reply from 172.217.166.46: bytes=32 time=118ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=74ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=83ms TTL=113
Reply from 172.217.166.46: bytes=32 time=149ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=73ms TTL=113
Reply from 172.217.166.46: bytes=32 time=150ms TTL=113
Reply from 172.217.166.46: bytes=32 time=79ms TTL=113
Reply from 172.217.166.46: bytes=32 time=78ms TTL=113
Reply from 172.217.166.46: bytes=32 time=68ms TTL=113
Reply from 172.217.166.46: bytes=32 time=71ms TTL=113
Reply from 172.217.166.46: bytes=32 time=69ms TTL=113
Reply from 172.217.166.46: bytes=32 time=182ms TTL=113
Reply from 172.217.166.46: bytes=32 time=164ms TTL=113
Reply from 172.217.166.46: bytes=32 time=188ms TTL=113
Reply from 172.217.166.46: bytes=32 time=155ms TTL=113
Reply from 172.217.166.46: bytes=32 time=182ms TTL=113
Reply from 172.217.166.46: bytes=32 time=172ms TTL=113
Reply from 172.217.166.46: bytes=32 time=172ms TTL=113

Ping statistics for 172.217.166.46:
Packets: Sent = 1441, Received = 1435, Lost = 6 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 188ms, Average = 67ms
 

kanewolf

Titan
Moderator
Ping statistics for 172.217.166.46:
Packets: Sent = 1441, Received = 1435, Lost = 6 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 188ms, Average = 67ms
Are you using an ethernet connection or a WIFI connection to the router ?
You need to have a parallel ping to your router to ensure that the dropouts are not local to your network.
 
Jan 18, 2022
12
0
10
0
Are you using an ethernet connection or a WIFI connection to the router ?
You need to have a parallel ping to your router to ensure that the dropouts are not local to your network.
Are you using an ethernet connection or a WIFI connection to the router ?
You need to have a parallel ping to your router to ensure that the dropouts are not local to your network.
using ethernet.

how may i do that?
 
Jan 18, 2022
12
0
10
0
C:\Users\Dell>ping -t 192.168.100.13

Pinging 192.168.100.13 with 32 bytes of data:
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.13:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
 

kanewolf

Titan
Moderator
C:\Users\Dell>ping -t 192.168.100.13

Pinging 192.168.100.13 with 32 bytes of data:
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128
Reply from 192.168.100.13: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.100.13:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Unusual address for the router, but otherwise totally normal.
 
Jan 18, 2022
12
0
10
0
as my connection is pppoe . i done manually connect mode from automatic . as same error occur i do disconnect and reconnect and again it work normal. i do season terminate in 50 minute . i don't do now router on off. it means my path of line is okay . Problem in VLAN or in my account?
 
If you really think the problem is in the line to your house you need to do a different ping.

Run tracert 8.8.8.8 It will likely show nothing interesting, the goal is to get the IP of the routers in the path.

Now leave a constant ping run to the IP in hop 2. This should be the IP of the first ISP router outside your house. If there are issues here you need to contact the ISP and have them test the line.
 
Jan 18, 2022
12
0
10
0
If you really think the problem is in the line to your house you need to do a different ping.

Run tracert 8.8.8.8 It will likely show nothing interesting, the goal is to get the IP of the routers in the path.

Now leave a constant ping run to the IP in hop 2. This should be the IP of the first ISP router outside your house. If there are issues here you need to contact the ISP and have them test the line.
there is no issue its pinging..
but my problem is i get high bandwidth of which i haven't subscribed . there is over flow of traffic?
 

ASK THE COMMUNITY

TRENDING THREADS