Information, Support and FAQ relating to OutagesIO. Monitor your Internet service and provider with optional alerts to connection issues or downtime. For home, small business, IT companies and enterprise. Tracks Internet and provider reliability with useful proof. For Windows 7, 8, 10, Centos 7, 8, Debian 7, Ubuntu, ARM (Raspberry, Tinker Board, etc).
Free Internet troubleshooting agent for Centos, Ubuntu and others. OutagesIO automatically finds connectivity issues and gives you hard facts.
Ok, so at least we know that pings can be sent when the agent is able to get them.
When I checked earlier, the agent had no pings to send which means it wasn't getting any results from the operating system.
The pings aren't really important in terms of being an accurate measurement. They are mainly being sent as information that could be useful in some situations but mostly to see if there is a substantial change in latency between point A and point B.
If pings latency goes up by a certain percentage, the agents algorithm considers that this could mean something happening and can trigger a speed test for example and other tests.
However, if pings aren't being sent, it means the agent is not running right as ICMP is one of several functions used to also determine if there is an IP outages.
All that to say, it's important that you see pings being sent to the dashboard.
Since restarting the agent got pings going again, to me, it means maybe there is something on the OS that is monitoring certain behavior and limiting something like ICMP.
I would rule out the agent as having a bug because we would have seen it by now as there are many others running the same version.
These can be a bit hard to figure out sometimes. Let's see what happens next.
OutagesIO can be used by consumers, MSP's, ISP's, employers with remote employees, telehealth, security systems, remote equipment rooms, anything Internet connected. Monitor any number of locations with alerts to connectivity problems.
Here is what I see and with more information maybe we can figure out what is going on.
New Agents become inactive, 2 still active, 4 total.png
First, we need to eliminate 128292 because it isn't properly installed.
From what I can see it looks like it was working, then you re-installed it and that installation never completed.
What ever machine you installed this one on, you will need to make sure there aren't two agents installed on that same machine because we have seen cases where this can happen. If you have two, just remove both from the PC then use the re-install function in the agent's dashboard to re-install it.
Next, I notice that all of these agents are in the Philippines which is fine but I see them all at the same address, all using the same provider. Is it safe for me to assume that you are trying to use OutagesIO to not only monitor the Internet service but also different LAN segments? Meaning, perhaps you have an agent installed on different floors and each as its our routing switch.
Next, I need to understand what you mean by 'active' agents. Agents only go into another status based on if they can reach the OutagesIO network or not. As long as the agent software is running on the PC, does have the correct firewall rules, then it should be able to run normally.
As you mention, those things are fine on the PC but it sounds like there is something else on the network that might be preventing some of the agents from communicating correctly.
If you search for 'statuses' or 'inactive' on this support site, you'll find several explanations of what the different statuses mean.
In the most basic sense, Inactive means the agent wasn't able to reach the OutagesIO network for around 20 seconds or more. If you see Disconnected, this means it's been at least a half hour.
If all of these agents are on the same network, then you'll see different things potentially. Until I know more about how you are using all four and why they are in the same building, I'll have to wait to continue.