Information, Support and FAQ forums for OutagesIOOur FREE software monitors your Internet service and provider then alerts you when you have connection issues or downtime. For home, small business, IT companies and enterprise. Monitor Internet outages, track network connection reliability, and get proof you can use. For Windows 7, 8, 10, Centos 7, 8, Debian 7, Ubuntu, ARM (Raspberry, Tinker Board, etc).
Learn more about www.outagesio.com by visiting our web siteNOTICE: If you previously registered on forums.outages.io, simply use the 'Forgot Password' option to recover your account.
Why so many outages?
Hey, the first brave soul to post in new forums :).
In terms of the service, it sounds like its doing what it should be, logging any and all outages.
If you find the number of outages being shown in your graph overwhelming, you could go to Settings and change the minimum outages shown to something higher. This way, you could filter to see only outages that lasted 5+ seconds for example.
In terms of the reasons, there are many. You didn't mention the type of connection, xDSL, cable, wireless, LTE but I'll cover some basics.
If most of your outages are showing 'On your local network', I would start looking locally. There could be something as simple as a cable or hardware failing somewhere. You should look at any and all of your equipment for frayed wiring, broken Ethernet tips and even a possible failing power supply.
If most of your outages are showing 'with your internet provider', then you'll want to look at your Network stats near the bottom of your dashboard page. Those stats will show which of the providers hardware devices is experiencing the most problems which are causing your Internet to be unreliable.
This information will give you everything you need to contact your providers support. Be aware however that providers typically will not acknowledge customer information showing where problems are. In this case, you would be best to take a screen shot of your findings and post those on your providers social pages.
One other option would be to get a neighbor or two to install agents so that you can pool your information and share that information on your providers social pages. If the problem is not at your location, the provider may be slow to get around to repairs until there are too many complaints to dismiss.
I hope this helps.
How do you actually determine its the local network Alex?
My agents are occasionally reporting outages "on the local network" but it's actually 4 hops from the monitor and on the private network of the ISP a few hops past my router.
Internally, we call this classifying the networks. For typical setups, this determination is quite accurate considering that both the local network and the providers often use private IPs.
Because of the above, there is no way to be one hundred percent sure that the software got it right and in not so typical setups, human intervention is required. The user must know their own network in order to understand the results.
In fact, this is something mentioned in these forums quite a bit, that in some cases, the agent cannot determine the local network from the providers and the user has to know this. I'll give you an example.
Lets say a private network with multiple routers, gateways and no static. The algorithm might think that the first gateway it sees is yours because the next one is say four hops away. It cannot reliably determine where your network ends and where the providers starts.
Lets say you have a couple of wireless routers being used as hot spots (APs) and in turns, those use your main router as their gateway. Then your providers IP is another private IP. The code may not be able to determine where your network ends and where the providers starts.
In some cases, providers control everything from their plant to the Ethernet port or access point they provide at the customers home. All these devices are on the providers network and the customer gateway is inside the providers network. The code may show that the gateway is where the local network ends.
While software can do a lot, in non typical setups, it is assumed that the user knows their own environment and can take this into consideration.
There is something on the table about allowing the user to 'adjust' their networks so the algorithm is aware of each network. For example, the user could specify which hops are in their own network and the algorithm would simply know this when it tries to classify the networks.
The classification code will get better as we get feedback and read about how members are using the service. We do have tests happening even as I type this and as we confirm something works, are able to constantly replicate a good result, then we look at adding it into production. There are a few things being tested in terms of the classification, it just takes time to prove or disprove it.