Information and Support

Thanks for letting us know.

And now we see it Inactive. It it stays this way for 29+ minutes, it will then change to Disconnected status.

Last communicated on 2023-02-09 13:02:30.

So our Windows dev did some digging and this is what we were told.

I've found the reason for the crash this person experienced when installing. If the service fails to start because the Listen() call throws an exception then the exception handler calls Close() and Close() fails to check if the handle pointer is a null reference before using it. What I don't know is why we are not able to start a named pipe on that persons machine. I'll add the missing check to the library code but that won't cure the actual problem they had, so I'll investigate further on what might prevent use opening a named pipe on Windows 10 Pro. I've never seen that fail before. So I don't think we have a general issue here, more likely a restriction configured on that machine or possibly the name we use for the pipe is already being used.

@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

We don't list Inactives in the reports because those very much confuse people but you can set notifications as you have which is why you see the email but nothing in the reports.

The main objective of the service is to show confirmed IP outages, mainly on the LAN and especially with the provider. All other data is simply helpful in trying to diagnose what is happening.

In other words, what you don't see is sometimes what the problem is. In this case, we're not seeing a lot of IP outages but we know there are disconnections. This tells us that the problem might be failing hardware or bad signal levels somewhere.

Here is what I see for the 27th so far.

Event Beginning at
Online 2022-01-27 12:31:12
Inactive 2022-01-27 12:31:09
Online 2022-01-27 12:11:43
Inactive 2022-01-27 12:11:39
Online 2022-01-27 09:57:03

This is something we see internally only.
2022-01-27_130736.jpg

We are working on a consolidated report that will show all of the metrics together in a way that will hopefully explain everything that's going on, in one correlated view.
This has been a huge challenge however for many reasons but we're working on it.

Inactive and Disconnection statuses do not automatically mean IP outages, it just means something stopped working. The agent is not able to communicate with the OutagesIO network but we don't know why since it doesn't seem to be IP related otherwise, the agent should always pick those up. Could be a bad cable, could be signal levels, something along those lines.

So far, the agent was able to confirm that there was just one IP outage that lasted one minute and fifteen seconds but all other issues appear to be non IP related.

This might help explain how the agent works a little and there are other articles in that section that also explain how things work.

Aabout Internet outages alerts and agent statuses

When you have problems like these, if you can find another location using the same provider in the same area that would be willing to monitor, it becomes quite eye opening if both locations seem to be experiencing the same problems.

There is another person experiencing something similar who has been posting in the forums in the past few days too.