diff --git a/MISSING_FEATURES.md b/MISSING_FEATURES.md
index 1ab70ba..26f0b7b 100644
--- a/MISSING_FEATURES.md
+++ b/MISSING_FEATURES.md
@@ -11,18 +11,23 @@ Features not yet implemented in the Zig version:
 - Support transparency and custom styling
 - Requires image rendering library integration
 
-## 3. Multiple Locations Support
-- Handle colon-separated locations (e.g., `London:Paris:Berlin`)
-- Process and display weather for multiple cities in one request
-
-## 4. Language/Localization
+## 3. Language/Localization
 - Accept-Language header parsing
 - lang query parameter support
 - Translation of weather conditions and text (54 languages)
 
-## 5. Json output
+## 4. Json output
 - Does not match wttr.in format
 
-## 6. Moon endpoint
+## 5. Moon endpoint
 - `/Moon` and `/Moon@YYYY-MM-DD` endpoints not yet implemented
 - Moon phase calculation is implemented and available in custom format (%m, %M)
+
+## ~~Multiple Locations Support~~
+- Handle colon-separated locations (e.g., `London:Paris:Berlin`)
+- Process and display weather for multiple cities in one request
+
+This is advertised as a feature in wttr.in, but it does not work on the live
+site. Given that this would be an unbounded computational risk and a DOS vector,
+this is not going to be implemented. That can be done easily through a script,
+and it will allow the rate limiting to work better that way
diff --git a/README.md b/README.md
index 69ec4b8..ce3d305 100644
--- a/README.md
+++ b/README.md
@@ -92,9 +92,8 @@ Available preconfigured formats: 1, 2, 3, 4 and custom format using percent nota
 * `format=3`: `Nuremberg: 🌦 +11⁰C`
 * `format=4`: `Nuremberg: 🌦   🌡️+11°C 🌬️↓4km/h`
 
-You can specify multiple locations separated with `:`:
-
-**Note:** Not yet fully implemented - see [MISSING_FEATURES.md](MISSING_FEATURES.md)
+**Note:** Wttr.in claims that you can do multiple locations at one with a ':'
+          separator, but that does not appear to work
 
 ```bash
 $ curl localhost:8002/Nuremberg:Hamburg:Berlin?format=3