Automatically monitor your Internet service and provider with alerts to problems
Track Internet disconnections, provider outages with historical data, and automated speed testing.
For Windows, Linux, ARM64, ARMa7. Learn more by visiting www.outagesio.com
Notice: If you created an account on app.outagesio.com, simply use the same credentials to log in here.
  • 1 Votes
    13 Posts
    600 Views

    Great. Please keep this in mind if you add/remove agents.

    Glad it's working now.

  • 0 Votes
    8 Posts
    437 Views

    @mshafrin

    I am assuming that your firewall is also your default gateway, if not then what follows could be incorrect.

    If I take a look at the hops recorded by all 3 SW agents (not only the one you mentioned) and the only HW agent, you will see that only the HW agent is having the first hop pointing to 192.168.1.1, the other ones go directly to an external IP without passing thru the firewall/gateway.

    So on one side either the Windows agents or the firewall is masking the direct hops or they are connected in a different way from the HW agent; I also saw that the 130435 was once connected in a different way since it had the same 192.168.1.1 that now doesnt show up again.

    In the end, what does it mean?
    If the agent cannot determine where the LAN ends and the provider begins there is no way to give you a correct report about where the outage was and IF it was a network outage or a problem related to cabling (provider's end of cabling).

    If the firewall is NOT your default gateway then it would be nice to understand a bit more about the LAN topology to help to troubleshoot it but so far I haven't seen a wrong behavior from the agents you have installed.