Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
SOLVED: Frequent brief disconnects
-
I have sent an email to the dev that works on the agent to see if he has any ideas because I'm stumped on this. I've never seen that before.
-
@outagesio_support
Thanks -
Sometimes, one browser can show something while another might not but in this case, that's not the problem as we're seeing the same thing as you are in your reports.
Hops have no relation to the browser and are sent by the agent software. -
@outagesio_support
Yeah, I realized that after I sent it because I don't even have to be logged in at all for it to still be sending pings.You mentioned something several posts back about my maybe having to enter some firewall command(s) manually. Can we try that? How difficult is it to do and are there any potential risks?
-
My disconnects have gotten worse. I have to get the cable tech out. Before he comes, I'd like to understand something:
My graph of speed tests for the last 50 attempts, between 4 am and 11 am, show over 40 outages.
Since the computer that is running your software is connected directly to the cable, being plugged into the back of the router, and is not running wirelessly, doesn't this graph alone prove that the problem is not in the router but in the cable?Thanks.
-
@johnmeyer said in Frequent brief disconnects:
You mentioned something several posts back about my maybe having to enter some firewall command(s) manually. Can we try that? How difficult is it to do and are there any potential risks?
No harm what so ever, it's just one rule to allow the agent only to communicate. This is assuming the rule is not there.
https://support.outagesio.com/topic/77/no-hops-no-pings-in-my-dashboard
Check the above post and see if you have such a rule in your firewall. The image is showing a Windows 7 I think so yours might look a bit different.
-
@johnmeyer said in Frequent brief disconnects:
My disconnects have gotten worse. I have to get the cable tech out. Before he comes, I'd like to understand something:
My graph of speed tests for the last 50 attempts, between 4 am and 11 am, show over 40 outages.
Since the computer that is running your software is connected directly to the cable, being plugged into the back of the router, and is not running wirelessly, doesn't this graph alone prove that the problem is not in the router but in the cable?
Thanks. -
@johnmeyer said in Frequent brief disconnects:
My disconnects have gotten worse. I have to get the cable tech out. Before he comes, I'd like to understand something:
My graph of speed tests for the last 50 attempts, between 4 am and 11 am, show over 40 outages.
Since the computer that is running your software is connected directly to the cable, being plugged into the back of the router, and is not running wirelessly, doesn't this graph alone prove that the problem is not in the router but in the cable?Thanks.
As mentioned, the reports don't indicate IP outages as the main problem but something else. It could be anything from a bad cable connection, failing router or with your provider such as signal levels issues.
The only IP outages you've had are all with this 192.168.50.1 device. The rest of the problems are something else. This is of course a lead. It means you should definitely try another cable as well.
When you say your Pc is connected to the cable, I assume you mean directly to your providers cable modem?
Your speeds have gone as low as 5.44Mbps which is incredible considering you said you have a 1GB connection.
The highest speed test recorded was 108.61Mbps which is almost 900Mbps less than what you are paying for. This leads to wonder if your PC has a 100Mbps card install and not a 1Gigabit card or that your router has 100Mbps ports rather than 1Gibabit.
You should take a look at what speed your PC network is running at. It will look something like this.
In terms of the black speed test result bars, we think there is a bug in terms of those outages based triggered speed tests.
We think that what is happening is that the agent triggered a speed test when it sees disconnections while it is supposed to trigger them only if there are confirmed IP outages.
It's not a bad thing, it's just not as clear as we'd like it to be for members.
-
Thanks.
My desktop is fairly old and the card is 100mps - which explains the slower speed on that computer. I do all my work, etc on my wireless tablets and phones which are newer.
The desktop is cabled, with a new cable, to the 1 gig port in my new router which is AX3000, about a year old, high end
I have two optional cox cable leads to the modem (also new and also mine) and the results are the same with either cable. The last Cox tech out told me each of the cables to the modem are receiving 1,024
When you say the speed test is being triggered by disconnections, then that means all those black bars represent disconnections, no?
thanks
-
My desktop is fairly old and the card is 100mps - which explains >the slower speed on that computer. I do all my work, etc on my >wireless tablets and phones which are newer.
That's fine. People should not be testing full speeds all day long anyhow. What we really want to know since it's shared bandwidth is that we have enough to work with. Your bandwidth seems fine then, at least very consistently usable but there is some other problem with the connection. This also leads me to believe bad cable or signal levels problem / bad interface on the providers side IF you determine it is not on your side.
The desktop is cabled, with a new cable, to the 1 gig port in my >new router which is AX3000, about a year old, high end
At this stage, your PC should be connected directly to your providers device to eliminate anything that is yours. If the problems continue (on the PC of course) and since you are connected directly to the providers device, that would show that the problem is with the provider.
The last Cox tech out told me each of the cables to the modem >are receiving 1,024
Remember that they are testing bandwidth to the street. It's all they are obligated to do but bandwidth alone does not mean your service is not experiencing problems which you obviously are. They need to check more than speed.
When you say the speed test is being triggered by >disconnections, then that means all those black bars represent >disconnections, no?
The black bars represent a speed test triggered by the agent. It means the agent algorithm noticed a change drastic enough to quickly trigger a speed test. The agent cannot know initially if the disconnection is just that, a disconnection or at actual IP outage;. It only knows there is a problem so it tries to run as many tests as it can as quickly as it can.
The black bars can be generated by either disconnections or outages. You can know the difference if there is an outage around the same time as when a black bar came in. If there is no outage but there is a black bar, it means there was a disconnection without an IP outage report.There is a difference between an IP or non IP outages.
These can help a bit.The nature of tcp ip and internet connectivity
About cable and wireless servicesThat section of the forums contains other information you might find useful.
-
@OutagesIO_Support
Cox cable worked at the street level and removed some splitters and replaced a few cables in our house. The brief disconnects have dropped from 18 to a consistent 4 a day. Have no idea why 4 remain and am still monitoring but we can live with 4 a day and would rather do that than have techs climbing through the house again.
My computer has been left on consistently for monitoring. Please let me know if can draw any conclusions at your end - I'd appreciate it. -
@johnmeyer My suggestion would be to keep monitoring to see if you can find a pattern since it's different from when this question started.
Once you spot something, post a new question with those details and maybe we can offer a little insight.