• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Default
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Quartz
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Slate
  • Solar
  • Superhero
  • Vapor
Collapse
Monitor your Internet service and provider

Information and Support

Automatically monitor your Internet service and provider with optional alerts to problems
Monitor your Internet services or devices to ensure they are always online. Tracks Internet connectivity and speeds with useful proof. For Windows, Linux, ARM (Raspberry, Tinker Board, etc).
Learn more by visiting www.outagesio.com
L

lp4y

@lp4y
About
Posts
76
Topics
2
Groups
0
Followers
0
Following
0

Topics

  • L

    Agents reports wrong router was down ?

    Scheduled Pinned Locked Moved OutagesIO features, agent or service questions agent internal outages
    0 Votes
    7 Posts
    115 Views
    L

    @SBK No matter if it's the primary WAN is up or not, 192.168.0.1 always remains up even during the failover or failback process. I verified this in my first post.

    That's why I said the agent reports something incorrect, because it reports that 192.168.0.1 is down when actually 192.168.1.1 is down.

  • L

    Agents is running but not reporting

    Scheduled Pinned Locked Moved Windows agent windows reports
    1 Votes
    142 Posts
    1085 Views
    OutagesIO_SupportO

    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.

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Login

  • Don't have an account? Register

  • Login or register to search.