Our FREE software monitors your Internet service and provider then alerts you when you have connection issues or downtime. For home, small business, IT companies and enterprise. Monitor Internet outages, track network connection reliability, and get proof you can use. For Windows 7, 8, 10, Centos 7, 8, Debian 7, Ubuntu, ARM (Raspberry, Tinker Board, etc).
Known to run on
1.67.2104 / 1.67.2106
(ARM 64) Cortex-A53, Pi 3A, 3B+, 4,
GL.Inet AR150, AR300
, 4MB TP-Link TL-WR703N
Centos, Debian, Ubunut 7,8
OutagesIO Hardware agent
7,8,All versions of 10 if fully updated
This post is a work in progress in wanting to come up with a useful matrix explaining the various versions that we offer and the differences between each.
This post should not be used as correct information at this time until this notice is removed.
Are Internet problems in your local network or with your Internet provider? Don’t waste countless hours, let Outages help! Shows issues with YOUR Internet connection AND neighborhood. Gives you hard FACTS on what’s REALLY happening, reported or not.
Let me try to summarize what I see and lets check together if there is a clear explanation.
Lets start with the inventory:
128389, SW agent (Win 10 Pro), OTM version 1.69.2106
128316, SW agent (Win 10 Enterprise), OTM version 1.69.2106
128309, SW agent (Win 10 Pro), OTM version 1.69.2106
128313, HW agent (GLinet MT300N-V2), OTM version 1.67.2104
Upload testing + Latency evaluation is available only from version 1.68.2105 and on the HW version we are still testing so this explains why you are not seeing the uploads on the HW agent: as soon as the testing period is over we will release the latest version and your agent will upgrade automatically.
As far as I can see:
agent 128309 was able to send proper download/upload/latency from Sep 20th when the version 2106 was installed
agent 128316 was able to send proper download/upload/latency from Sep 11th when speed-test was enabled
agent 128389 seems to be the tricky one since it started from yday right after 3 am
The only thing we noticed is that some old Windows 10 builds were blocking some features of the OTM (the software that does the monitoring) and maybe (it is just an assumption) that pc/server was updated to the latest build.
Can you please double check that so I can have a better understanding of this weird behavior?