# Specific Wayspot (VPS Activated) is broken. VPS-Activated Waypoint Not Appearing in Scaniverse VPS Map

**URL:** <https://community.nianticspatial.com/t/specific-wayspot-vps-activated-is-broken-vps-activated-waypoint-not-appearing-in-scaniverse-vps-map/5634>\
**Category:** I'm Stuck\
**Tags:** vps\
**Created:** [December 2, 2025, 9:08am UTC](https://community.nianticspatial.com/t/specific-wayspot-vps-activated-is-broken-vps-activated-waypoint-not-appearing-in-scaniverse-vps-map/5634 "2025-12-02T09:08:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fortiz](https://avatars.discourse-cdn.com/v4/letter/f/7c8e57/32.png) [@fortiz](https://community.nianticspatial.com/u/fortiz)\
**Post date:** [December 2, 2025, 9:08am UTC](https://community.nianticspatial.com/t/specific-wayspot-vps-activated-is-broken-vps-activated-waypoint-not-appearing-in-scaniverse-vps-map/5634/1 "2025-12-02T09:08:53Z")

</div>

_Include the following details :_

- **Issue category** : Lightship Maps / Semantic Segmentation / Multiplayer / VPS / Scanning Framework / Ingress
- **Device type & OS version** : Android / iOS
- **Issue Environment** : Ingress, Scaniverse, Spatial Browser

**Location-ID** : af2abc604cd03d4b8bb67864853afd55.16  
**Location** : Johann-Jacob-Engel-Straße 14, 13057 Berlin, Germany  
**LatLng** : 52.572829, 13.558266999999999

_ **Why do I write here and not in Ingress?** _  
_The waypoint (VPS Activated “Production”) does not appear as VPS in the Scaniverse app, so this seems to be an issue with the waypoint itself rather than an Ingress-related problem._

**Description of the issue:**

I have a waypoint that I successfully activated for VPS through a large number of high-quality scans. Test scans work without any issues, and in the Geo-Spatial browser the waypoint shows up correctly as VPS-activated.

However, the same waypoint does **not** appear in the Scaniverse VPS map.

Additional details:

- Even a **Reactivate** attempt does not work.

- Other waypoints can be activated or reactivated without problems — only this one fails with an error.

- This makes me suspect that the waypoint might be corrupted or incorrectly tagged on the server side as an activated VPS object.

**Expected behavior:**  
A VPS-activated waypoint should appear in the Scaniverse VPS map and should be scannable/reactivatable in Ingress.

**Actual behavior:**  
Waypoint appears in the Geo-Spatial browser but not in Scaniverse, and Ingress scanning/reactivation fails every time.

**Request:**  
Please check whether this waypoint is incorrectly tagged, corrupted, or stuck in an invalid VPS state and correct it on the backend.

 ![spatialsupport](https://us1.discourse-cdn.com/niantic/original/2X/2/2d775614cfbf999ca3f5fc06f6d722d1a9a9cb0d.jpeg)

---

<div class="post-metadata">

**Author:** ![fortiz](https://avatars.discourse-cdn.com/v4/letter/f/7c8e57/32.png) [@fortiz](https://community.nianticspatial.com/u/fortiz)\
**Post date:** [December 15, 2025, 2:20pm UTC](https://community.nianticspatial.com/t/specific-wayspot-vps-activated-is-broken-vps-activated-waypoint-not-appearing-in-scaniverse-vps-map/5634/2 "2025-12-15T14:20:36Z")

</div>

Is it possible that the VPS-Activated Waypoint conflict with that rejected one?  
What does “Rejected” mean here?

The Activated one:  
LocationId: af2abc604cd03d4b8bb67864853afd55.16

> **[Niantic Lightship](https://lightship.dev/account/geospatial-browser/52.57281499999999,13.558264000000008,15.43,6AD160F467154B748A72EB976903E0A4,af2abc604cd03d4b8bb67864853afd55.16/scan-wayspot)**
>
> We are empowering creators to seamlessly and realistically bring AR experiences into the real world, at a global scale.

LocationId is different: ba8994965ce0373aaa41331d97b5a01b.16

> **[Niantic Lightship](https://lightship.dev/account/geospatial-browser/52.57281499999999,13.558264000000008,15.43,,ba8994965ce0373aaa41331d97b5a01b.16/scan-wayspot)**
>
> We are empowering creators to seamlessly and realistically bring AR experiences into the real world, at a global scale.

 ![image](https://us1.discourse-cdn.com/niantic/original/2X/3/31e8330b36cc3145ada9423a7a90f466cc31dbf3.jpeg)

---

<div class="post-metadata">

**Author:** ![Maverick\_Niantic](https://avatars.discourse-cdn.com/v4/letter/m/8edcca/32.png) [@Maverick\_Niantic](https://community.nianticspatial.com/u/Maverick_Niantic)\
**Post date:** [March 5, 2026, 9:21pm UTC](https://community.nianticspatial.com/t/specific-wayspot-vps-activated-is-broken-vps-activated-waypoint-not-appearing-in-scaniverse-vps-map/5634/3 "2026-03-05T21:21:19Z")

</div>

Hi fortiz,

I sincerely apologize for the delay in response.

After further review, this behavior is functioning as intended on our end, as Ingress portals are no longer designed to appear on the Scaniverse map.

For further assistance with Ingress-related issues, please reach out directly to Ingress support here:  
[https://support.ingress.com/hc/en-us/requests/new](https://support.ingress.com/hc/en-us/requests/new)

Kind regards,  
Maverick L.

---

<div class="post-metadata">

**Author:** ![NianticSpatial](https://avatars.discourse-cdn.com/v4/letter/n/49beb7/32.png) [@NianticSpatial](https://community.nianticspatial.com/u/NianticSpatial)\
**Post date:** [March 6, 2026, 7:08pm UTC](https://community.nianticspatial.com/t/specific-wayspot-vps-activated-is-broken-vps-activated-waypoint-not-appearing-in-scaniverse-vps-map/5634/4 "2026-03-06T19:08:43Z")

</div>

Closed on March 6, 2026, 7:08pm UTC


