Hi, can we consider this closed at this point?

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

Did the reply help you to know why the settings are as they are? Just wondering if I should close this.

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?

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. :)

Were you able to resolve this? We're happy to help if you still need help.

Hi, If this has not been solved yet, we can get your agent/s back up within a few minutes. Please see this post. https://support.outagesio.com/topic/295/urgent-yellow-hardware-agent-owners/4

Hi, We can get your agent/s back up within a few minutes. Please see this post. https://support.outagesio.com/topic/295/urgent-yellow-hardware-agent-owners/4

Great. Please keep this in mind if you add/remove agents. Glad it's working now.

BTW, if you go to Historical, Pings or Outages, there you can zoom in and out to see more data spread out.

The problem with using or posting IPs is that they can and do change so posting those publicly ends up being stale information at some point that some people would use only to find that nothing works. That said, let me explain how the pings work. The pings are set from source to destination. It doesn't matter what the destination is so long as it's consistent. The agent is not providing you pings to anything specific or meaningful to the user, it's using those to recognize if ping times are changing. The agent runs a set of pings, averaging those every minute then sending them to the network, mostly used as a visual piece of data showing when events may or did happen. The agent algorithm monitors for changes from what it has last re-calculated as average to x percentage difference. If that difference appears to be higher than average, then this triggers other tests such as a short speed test which can in turn trigger a full speed test if enabled. The point of the service is not to monitor the Internet but the provider so we're just using a target that is beyond the provider as a destination. Now, on the other hand, if you were a business customer with us, and you needed certain custom things specific to your environment, we would work with you for what ever you need because we would be communicating regularly so if we had to make changes and those could affect you, we would have a contact person to reach out to or that would know about the changes. Hope this helps to explain a little better why providing IPs would not work well.

Hi Marc, The value is intended always for the download speed which is usually higher or equal to upload. Also the percentage, right below, is intended for download only even if the results are including also upload and latency.