Hi. I am testing out the agents at a couple customer sites to see how they work. One specific site would work for 30 seconds and then stop reporting and go offline indefinitely. I could still see requests from the agent going out to 184.164.141.219 and 66.85.130.2 over the http port on the network firewall. For some reason today after I restarted the echo service on the host machine it started working again. I will keep an eye on it. I am hoping to get more information about how the echo service/agent works so I can better troubleshoot in the future if this information is available I would gladly appreciate it.

@OutagesIO_Support
The problem Agent 130067 is running on Windows Server 2019 Essentials
The below are working:
Agent 130066 is running on Windows Server 2019 Datacenter
Agent 130072 is running on Windows 10 Pro 21H2
Agent 130071 us running on Windows Server 2012R2

@OutagesIO_Support It was already running, have restarted the service, I expect it to work for the next 30 seconds

@EchoMin I can ping from that computer:
Pinging 66.85.130.2 with 32 bytes of data:
Reply from 66.85.130.2: bytes=32 time=83ms TTL=51
Reply from 66.85.130.2: bytes=32 time=84ms TTL=51
Reply from 66.85.130.2: bytes=32 time=75ms TTL=51
Reply from 66.85.130.2: bytes=32 time=85ms TTL=51

Ping statistics for 66.85.130.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 85ms, Average = 81ms

C:\Users\Administrator>

I have tried multiple computers on that network and they acted the same way with the agent so its definitely something on that local network. I just don't know how I would go about troubleshooting where the communication is getting broken.

@EchoMin Agent was restarted on 2023-02-08 10:13:24.
Last communicated on 2023-02-08 16:36:21.

@marcuscommunications
This is what I see on our firewall for traffic coming from the agent and going out to what I assume is the Outages IO reporting server.

@SBK
Hi,
130067 is disconnected currently. I installed with admin rights. What do you see on your end? I don't see anything blocked on our end.

@OutagesIO_Support The agent ID is 130067

Hi. I am testing out the agents at a couple customer sites to see how they work. One specific site would work for 30 seconds and then stop reporting and go offline indefinitely. I could still see requests from the agent going out to 184.164.141.219 and 66.85.130.2 over the http port on the network firewall. For some reason today after I restarted the echo service on the host machine it started working again. I will keep an eye on it. I am hoping to get more information about how the echo service/agent works so I can better troubleshoot in the future if this information is available I would gladly appreciate it.