Hi, I can confirm that they are not connected to our network.
Can you please use the www.outagesio.com contact form letting us know which agents are involved and we can get into direct contact.
Global Moderators
Forum wide moderators
Posts
-
-
Great. Please keep this in mind if you add/remove agents.
Glad it's working now.
-
Hi,
Do you have this working now?
-
Is it better now?
-
Can you check it now please or keep an eye on it to see if it's correct? We made the second hop your ISP.
-
Thanks. I'll ask that someone look at this shortly and adjust it.
-
Hi, sorry, for some reason, we didn't see this reply.
Can you provide the agent ID please. -
BTW, if you go to Historical, Pings or Outages, there you can zoom in and out to see more data spread out.
-
@mschubert
Let me highlight few things before I will dive into your agent's issue.The idea behind the "pings gaps" is to show in a graph when the pings are not reaching our receivers (our network's servers in charge of this feature).
This "not reaching" can be explained with:
- a real missing connection to our network meaning the agent becomes inactive, disconnected or abandoned, please check https://support.outagesio.com/topic/55/manage-agents-menu for further explanations of the "offline" status
- a temporary overload of local (your) or remote (our) network
- an error in the local agent associated to the multi-threading nature of the agent app
- a network outage
I do see that your agent has had 3 outages and this reflects only part of the "missing pings"
but I also see that from April 18 your connection was inactive few more times:
In your case I tend to believe it is option 1 but I have opened an internal ticket to be sure we are not in option 3 for the agent 130916.
-
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.
Support for GL-MT300N-V2
ISP using 10. for first hops. Those are not on my local LAN.
Raspberry Pi4 x64 otm error
ISP using 10. for first hops. Those are not on my local LAN.
ISP using 10. for first hops. Those are not on my local LAN.
ISP using 10. for first hops. Those are not on my local LAN.
ISP using 10. for first hops. Those are not on my local LAN.
Gaps in Pings Graph in Dashboard
Gaps in Pings Graph in Dashboard
List of servers/IPs