Synthetic Monitoring FAQs

You can find the IP addresses on the Synthetic Monitor reference page

Monitoring from infrastructure that is separate from where your application is hosted gives an unbiased perspective of your application health and performance, resulting in a more realistic picture of application availability and end-to-end performance for end-users.

Currently newly created monitors take ~2-3 min before

The TLS monitor report will always source from US-EAST-1 within the reference page. This will be the case regardless of what regions the performance and health monitors you have running are set to.

The TLS report for a given HTTPs monitor is generated one time every 24 hours.

The overall TLS score comes from the SSL Lab's Server Rating Guide. You can view a detailed explanation of the specification here.

Monitor Executions represents the number of individual times a monitor has been run across all configured regions. The 3 factors that determine the monthly consumption for a monitor are:

• Number of Regions for the monitor
• Interval of the Monitor in minutes

Formula: (1440 (Minutes in a day) / <interval>) * (<Number of regions>) = Executions per day

Monitor Executions per interval per day:

Examples for a single monitor using a 1 min interval:

• 1440 (executions per day) x 1 Region x ~30 days in a month = 43,200
• 1440 (executions per day) x 3 Regions x ~30 days in a month = 129,600

Examples for a single monitor using a 5min interval:

• 288 (executions per day) x 1 Region x ~30 days in a month = 8,640
• 288 (executions per day) x 3 Regions x ~30 days in a month = 25,920

The base Organization plan includes 500,000 Synthetic Monitoring executions per month. For usage over the included 500,000 executions per month, please reach out to your account team for more information.