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.
7m outage noted as Internal when it shoud have been Provider
-
2.1 is my router that is connected via ethernet drop to my ISP. No separate firewall is in the mix here.
-
So the router has a LAN and a WAN port: LAN is xxx.xxx.2.1 and WAN ?
Does it have an IP in the xxx.xxx.88.xxx network? -
Yes, LAN is 2.1, WAN is DHCP from ISP.
-
What Is My IP?
My Public IPv4:
192.182.88.71My Public IPv6:
Not Detected
My IP Location:
Patterson, CA USMy ISP:
Frontier Communications of America Inc.Not sure what the xx.42.148.201 address is.
-
Hi,
As an update, after a lot of testing, we believe the bug has been identified.
An internal test version will be created today and if confirmed as solving the problem, will become available on the site. -
What will I have to do if the bug resolution is confirmed?
-
Windows users would use the dashboard to re-install the software.
All others, it's an automatic update the next time the device downloads the agent.
We always suggest restarting the agent every 24 hours. -
I am running the software agent on Linux. You really suggest an agent restart every 24 hours? Is the restart necessary to update the agent? I have not automated the running of the agent. Can you remind me how to restart the agent service on Ubuntu? Thanks!
-
This is a post on how to turn it into a service.
https://www.outagesio.com/monitor-your-internet-with-linux-desktop-or-server/Then you can use a cron job to auto restart the service every X that you'd like. You don't have to auto restart it, this is a precaution we used to take because Windows machines used to have memory issues now and then so restarting the service was just a way to make sure the agent didn't get caught up in that.
We automatically reboot our hardware agents, just as a precaution and to make sure they pick up the lastest agent if there's been an update.
-
I don't want to make it a service at this point. What is the command to restart the agent?
-
There isn't one. You just kill the process then run the starter again.
-
that's what I am asking, remind me of the starter command. Sorry if my wording wasn't correct.
-
I'm not quite following.
When you created and installed the script in your preferred directory, you simply made it executable, and then ran it, ./starter.sh (or what-ever it's called)Now, just run 'ps aux' and look for the process ID that is the otm agent running then use 'kill -9 xxx', with xxx being the process ID. Make sure you only have one otm agent running of course.
When you're sure none is running, just run the starter again;
./starter.sh &&
That should be it.
-
As an update, please know that we are working on this problem and are testing it now.
It takes a while because we need to see real outages and other events occur. -
If you are interested, we have a test version available.
Please see this post;
https://support.outagesio.com/topic/287/dec-10-2023-agent-test-version-released-v1-80-2303 -
How do I utilize this test version? Agent ID is 130562
-
Linux will be a little harder to test. You might want to wait until we get a final version fix, then your script will automatically update when you kill it and start it again.
-
Yes, I will then wait for the final version fix. Please let me know when available, thanks!
-
Just check the app site or emails, it will be mentioned in there once it's out but someone will try to update this post too.
