Skip to main content
Question

Request to have an illegal segment/route removed from my private property

  • December 16, 2025
  • 3 replies
  • 31 views

Forum|alt.badge.img+1

Hi,

I’m experiencing the likewise issue as below link and would appreciate guidance.

 

A private road on my property is still routable on Strava, even though it is correctly tagged as access=private in OpenStreetMap. 

Despite multiple support tickets, the issue has been repeatedly closed without comment, and routing continues to direct users through my property. This has resulted in repeated trespassing.

 

My question to the community (or Strava moderators) is:
Is there any way to request a routing geofence or routing block for private property when OSM is already correct, but Strava routing still allows it?

Any advice from others who have dealt with similar situations would be appreciated.
 

3 replies

Jan_Mantau
Superuser
Forum|alt.badge.img+27
  • Superuser
  • December 16, 2025

Strava uses partly mapbox instead of OSM. You can try to inform mapbox that this road is private:

  • In the webbrowser open the “Maps” in Strava
  • Click on the (i) in the bottom right corner and then “Improve this map"
  • Go to your private road and press long with the left mouse button to contribute
  • From there you have some options, I don’t know which is better: You can use “Add road” and set the access restrictions to private or you can use “Add incident” where you can report a road closure or a “Miscellaneous” problem.

Forum|alt.badge.img+1
  • Author
  • Hub Rookie
  • December 16, 2025

Thank you very much, I will try with road closed permanently and get back with feedback in a week.


anchskier
Superuser
Forum|alt.badge.img+28
  • Superuser
  • December 16, 2025

Going back to your support tickets, what is the timeline of the support tickets you submitted?  I ask because the response times right now are generally pretty long (think a week or more) on initial requests.  If you submit any new support tickets while the first one is still active, or if you have an unrelated one in the system being worked, the new tickets will automatically be marked as closed (system function, not anything any person does) because it won’t allow anyone to have more than one active ticket at a time.  If it hasn’t been too long, it may be that they just haven’t gotten back to the initial ticket yet and that will just take more time.  figured I would mention it just in case that might be part of the issue on the support side.