Information and Support

Thanks. I disconnected elsewhere in my local network, and that IS logged correctly. So it is all working as expected then.

Mike

Agent 127083

I have disconnected the local cat5 connection for several minutes several times, and also rebooted the device. These are all registered by gaps in the heartbeat and ping, but nothing is reported in the other graphs.

I have (I think) successfully updated my Linux client to the latest version

OTM version 1.62.2006

and am getting heartbeat/status and pings, which correctly indicate when I deliberately disconnect the network connection, but nothing is shown under "breakdown..." , "my outages" and "when are most...".

Under recent events I just see when I first started it and when it last got reconnected, but nothing else.
I.e.
Agent communications

2022-04-09 08:19:38: Agent is sending updated hops to OutagesIO.
2022-04-08 16:07:46: Agent is now communicating with OutagesIO.

So have I got something wrong, or are these no longer available in the free service?

@mikeshand consistently getting error with "remember" ticked and working fine without in both chrome and safari.

@SBK yes I just check this morning. With remember me checked I get the error. Without it worked fine.

@SBK ok this is really weird. If I logout (and make sure I have no other tabs that are logged in) then I can login again just fine.
I can even login from safari ( I previously used chrome).

@SBK that works fine.

@SBK
I just tried going to outagesio.com choosing the get started drop down and selecting user control panel and tried to login..
I got the gateway error.

I did it again in a new window.

Same thing.

So I copied your first link into a new window and bingo I was able in!

So https://app.outagesio.com/ doesn't work, but https://app.outagesio.com/agent/manage

Does.

Thanks. I'll report back after a few days.

The first link takes me to a login page where I can type in my credentials and I get to my dashboard just fine.

The second link takes me to the notifications page and from there I can move back to my agent with no problems.

If I then logout I can now login again from the usual place.

I'm totally perplexed. Something to do with browser caching?

If I now try from DuckDuckGo it works fine from there too.

So something seems to have sorted the problem.

The new password gives the same gateway timeout error for me.

Sorry, messages crossed. Yes go ahead and force change the password.

Well that's interesting. I've managed to get the password reset email and reset it to the same password. It then automatically logged me in and I could see my dashboard.

So I logged out and tried to login again and I am back to getting the error!

Still get the same error when attempting to login to my own account, BUT strangely I CAN login to the demo account! So is it some problem specific to my account?

I tried to do a password reset both using my email address and my username and in both cases it said it had sent a reset to my correct email address (so it knew the correspondence between the two) but nothing has arrived after 10 minutes, and yes I have checked my spam.

Unable to login to the dashboard for at least 5 hours this morning using various browsers. I got in once on Sunday, but mostly got the same error.

Gateway Timeout

The gateway did not receive a timely response from the upstream server or application.

You announced a few weeks ago that you were stopping logging beyond your provider outages. I’m still getting these. Have you not done this yet or do I need to upgrade my agents first?

Many of the outages I am seeing by getting emails are not being logged in the dashboard. Is this because they are very short duration? The ones that are logged are usually in Denver 10 hops away, which is not of any concern.

Sounds great. Keep up the good work.

thanks. Understood.

Our main priority with monitoring speed is the upload speed for live streaming church services, so I was wondering if you had any plans to support testing this. Or is it technically difficult?

Thanks

Unfortunately it still seems to be reporting that second hop failure as “beyond”

2020-11-11 23:09:05: Outage occurred lasting 1 minute 11 seconds , indicating a problem beyond your internet provider.

2020-11-11 22:58:55: Outage occurred lasting 1 minute 9 seconds , indicating a problem beyond your internet provider.

2020-11-11 22:16:18: Outage occurred lasting 1 minute 14 seconds , indicating a problem beyond your internet provider.

And these are for hop 2 64.24.254.203 and 204 this time

Did I have to reset something to make the new algorithm work?