---
title: IPv6, port-25 and browser checks only run from locations that can do them
description: A monitor forced to IPv6, or pointed at an IPv6-only host, could be given a location without IPv6, and an SMTP check on port 25 a cloud location that blocks…
canonical: https://watchfor.io/changelog/2026-11-17-location-capabilities
---

[All updates](/changelog/page/3#2026-11-17-location-capabilities) ⚡ Improved Nov 17, 2026 · v 12.5.5

# IPv6, port-25 and browser checks only run from locations that can do them

A monitor forced to IPv6, or pointed at an IPv6-only host, could be given a location without IPv6, and an SMTP check on port 25 a cloud location that blocks port 25. The check then failed there and could open a false incident. Every location now measures what it can do (IPv6, port 25, a working browser), and the picker greys out the ones that can't run your monitor, with the reason. Saving with one is refused in the dashboard, API, MCP and imports. If no location can run a monitor right now, its page says so and Run now explains why.

Share this update

---

Canonical page: https://watchfor.io/changelog/2026-11-17-location-capabilities · Site guide: https://watchfor.io/llms.txt
