- Probe Server Types
- Probe Server List
- Checking the Status of Uptime.com's Public Probe Servers
- Using Custom Secret Headers to Allow Uptime.com Traffic
Uptime.com's Probe Servers are the individual servers in our Global Locations, which are assigned and configured as needed for Uptime.com monitoring checks. The Probe Servers also include “AUTO & TEST” types which we will explain below.
Please note: Uptime.com provides a list of IP addresses to allow you to make sure all relevant probe servers (the locations you intend to use) are whitelisted in your WAF or CDN. This reduces false positives by ensuring our probes are able to establish a connection with your website or resource.
Probe Server Types
There are three types of Probe Server Locations: AUTO, TEST, and Global Locations (such as US East, United Kingdom, etc).
AUTO
The AUTO Location is the set default Location for checks that run at a predefined interval, such as once per hour checks (SSL Certificate Expiry) and once per day checks (WHOIS/Domain Expiry, Malware/Virus, and Domain Blacklist). The results of these checks do not change from different locations around the world since they are looking up the same data source.
TEST
TEST Locations are used by the Run Test feature, which manually tests and confirms that check configurations are working. Different check types may use different TEST locations.
There are a few probe servers of this type, so make sure all are whitelisted.
Please note: Basic check types can use any individual probe server for the Run Test function. Transaction and API checks are limited to the dedicated TEST locations.
Global
Global Locations are the publicly accessible monitoring Locations for selection on your Uptime.com checks. These are globally distributed to make sure that all endpoints and customer bases can have a nearby source of monitoring. Please note that the Global Locations and Probe servers are individual and use different ISPs to provide real client like monitoring and reduce false positives.
For internal or secure monitoring needs, we offer Private Location Monitoring.
Probe Server List
The Public Probe Server page provides a full list of servers we use to monitor all checks configured within your account. Click Probe Servers in the main menu to view the Public tab, which includes the full list.
On this page, you will see there is a filter option, where you will be able to filter out the probe servers by:
- Regions: Filter out probe servers by a specific region
- Location: Filter out probe servers by a specific location
- Tier: Filter out probe servers by a specific Tier
You will also see a search bar, where you can search for any desired probe server location.
Users have the option to export a CSV list of the available probe servers by clicking Export. The number of probe servers available for the checks you configure may vary based on the account's subscription level.
Users can also access the probe server list from the add/edit check screen, as depicted below:
For more information on when Uptime.com will alert you, you may want to review our documentation on Sensitivity and Retries. For any other questions, contact support@uptime.com.
Checking the Status of Uptime.com's Public Probe Servers
In addition to the primary Status Page, Uptime.com also operates a separate Status Page specifically for reporting on the health of the probe servers used to monitor your checks. Access the Public Probe Server Status Page at https://probestatus.uptime.com/.
Using Custom Secret Headers to Allow Uptime.com Traffic
As an alternative to whitelisting Uptime.com's probe servers for the purpose of allowing traffic to reach your endpoints, you may choose to utilize a custom secret header and value, for example:
X-Uptime-Monitor: SecretToken1234A rule can then be created in your organization's WAF settings that allows requests from our monitoring service that contain this header. This eliminates the need to whitelist our probe servers and keep your whitelist records updated.
Comments
0 comments