it is rarely rebooted

it's working thanks.

It's good now thanks!!

I'm not sure what you mean by 'give us the ability to use our own mail server'? I don't see how that would be possible as it would require a lot of configurations between the application and our own mail services. We came up with the limit of three emails before a reset after many years of monitoring the results of changing those and it has to remain at 3 unless there is a very compelling reason to change it. The point of the service is to help solve Internet issues which implies that someone monitoring is going to be checking when they get emails therefore, there is no point in constantly sending more and more emails about the same problem.

@edmundo Looking at the historical pings I can see almost the same behavior in both agents, maybe around the time you were sending the image it appeared to be different but I can see a consistent issue at your site. The amount of outages you are experiencing is very high. One more note about alerts... Alerts need to be acknowledged before another one can be raised i.e. if you don't acknowledge, let's say, an outage alert, even if new outages are recorded you won't be seeing it in the alerts

I have solved the issue. Thanks

I'll try now.

One thing that might help, can you use a 2amp power supply, just to be safe.

Thanks so much for fixing it! Everything is fully operational again and the subscription access is showing.

@SBK Yes. Connected to WeLink and working well! It also came back to working well state after enabling IPV6 in Eero router to check that (07 Feb 0814 CST, which caused router reboot). So, it seems like you have found a way to overcome whatever WeLink was doing differently than other ISPs (at least at this installation), or perhaps WeLink corrected something on their end (they did not tell me about any change, but they usually don't)

You're very welcome and thanks for bringing it up.

Yes, ping times are affected by which hops they flow through. We always wanted a more 'real world' result for pings so wanted those to go through many switches getting to our network. We just needed a reliable destination. It didn't matter where or what, so long as the agents algorithm was able to build up averages from which it would recognize latency changes. We've tested using closer (to the agent) destinations but it's never 'real world' like. We keep testing this to see how we can improve it. Thanks very much for bringing this up. We're looking into the other things too.

Kind of... I swapped it over to a switch that provides access to that same vlan subnet, and it was able to obtain an address that way. It doesn't seem to like being told what vlan to be a part of at the router interface. Still a mystery, but at least I've got a work around. Thanks again for your help in troubleshooting!

Did you find the email?

Hi Ed. Yes. I can see your messages now here.

Working now. Thank you!

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

Hi, yes, there is a delete option under Manage in that agent dashboard. Glad this was solved and thinks for using OutagesIO.

Thank you for the assist in regards to all of this. We are sorted and closed. :)