What is happening?
An updated synthetics runtime for public locations is planned to be released on April 7, 2022 that includes support for new versions of Chrome, Selenium WebDriver, and Node.js. Any new monitors created or monitors upgraded to use this runtime will use a new IP space.
These new IP address ranges have been added to our public IP documentation in a new IP range list document.
While this new IP space will initially only be used for new and upgraded monitors, all public ping, simple browser, certificate check, broken link monitors, and step monitors will start migrating to this new IP range on May 2, 2022. Migration timelines for existing scripted API and scripted browser monitors will be shared in the future.
Do I need to do anything?
- If the endpoint or webpage that your monitor checks is restricted, you’ll need to add the IP address ranges above to your allow list. This may include firewall rules, bot detection software, or similar configurations
- If your team allows traffic from any IP, no action is required.
How do I identify synthetic monitoring requests?
Synthetic monitoring requests include x-abuse-info request headers so that they can be easily identified.