Skip to content
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
    18 Posts
    51 Views
    OutagesIO_SupportO

    The 3 agents are recording a similar situation on Jan 13 at >around 13:33 Chicago time but at the same time are not >recording any type of outage.

    We are confused why you keep saying the agents are not reporting outages, all three have done just that.

    This is your 129878;
    image.png

    This is your 131232;
    image.png

    This is your 131236;

    image.png

    As can be seen, outages are being logged. There was a problem with notifications which we fixed as soon as you told us about it.

    Did you read the links that were sent? Outages are being recorded but most of your problems are not IP outages, they are some other kind of disconnection.

    Two different technologies (Windows, Openwrt) and >three different versions (MT300 and MT3000 even if >they both are openwrt are different in binaries) but they >all:

    The technology is the same in terms of how the agent works but the binaries are of course different since they run on different platforms.

    cannot identify an outage
    See images above.

    are monitoring inactives
    Because that is where most of the problems you are experiencing are, disconnections, not IP outages.

    they disagree in some minor timing, which can be >related to the way the three agents are connected to >the LAN
    Yes, there would be minor differences in timing which is expected since loops have to run so timing can be a bit different.

    So next question is: is it possible, without any specific >detail, understand if all three agents are connected the >same way within the LAN (different VLANs, directly >connected to the router or thru a switch, different rules >in the firewall)

    Sorry, I'm not seeing the actual question. Can you elaborate on this please.

    A simple hand drawn picture is more than enough, as I >said no company detail is needed, jsut trying to see >where the problem is originated and why they behave in >such a way.
    An image of what? From whom? For what?

    We've spent two days solid on this and still willing to help but cannot know anything beyond what you are explaining without remote access. Even with remote access, it might not be clear what's going on but we're still trying to help. Just kind of blindfolded at our end other than what we see from your agents.

    What we see is that there is something on your network that seems to be blocking communications here and there. It seems to be random, like maybe a firewall rule suddenly kicking in after it's seen a certain amount of traffic to/from our network.

    If this were a common problem, we would see it across all of our agents but we don't. We only see it in your reports and it's as odd to us as it is to you.

    Remember that this service is not the ultimate answer to everything, it is just another tool. It automates as much as possible logging disconnections and IP outages. It is meant to monitor your ISP, not your LAN. It is not a network diagnostic tool, it is part of your other tools that you would use to find and solve IP problems.

    Other than monitoring to see if we can catch a clue, we so far have not seen anything that tells us what is going on but we are also blind since we cannot see what's going on from the agents point of view.