Information and Support

Trashing us publicly for trying to help you doesn't make any sense. You told us you have had up to 30 agents running and said it was great that it's free.

As an admin yourself, surely you can appreciate the complexity of this problem. Even as a free member, we are still committed to helping because we want to find and solve the problem.

The problem is not widespread. If it was, we would be hearing about it a lot but we aren't. You are running 2016 servers and it's quite the task to have a single software that runs across all Windows versions.

Losing track is easy because it's a very long thread, and we've made other updates in some of the releases. The dev told me it was fixed in 1.75 but the log you sent us was 1.77 so clearly there is simply something that got out of sync.

If the agent is not working for you, we do not know why. I can tell you that the Windows dev has been working on yet another release to try and improve the fixes recently made but I don't know if that will solve why only some of your agents are not working right.

I'll reach out again to try and find out what he meant by pointing out 1.75 as being fixed.

BTW, what did it cost you to send those agents back so we can include that in the refund.

Thanks for the update. Glad it's working now.

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.

The update to fix the Windows installer problem has been released. Simply create a new software agent which will give the download to the new version.

@kmichailg

Yes, this confirms the change we decided to apply: we want to avoid cookies usage in the login phase at least.

That error is the effect of that change.

Please inform of any other situation where the login for some reason is affecting the normal behavior of the app

@OutagesIO_Support Thank you. I appreciate the time it took to troubleshoot this one with me.

Thank you!!! All reported times (pings, hops, etc) seem to be spot-on here. You guys are the absolute best!!

@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.

Thanks for feedback.

They key to getting the best reports is to run the agent on something that can remain on 24/7 if possible. If that is not your main PC, then a very low cost second PC or a hardware agent. The only way to really know what is going on is to log everything non stop, at least for a while so you can also see trends.

Hi,

Those refurbs come up now and then but we no longer have any at the moment sorry.

First, enabling DDNS in your agent dashboard is a way to reach something on your network without having to remember the IP.

For example, if you had a security camera at home and didn't want to look up the IP all the time, you would set the DDNS on your agent to a name. In this case, mylan.dnspoints.com.

The dnspoints.com is simply a left over domain from something else we worked on which we use to give members an easy to remember word.

Next time you wanted to reach your camera, you would enter mylan.dnspoints.com into your app/browser and would not have to remember any IP even if it changed.

Second, the DNS server built into your router can be used if your ISP's dns server goes down.

You could configure the agent's LAN IP as another DNS server in your router or on your PC.

Most people have their routers handing out DHCP IPs so that is probably where it should be put.

You won't reach anything by trying to visit the agent as it does not respond to anything in terms of trying to see something with a browser. There is no service other than the DNS service.

After 3 emails have been sent out the system automatically disable that option to avoid sending too much of them
That value has been set based on the past experiences we had with other customers

There is a chance we will re-evaluate how that is working for consumers (enterprise user have a different setting)

@outagesio_support

Yes, we played with enabling different DNS but it never really got "ideal".

However after they redid all the connections, one of my "download" scripts became much better -- so I dunno. Our web connections/surfing were not particularly better until the VPN.

I'm not sure if you've already done this since this post was not updated but the latest version is now;

SCRIPT_VERSION="2023-1-26_1050_Phoenix_TZ

And you can download it here;
https://downloads.echonets.com/scripts/starter.sh

Just kill the otm process (as explained above) if it's running, then start over using the new version of the starter. The starter itself will now tell you when there is a new version.

You're welcome. Thanks for using the service and please, pass the word on. We live by word of mouth since it's impossible to outbid deep pocket ISPs and outages sites that would rather you don't find a service like ours.

image.png

image.png

image.png

We now see your replacement agent online and will swap it back to your subscription. The ID will change back to 130151.

Always happy to help.

Please consider mentioning us in other forums, telling friends or sharing a review on Google.
People have a very hard time finding us because Google favors the very deep pockets of providers and outage sites that may prefer you don't find tools like this :).

I have made a tiny change in the logic
Please let me know if the following outages are correctly identified
The hops looks better now for both agents