Information and Support

They don't include any when we order them either. We used to provide them but most people have dozens of old USB power supplies laying around. Any 5v 1amp will do. Example; USB wall plug from ebay Probably bags of them at the local Goodwill :).

Thank you for letting us know. Glad you got it.

@fardvrsgr Hi Frances, When you create a new agent you are supposed to follow the instructions that are taking you to the point of downloading the executable to install the software on your PC In that page you didn't confirm that you downloaded the software so you cannot see the keys needed to continue the installation From the agent list if you click on the link "Click to complete" you will be taken to the page where you already downloaded the file and there you can simply press YES to confirm you did download the software (assuming you have) and there you will see the keys needed to install

@shahinfard Hi, Please double check that all the settings are now associated to the HW agent.

Glad you got it.

As explained earlier, when you see disconnections but no outages, it means anything but IP outages. Those links I shared explain what some of the causes could be, bad or slowly failing cable, firmware needing an update in your firewall or router or modem, or your provider has a signal level problem at the street level and they aren't acknowledging the problem. The only way to know more in your case would be to get one or two neighbors to install an agent also so that we can correlate their data. To get more info, you could always upgrade your reports for 30 days and that will show you historical data and other information that may or may not help. It may not help since you seem to be experiencing problems which aren't specifically IP related so the agent cannot log those, it can only tell you that's what seems to be happening. You can know this because of what you aren't seeing, IP outages that would be logged by the agent.

So how is it going? Did you figure it out?

@rollytabora The installation of the agent is not provider related i.e. you can install the agent (the software you will install on each of your two PCs) and let the software run. If one computer is connected to Verizon 5G and the other one is connected to T-Mobile you simply have to check how many outages were accounted to each agent and you will know which is best for you. Otherwise, if you can have only one provider at a time for both computers then you can let the agent collect as much data as possible (let's say for one week) and check how many outages were collected; then you can RESET the agent's data (you will loose that historical info) and connect to the other provider to test it the same way you did it before

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. In terms of running as a service, I think this is what you are looking for. Monitor your Internet with raspberry pi, nanopi and other arm devices

@markl Hi Mark, I recall during the tests we made that if the agent was connected to one network the speed tests were coming in correctly while connected on the other one they didnt. Is this the situation?

@SBK No matter if it's the primary WAN is up or not, 192.168.0.1 always remains up even during the failover or failback process. I verified this in my first post. That's why I said the agent reports something incorrect, because it reports that 192.168.0.1 is down when actually 192.168.1.1 is down.

@dberges Hi Dave, I see you were installing twice the agent on the same PC (ids 129143 and 129196) and then you installed on a new one (id 129201) I bet you are referring to the last one since the other one is not connected (software uninstalled or something else) This agent was created almost 10 hours ago but so far no IP outage has been recorded. Consider that the disconnections could also be unrelated to IP outages but I suggest to let it run for at least 48 hours before analyzing what is happening to the connection Anyway just check the pings graph [image: 1655429887176-b22ca079-9164-4745-b6a2-8f6949c2fc88-image.png] You can see that some info was missing from the agent even if no outage was recorded

@Laguy442 Yes correct Those "missing" ping are just a possible problem in the connection If your router disconnects for those 2 min and 22sec then you have already the answer but lets wait a bit to see how much data is stored and what you can see from the dashboard

@SBK Yes, it says "Export date: Jun 9, 2022, 4:26:43 PM" but it was 7:26pm.

@markl Done

Hi, were you able to find the problem?

@claytonbcollins Hi, Yes, we are already testing a new version that is going to include also the upload speed test. I cannot give a precise time-frame yet but definitely we want to get there too :-)

@OutagesIO_Support Never mind. I searched for that command you suggested, "ps cax | grep otm_binary", in the forums and saw it mentioned to run the script, "sudo ./starter.sh". And now I'm back up and running! Thanks! Clay