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.
Outages flagged incorrectly as Internal.
-
This is for both 131123 and 131124, I have them setup to track my provider in two separate ways, allow me to explain.
131123 - Is on a Pi that's plugged into my home router, it shows repeated "Internal" alerts even though my home network is fine to the point to where I use an app to control my second machine from my first to share keyboard and mouse and it never has an issue. Almost all alerts show internal.
131124 - Is on a Pi with wireless connection straight to my ISPs modem. There is no internal to go down here, this is when the modem stops serving internet access, but I confirm with my third machine that the wireless itself stays functional, it has no route at the times denoted.
The time windows of outages are fairly close as you can see, but that makes that internal flag even more confusing if one agent hard wired behind a router and a wifi straight to modem with no home networking at all are showing the same outage windows.
Can you please check both agent logs and investigate why it is flagging things the way it is? 131124 is most confusing when there's nothing to go down but the modem.
-
I would suggest you take a look at the historical hops to understand why the system is assigning the outage to the internal (i.e. LAN) network.
The two devices are connected in different way to the router
My question is the 10.x.x.x network is the one of the provider router or is it still in your network? -
My setup is a bit odd as I'm trying to prove two separate ways to my provider that it's not the house wiring, my router, ect.
The 10.x.x.x is the DHCP pool from the modem, the 192.x.x.x is from the router which is why it is only seen on 131123.
-
Looking at hops on 131124, the second hop is not internal, the .1 is the gateway which means that second hop should be considered something else.
-
Alrighty, sounds good thank you. I think that will clear up what I'm seeing as confusion
-
I assume that change will not be retroactive?
-
Oh no, leave that as external as it's outside of my house's gateway. I mean the history is going to still show "internal" on those and only new events will reflect correctly?
-
On 131124 can we please change .1 to provider since it's the modem itself and no other network component?
-
Finally happened again, and it is incorrect
2024-09-27 04:05:05 - Down (10.0.0.1) for 7s (Internal) on 131124
-
Hi, just FYI, we'll take a look at this again on Monday and try to help out.
-
Checking in regarding this, happened again today.
2024-10-01 12:33:44 - Down (10.0.0.1) for 15s (Internal)
on 131124 -
-
Yes, 131124 is connected wirelessly directly to my provider modem as I covered in the very first post. 10.0.0.1 is the gateway IP from the modem.
First hops between 23 and 24.
131123:
2024-10-01 19:27:30 335 1 192.168.50.1 On your local network
2024-10-01 19:27:30 335 2 10.0.0.1 With your Internet provider <---
2024-10-01 19:27:30 335 3 10.61.79.194 With your Internet provider131124:
2024-10-01 18:53:00 334 1 10.0.0.1 On your local network <---
2024-10-01 18:53:00 334 2 10.61.79.194 With your Internet providerThis shows the discrepency between each agent, can we make them both match to say "With your Internet provider"?
If I need to detail that any further please advise what I missed in describing how both agents are configured.
