The usual way is you let each device get an IP from the upstream DHCP server and as you see them, you note their MAC address and the agent ID. Then you can associate those together to know which agents are which.

2026-02-27 11:25:10 - Down (142.254.184.109) for 1m 38s (Provider) 2026-02-27 10:53:14 - Down (142.254.184.109) for 8s (Provider) 2026-02-27 10:04:39 - Down (142.254.184.109) for 55s (Internal) 2026-02-27 09:44:39 - Down (142.254.184.109) for 2s (Internal) 2026-02-27 09:09:04 - Down (142.254.184.109) for 3s (Provider) 2026-02-27 08:00:44 - Down (142.254.184.109) for 6s (Provider)

Email sent.

Ok, let us know if you need anything else. Thanks for using our service.

Yes, it can be closed, thanks

Is this solved now?

Any news on this?

LOL All fine, and let me say that thanks to you we were able to identify an error, so please keep up sharing: we need feedback like this

This has been done. SMS counts are now across however many agents someone has. Please let us know if this is all ok now and we'll close this question.

The second problem was an SSL certificate that didn't get renewed in time. Automated things sometimes break when other companies change things. It's fixed too now.

Let me first ask if I am interpreting correctly your setup... For what I see you are asking the service to check every 15 minutes if the TCP port 65201 goes down and in the historical section you don't have any report. If my interpretation of the setup is correct then I confirm that no error has been found so far, i.e. port 65201 never went down from the moment you set it up.

After talking about it, we cannot take the chance of raising the number of emails because email sites will block us every time there is a huge outage with lots of emails being sent at the same time. This is why we limit the emails. That said, we've decided to re-design our SMS option so that all members can use that to receive notifications. Currently, only organizations that monitor dozens to thousands of locations get this by default so we have to review how we can do this for regular members. It will be announced as soon as it becomes available, possibly days to a week or so.

@Custom-Software Thank you very much for taking the time to let us know this. Every now and then, a certificate can be overlooked, especially when automated updates fail for any reason.

As far as I can see there has not been any Internet outages otherwise they will appear listed. There are other reason why you could experience a missing internet connectivity but no internet outage is recorded like for instance coaxial cables issues or fiber optic malfunctioning, wifi connectivity Can you please identify a specific moment in time in the past 30 days or from now on where you are experiencing a missing Internet connectivity but the agent doesn't "recognize" it as an internet outage?

Sorry but this post was not in the email alerts :-( Can you please tell me which agent ID ?

Yes, that would work but we have to do that in chat please. I'll go ping you there.

Thank you!

Thank you for your patience and for highlighting a behavior we had to fix

Two things: anytime the agent reboots (this happens once everyday at 3:00 am UTC) it will start from wired and then will move to wireless i.e. you will always need a wired connection for the agent you can switch from wired, wireless or AP anytime from the same configuration menu