Sign inStart free

nuvem.team checks traffic

Version 1 · Last updated: October 30, 2026

This page is for whoever runs a server, a website or a service and saw requests with the nuvem.team-checks User-Agent in the access logs. It explains what that traffic is, why it reached you and how to ask for it to stop.

1. What it is

nuvem.team is an on-call, alert management and incident response platform offered by NUVEM.ONLINE LTDA ("Nuvem.Online"). One of its features is checks: calls the platform makes from time to time, at an organization's request, to find out whether an address is still responding. When the address stops responding, nuvem.team notifies that organization's on-call team.

2. How to recognize it

The HTTP and HTTPS requests from checks carry this User-Agent:

nuvem.team-checks (+https://nuvem.team/check-traffic)

What follows the name is the address of this page. Filtering the access log by User-Agent finds every nuvem.team check result, and only those.

  • HTTP or HTTPS check: a request to the registered address, with the method, headers and body the organization configured, and a reading of the response to verify the status code and, if the organization wants, a keyword.
  • TCP check: a connection attempt to the registered address and port. As there is no HTTP request, there is no User-Agent.

Checks go out from the IP address 159.112.184.255, which you can allow in your firewall. If it changes, this page is updated before the change. To identify the traffic, use this address or, for HTTP and HTTPS checks, the User-Agent.

3. Why you receive this traffic

Because an organization that uses nuvem.team registered your address as the target of a check, usually to watch its own service, which may be hosted or served by you. nuvem.team doesn't look for addresses on its own: each check exists because an organization created it, and the organization may only point a check at an address it manages or is authorized to monitor.

Checks only reach addresses on the internet. The platform refuses private networks, loopback, cloud metadata addresses and their equivalents, and repeats that verification on every redirect.

4. How often

The frequency is the one the organization configured, within its plan's limit. After a failure, the check retries at a short interval, to confirm whether the address is down or it was a network hiccup.

5. How to ask for it to be blocked

If you don't recognize the traffic, or don't want to receive it, write to contato@nuvem.online and include:

  • the address (domain, URL, or host and port) that is receiving the check results;
  • the User-Agent, or a line from the access log with the date and time.

We review the request and, once it is confirmed that the address is yours, we stop running checks against it.

If the use looks abusive, such as a check pointed at a third party's system without authorization, use the same contact. The Terms of Use forbid monitoring, probing or attacking third parties' systems without the permission of whoever manages them.

6. More information

Talk to the team