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.
Hardware Agent Setup
-
Hi,
Yes, this is the remaining view of the old style which we will also update soon.
After getting a little feedback over the past week about this we understood that it might not be as clear as it could be.
Our priority was the initial location and device selection when you install a new agent which we changed last week.
We then created an issue (work to be done, based on priorities) to do this one next.
You can see the new method if you go to your Agents view then create a new software agent. No need to complete the installation if you're just looking, leave it in Created status and it will be removed in 24hrs.
We can always improve how things work so long as we get feedback and input so appreciate this post.
-
The update to fix the Windows installer problem has been released. Simply create a new software agent which will give the download to the new version.
-
Hi,
We looked at your agent data and we think that the reports are wrong.
It's because in some cases, only humans can understand where your home starts/ends and where your provider starts.
In this case, it looks to us that most of the outages are in fact with your provider but there is no way for the agent to determine this without some input from a human.
This might explain a little better and seems to be something we need to explain, write about;
How is "beyond" determinedWe have been talking about adding manual ways for members to enter which devices they know are internal and which they know are external/provider so that the classification will be better.
When you cannot reach the Internet, you should still be able to reach devices on your own network as you said.
In your case and others, the problem is that the provider is either working with/under another network owner or has bought one or more companies and has not updated it's info to be the same company. The algorithm looks up IP and company info and determines partly what is outside of the building based on this information.
Unfortunately, in some cases, it isn't possible for it to know and it takes human intervention.
Having said all of the above… it looks like you have a router/firewall, then your providers router/modem then something else that is your provider.
Can you let me know what the setup is in terms of devices I've guessed above and we can go from there.
-
> Having said all of the above… it looks like you have a router/firewall, then your providers router/modem then something else that is your provider.
You've pretty much nailed it. We have a router (TP Link is the brand). It does some firewall stuff. Then there is a little widget on the wall that connects to the "Radio" that is on the outside of the house and that Radio communicates with a relay tower that relays to one of their actual towers. The "Radio" communicates wirelessly.
If I want to reboot the internal provider link, I unplug that widget and replug it in.
We also have a VOIP (OOMA) but it hooks directly into the router.
-
Thanks for confirming.
This is something we continue to try to improve. We're not done yet, we want that algorithm to get better when it comes to classifying the network segments between home/building, provider and beyond. We've got it working quite well with provider and beyond but it's quite the trick to try to decipher.
I'll speak with someone about this today since you can confirm your setup. Knowing this could help us do some testing.
-
> The update to fix the Windows installer problem has been released. Simply create a new software agent which will give the download to the new version.
FYI, I created a new software agent. Surprise, it actually auto-filled my address and got to the right place - whether that is because the hardware agent knows where it is or you have fixed something, I don't know.
Norton 360 REALLY DIDN'T LIKE the installer. Not sure if this is why it failed or not, should I retry. I know this is different from the setup error thread. But…
[5DE0:5430][2020-11-24T08:44:19]i001: Burn v3.11.0.1701, Windows v10.0 (Build 17763: Service Pack 0), path: C:\Users\lklawrie\AppData\Local\Temp{BF36D829-3A21-4B10-83A7-BE4F712CB6EA}.cr\Echo_Networks_Service_Installer_V1.62.2006_Release.exe
[5DE0:5430][2020-11-24T08:44:19]i009: Command Line: '"-burn.clean.room=H:\V108\Updates\Outages Internet\Echo_Networks_Service_Installer_V1.62.2006_Release.exe" -burn.filehandle.attached=716 -burn.filehandle.self=712'
[5DE0:5430][2020-11-24T08:44:19]i000: Setting string variable 'WixBundleOriginalSource' to value 'H:\V108\Updates\Outages Internet\Echo_Networks_Service_Installer_V1.62.2006_Release.exe'
[5DE0:5430][2020-11-24T08:44:19]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'H:\V108\Updates\Outages Internet'
[5DE0:5430][2020-11-24T08:47:46]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\lklawrie\AppData\Local\Temp\Echo_Networks_Service_20201124084746.log'
[5DE0:5430][2020-11-24T08:47:46]i052: Condition '(VersionNT64 > v6.1) OR ((VersionNT64 = v6.1) AND (ServicePackLevel >= 1))' evaluates to true.
[5DE0:5430][2020-11-24T08:47:46]i000: Setting string variable 'WixBundleName' to value 'Echo Networks Service'
[5DE0:5430][2020-11-24T08:47:46]i000: Setting string variable 'WixBundleManufacturer' to value 'Echo Networks LLC'
[5DE0:5D78][2020-11-24T08:47:46]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
[5DE0:5D78][2020-11-24T08:47:46]i000: Setting version variable 'WixBundleFileVersion' to value '1.62.2006.0'
[5DE0:5430][2020-11-24T08:47:48]i100: Detect begin, 2 packages
[5DE0:5430][2020-11-24T08:47:48]i000: Setting string variable 'NETFRAMEWORK40CLIENT' to value '1'
[5DE0:5430][2020-11-24T08:47:48]i052: Condition 'NETFRAMEWORK40CLIENT' evaluates to true.
[5DE0:5430][2020-11-24T08:47:48]i101: Detected package: NetFx40ClientRedist, state: Present, cached: None
[5DE0:5430][2020-11-24T08:47:48]i101: Detected package: EchoNetworksServiceInstaller.msi, state: Absent, cached: None
[5DE0:5430][2020-11-24T08:47:48]i199: Detect complete, result: 0x0
[5DE0:5D78][2020-11-24T08:48:02]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1
[5DE0:5430][2020-11-24T08:48:02]i200: Plan begin, 2 packages, action: Install
[5DE0:5430][2020-11-24T08:48:02]w321: Skipping dependency registration on package with no dependency providers: NetFx40ClientRedist
[5DE0:5430][2020-11-24T08:48:02]i000: Setting string variable 'WixBundleRollbackLog_EchoNetworksServiceInstaller.msi' to value 'C:\Users\lklawrie\AppData\Local\Temp\Echo_Networks_Service_20201124084746_000_EchoNetworksServiceInstaller.msi_rollback.log'
[5DE0:5430][2020-11-24T08:48:02]i000: Setting string variable 'WixBundleLog_EchoNetworksServiceInstaller.msi' to value 'C:\Users\lklawrie\AppData\Local\Temp\Echo_Networks_Service_20201124084746_000_EchoNetworksServiceInstaller.msi.log'
[5DE0:5430][2020-11-24T08:48:02]i201: Planned package: NetFx40ClientRedist, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None
[5DE0:5430][2020-11-24T08:48:02]i201: Planned package: EchoNetworksServiceInstaller.msi, state: Absent, default requested: Present, ba requested: Present, execute: Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: Register
[5DE0:5430][2020-11-24T08:48:02]i299: Plan complete, result: 0x0
[5DE0:5430][2020-11-24T08:48:02]i300: Apply begin
[5DE0:5430][2020-11-24T08:48:02]i010: Launching elevated engine process.
[5DE0:5430][2020-11-24T08:48:59]i011: Launched elevated engine process.
[5DE0:5430][2020-11-24T08:49:00]i012: Connected to elevated engine.
[64D4:06F8][2020-11-24T08:49:00]i358: Pausing automatic updates.
[64D4:06F8][2020-11-24T08:49:00]i359: Paused automatic updates.
[64D4:06F8][2020-11-24T08:49:00]i360: Creating a system restore point.
[64D4:06F8][2020-11-24T08:49:58]i361: Created a system restore point.
[64D4:06F8][2020-11-24T08:49:58]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{d01b8410-3a27-43f2-b492-963a9a8cf914}, options: 0x7, disable resume: No
[64D4:06F8][2020-11-24T08:49:58]i000: Caching bundle from: 'C:\Users\lklawrie\AppData\Local\Temp{573A228F-2780-47EA-A069-7EAAEDDEEE58}.be\EchoNetworksServiceSetup.exe' to: 'C:\ProgramData\Package Cache{d01b8410-3a27-43f2-b492-963a9a8cf914}\EchoNetworksServiceSetup.exe'
[64D4:06F8][2020-11-24T08:49:58]i320: Registering bundle dependency provider: {d01b8410-3a27-43f2-b492-963a9a8cf914}, version: 1.62.2006.0
[64D4:06F8][2020-11-24T08:49:58]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{d01b8410-3a27-43f2-b492-963a9a8cf914}, resume: Active, restart initiated: No, disable resume: No
[64D4:43B0][2020-11-24T08:49:59]i305: Verified acquired payload: EchoNetworksServiceInstaller.msi at path: C:\ProgramData\Package Cache.unverified\EchoNetworksServiceInstaller.msi, moving to: C:\ProgramData\Package Cache{AF6AACE3-C803-4D7D-B9CB-4F3B156CE57F}v1.62.2006\EchoNetworksServiceInstaller.msi.
[64D4:06F8][2020-11-24T08:49:59]i323: Registering package dependency provider: {AF6AACE3-C803-4D7D-B9CB-4F3B156CE57F}, version: 1.62.2006, package: EchoNetworksServiceInstaller.msi
[64D4:06F8][2020-11-24T08:49:59]i301: Applying execute package: EchoNetworksServiceInstaller.msi, action: Install, path: C:\ProgramData\Package Cache{AF6AACE3-C803-4D7D-B9CB-4F3B156CE57F}v1.62.2006\EchoNetworksServiceInstaller.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"'
[64D4:06F8][2020-11-24T08:50:40]e000: Error 0x80070643: Failed to install MSI package.
[64D4:06F8][2020-11-24T08:50:40]e000: Error 0x80070643: Failed to execute MSI package.
[5DE0:5430][2020-11-24T08:50:40]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[5DE0:5430][2020-11-24T08:50:40]i319: Applied execute package: EchoNetworksServiceInstaller.msi, result: 0x80070643, restart: None
[5DE0:5430][2020-11-24T08:50:40]e000: Error 0x80070643: Failed to execute MSI package.
[64D4:06F8][2020-11-24T08:50:40]i318: Skipped rollback of package: EchoNetworksServiceInstaller.msi, action: Uninstall, already: Absent
[5DE0:5430][2020-11-24T08:50:40]i319: Applied rollback package: EchoNetworksServiceInstaller.msi, result: 0x0, restart: None
[64D4:06F8][2020-11-24T08:50:40]i329: Removed package dependency provider: {AF6AACE3-C803-4D7D-B9CB-4F3B156CE57F}, package: EchoNetworksServiceInstaller.msi
[64D4:06F8][2020-11-24T08:50:40]i351: Removing cached package: EchoNetworksServiceInstaller.msi, from path: C:\ProgramData\Package Cache{AF6AACE3-C803-4D7D-B9CB-4F3B156CE57F}v1.62.2006\
[64D4:06F8][2020-11-24T08:50:40]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{d01b8410-3a27-43f2-b492-963a9a8cf914}, resume: None, restart: None, disable resume: No
[64D4:06F8][2020-11-24T08:50:40]i330: Removed bundle dependency provider: {d01b8410-3a27-43f2-b492-963a9a8cf914}
[64D4:06F8][2020-11-24T08:50:40]i352: Removing cached bundle: {d01b8410-3a27-43f2-b492-963a9a8cf914}, from path: C:\ProgramData\Package Cache{d01b8410-3a27-43f2-b492-963a9a8cf914}\
[64D4:06F8][2020-11-24T08:50:40]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall{d01b8410-3a27-43f2-b492-963a9a8cf914}, resume: None, restart initiated: No, disable resume: No
[5DE0:5430][2020-11-24T08:50:40]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart: No
Not sure whether to just try installing again or?
-
Hi,
There is a note at the top of the installation instructions, where you download the software that states this is not the final version and does not contain our author license. It is perfectly ok to continue the installation.
Once we see enough install to confirm that all is fine, we will generate a final update.
-
Nice, thanks for the update :).
-
Hi,
Never reset an agent, especially if there is an outage in progress.
The agent will always log IP outages so long as it was never disabled, restarted, lost power, etc. So long as there is in fact an IP outage happening, it will keep logging then sent its report as soon as it can reach the Internet again.
If you aren't seeing outages events in your reports, it means the disconnections are something else. The agent cannot know about other things like signal loss or a cable going bad, things like that. You should be able to check the provider side of the router/device they have installed at your location. In that device, there should be a log showing signal losses for example.
I'm a little confused with your mention of software, hardware and reports so lets make sure we are in sync.
The reports are the dashboard for your hardware or software agent.
There is where you would see 'disconnected' if the agent is no longer able to communicate with the OutagesIO network.
There is no reason to uninstall the software, those statuses are showing you the status of the connection/agent.
It sounds like by the time you re-installed, your Internet was back up and running since you would need to access your control panel to start a re-install process.
Let's try to get in sync so we can help out.
-
I have not reset the hardware agent – though it looks like it wants me to, occasionally. Or reboot.
The disconnected agent was the software agent. Stayed disconnected for 2-3 days -- regardless of internet / outages. It was not reconnecting, the service (Echo Networks) was running, internet was available so all I could figure to do was uninstall and reinstall the software agent. It is now active again but I have not rebooted this computer in over a day. (usually have to once a day) We can usually tell when we can't reach the internet -- either from the task bar on the computers or just not being able to reach.
I am unsure how to tell that the provider is out vs something else -- your hardware agent is telling me it's "inside" but I look at the router and it says it is not communicating with the provider widget that is inside the house. I don't know how to test the provider widget or radio, but I don't think the 300 outages I experienced before the agents were installed came from inside the house.
Not sure how to help you.
-
I have not reset the hardware agent – though it looks like it wants me to, occasionally. Or reboot.
Could you expand on 'though it looks like it wants me to'. Where do you see this, what makes you think that? When someone brings something like this up, maybe there is room for improvement on our part in terms of clarifying how something works.
The disconnected agent was the software agent. Stayed disconnected for 2-3 days -- regardless of internet / outages. It was not reconnecting,
the service (Echo Networks) was running, internet was available so all I could figure to do was uninstall and reinstall the software agent.
Thanks for clarifying. I suppose it's possible that the service could get stopped or blocked or something. I'd have to ask the Windows developer what could cause this kind of condition.
Any chance you kept track of which version it was? We replaced the previous version with a new one recently that is our fix to a recent installation issue that some were seeing. We'll eventually put out a final version once we've concluded that all seems fine.
I am unsure how to tell that the provider is out vs something else -- your hardware agent is telling me it's "inside" but I look at the router and
it says it is not communicating with the provider widget that is inside the house. I don't know how to test the provider widget or radio,
but I don't think the 300 outages I experienced before the agents were installed came from inside the house.
Yes, I think we talked about the inside vs provider algorithm not being able to auto determine in some cases when private IPs are being used for the few few hops. With your extended reports which adds the historical menu and hops history, it can help you to determine which hardware is which hops.
With that, even if the overall report or classification is saying 'inside', you'll know which are in fact with the providers device at your location, or beyond and inside your providers network.
Not sure how to help you.
It's ok, I'm trying to help you. That's why we wanted to make these forums available, so that we could communicate with members, get some feedback, input which we can use to improve all parts of the service. Some things work well, some things work but need improvement. It's a process.
-
This is going to come in several posts…
> Any chance you kept track of which version it was? We replaced the previous version with a new one recently that is our fix to a recent installation issue that some were seeing. We'll eventually put out a final version once we've concluded that all seems fine.
Software agent - the recent version as I could not install the earlier version. (One of "those" people. :D ) V 1.62.2006
-
> Could you expand on 'though it looks like it wants me to'.
Where do you see this, what makes you think that? When someone brings something like this up, maybe there is room for improvement on our part in terms of clarifying how something works.
So the alert area says the agent is inactive (or maybe it is the alert that is inactive) and the button on the right is "reset".
I don't know if that resets the alerts or the whole agent.
-
Ah, it all comes together now, thank you for sharing that.
Ok well, with Extended reports, you get dashboard alerts as well as email notifications.
What's happened is that you have alerts enabled so you are seeing past events and not something that is currently happening.
The dashboard alerts are usually used by IT people and organizations that manage many locations and they also get an overview map. The map shows them if there are any agents that recently had problems. The admin for that location looks into the problem and has to enter what they did to resolve the problem into the alert. The alert remains until someone has seen or dealt with the problem so that there is a historical trail of what's been done.
So, nothing is wrong, you can see your Heartbeat is green, which means your agent is running as it should be.
In your case, you don't need to enable any dashboard alerts as emails or logging in on a regular basis will do the job for you.
A challenge that we are constantly facing is that of how to explain everything to everyone. It's something we keep trying to figure out. The more features we add, the more complex the service becomes and unfortunately, a little hard to understand at times. Most pages have a 'About this page' button near the right hand top that leads to a forum post explaining that particular page, what the different features mean and how to use them.
I hope this explains and helps.
-
Hi,
In your second image, looking at the DNS entry, the record for your 126919 is correctly pointing to the public IP that you have where it is installed. However, you don't seem to have anything that is reachable at that IP so the browser is not getting a response from anything. Normal.
In your first image, it looks like you are experiencing DNS failure from your provider. Did you know what your agent has its own DNS service built in?
The hardware agent contains its own DNS server/service to give you not only privacy from your provider but also as a secondary/redundant DNS service should your providers become unreachable.
Looking at your agent, it's LAN IP is 192.168.1.201. If you make one of your DNS entries that, you'll have some DNS redundancy.
Other than this, our service doesn't interfere with your Internet service in any way at all. The agent acts just like anything else on your local network, just a simple client that communicates back and forth with our network.
If I am not understanding, please continue with more information and we'll try to help.
