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.
Rebooting
-
We've had a solid build since yesterday. If testing continues well tomorrow, we'll be shipping first thing next week.
-
At this point, we'll be shipping replacements as of Monday.
We've repeatedly tested every possible thing we could and feel confident that these should be reliable.
The caveat is, we've been trying to hurry and it's always possible we missed something small. As long as we can send them updates, we should be able to solve any issues.
Thank you for your patience.
-
Hi,
Did you get your replacement yet? We shipped replacements using high priority.
-
That's odd, they went out priority.
Let me find the tracking and go from there. -
Update here when it's done so I can have your data moved over unless you don't care. If you don't care, then I'll just assign the new one to your account as soon as it's online. Just let me know what the ID is. It should be a sticker on the side.
-
Is the ID the same on both?
-
Thanks for checking. Let us know when it's online.
-
If it's blinking, it doesn't seem to be getting a DHCP IP address from the uptream. We don't see it communicating yet. After a short boot, the red LED should be solid.
Can you log into your router/firewall to see if it's getting an IP?That's something we'll change with a remote update in the future.
-
I know these were tested repeatedly so it should work right out of the box.
I do see that it communicated at 2024-02-24 15:10:07 but no more after that. I'll have to ask a dev for help. I'm not sure why it's not working but I do see that it tried.
He's away right now but I'll send a message and hopefully hear back soon.
-
There must be something I'm not seeing while waiting for the dev. I can see the others communicating and all of these are using the same firmware. Can you look at your DHCP server and let me know what the MAC address is please?
Also, do keep it connected to the LAN port.
-
Is it possible that you put the old agent back online and not the new one? The one communicating seems to be using the old files that were on the original one we sent you.
There are two ways to solve this quickly.
First, put a sticker on one so you're 100% sure which is which.
Take one agent, connect it (LAN port) then let us know so we can check. Note the MAC address from your DHCP server and share that here in messaging. If that one does the same, we'll have you swap it for the other one.Second, if neither works, if you could give me emergency ssh access to it, we can fix it remotely so long as we can reach the replacement. If we're not 100% sure which is which, being able to log in will tell us immediately.
To give us ssh access, you would need to forward port 22 on your router/firewall to the device from an IP that we would provide. Or you can simply open port 22 temporarily.
This will save having to ship stuff back and forth and get this online for you asap. I will send you a private message after this.
-
You have me questioning if I did use the new one. Assuming I'm right, when the "new" one is connected, there's a solid red light in the front but no green light under LAN. My router sees it. When I replace it with the "old" one, the red light keeps blinking and there's a green light under LAN. My router doesn't see it. I'm pretty sure I know which one is "new" as I noticed that there was no green light (as opposed to "old" one.) The "new" MAC address is 22:3B:87:07:1A:83
-
Ok, now, your agent connected and ran for a while then it went disconnected again.
The one with MAC address 22:3B:87:07:1A:83 should be the correct one but the one that connected seems to be the old one that we were replacing as it has MAC 12:0A:AB:80:66:01.
There is definitely some sort of mixup happening.
Can you make sure the one with the first MAC address is connected please.
