Information and Support

Fair enough. I can get the same functionality by configuring your email notifications to use [phone number]@[carrier's email].com. Just wanted to make sure I was seeing everything I was supposed to. Appreciate the response.

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)

Maybe we were not understanding each other.
I reviewed this post and I think what you are asking for is to specify what you'd like to ping.

If so, this is something we've considered and may implement in the future but I'd like to explain why it's not that way right now.

The main goal of the service is to let you know if your ISP is having problems. That means source and destination but not specifically with the ISP, only through it. In other words, so long as the destination is outside of the ISP, you'll be able to tell when/if your ISP is having problems.

If we set the ping destination to a certain hop, then you'll only ever know if that hop becomes unavailable and since packets can take different paths, you may not know about other connections failing.

This is why we just go through the provider to our own network where we have target servers that let the agents know if they reached or didn't reach the target, logging in between when there are IP outages.

Now, if you were not even seeing hops coming in, that would mean that ICMP is being blocked somewhere and that would affect one aspect of the agent being able to determine outages. Pings aren't really that important but they play one part. There is a constant test being done for source/destination latency. If pings start showing a certain amount of latency, that will trigger an automatic speed test.

I hope this helps to explain.

This question just happened to come in as we were working on some email related things. Adding this took all of a few minutes and is already in production.

Thank you for the suggestion.

BTW, we now have subscriptions that automatically renew and have lowered the price since this post.

Hi,

Not sure how this got past us but there isn't anything that only shows the past hour but perhaps I'm not understanding the question.
I believe the free community service shows the past 50 events, and the last four hours of pings.

Pings are mainly just a quick way to know if something has been happening.

Let us know if you have any more questions and apologies that this somehow got left open.

Hi, Did no one reply to this or did you start another question that gave you the solution?

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

@jjuly Great, thank you for the update and for using OutagesIO!

Please let others know whenever possible because Google favors deep pocket advertisers that prefer you would not find a solution like ours.

@SBK
I checked everything.
It seems I had the wrong keys.
Now works
Thanks for your time

@markl
Hi

It seems your agent is not able to connect properly to the internet.
I can see that now it is disconnected completely and it never sent PINGS.

Is there a chance your internal firewall is preventing this agent to use ICMP?

The ratio is much higher for software because it's an instant download.

Hardware is mostly used by businesses while software agents are mostly used by consumers and especially free members.

Because most people are becoming used to ordering online that waiting a day to a few days for most might not be a problem.

The Windows software is much more of a challenge to maintain across so many versions and so many possible combinations of packages installed on different PCs.

That said we do continue to try and find the elusive problem we seem to have with the Windows agent on some combinations of PCs and their installed software. However, this seems to be a rare problem as we've only heard about it a few times.

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.

Thanks for clarifying.

That method evolved because many members would never disable their emails when leaving the service and we found our domain getting blacklisted.

At one point, we didn't have such a limitation so the network could end up sending hundreds upon hundreds of emails to a mail service. It didn't take long before we got blacklisted which affected any other members using the same mail services.

Instead, we decided that since Inactive is something that someone should look into quickly if they are interested in such notifications, it made no sense to keep sending emails about the same thing.

This also helped solve being blacklisted and affecting other members.

Inactive notifications aren't outages, they aren't something the agent is able to detect, such as signal loss on coax and wireless based services. It's more of a notice that something is preventing the agent from communicating with the OutagesIO network.

https://support.outagesio.com/topic/12/about-internet-outages-alerts-and-agent-statuses/1

Hope this helps.

Hi,

Just visit paypal and you can cancel there. Just as a note, it's also where you can cancel any other subscriptions you have when it's not available on the site you purchased from.

In our case, we've spent countless hours trying to integrate it into the site but have not been successful and will keep working on that.

Hope you found the service of some use.

@brendan-techdoz said in Ordered subscription for the wrong agent:

130090

Hi,

Not a problem, the subscription was moved to the other agent for you.

Thanks for using OutagesIO.

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.

Hi,

The agent service should automatically start and stop when the PC comes up or goes down.

Have you looked at the service to make sure it's running? It's called Echo Networks Service.

When you installed, you were sure to be doing so as Administrator?

As an update, there is another thread in the forums where someone has around 30 agents and some random problems were coming up.

After months of testing, we were finally able to isolate the problem and we thought it was fixed.

Additional logs provided to us using the latest version shows that the problem is still there in some form or another.

The agent uses a multithreaded method and it seems that in some cases, one of the threads can spiral out of control causing the agent to miss sending some data now and then.

What's probably happened from looking at your reports is that the agent missed sending pings because the rest of the data looks consistent while the missing pings have no associated missing communications.

In other words, when those pings were missed, the gaps, the agent was still communicating which tells us it failed to send the pings in those times.

When you see gaps, you can always look at your outages to see if there was an outage at the same time. If so, you can discount the missing ping/heartbeat as it makes sense since the agent was not able to communicate. Otherwise, you can attribute the gaps to the problem we are now working on and will release an update once tested.

The biggest challenge with offering online services is that when folks come across problems, they usually prefer to blame the service and tell others how bad it is.

The fact is, if people took the time to let the service know about the problems, they will always do everything possible to fix any problems to keep hard-earned members.

Thank you for pointing this out.