Geolocation API stuck?

I'm completely stuck and tearing my hair out over an issue with our 'What is My Location?' web tool. We just pushed an update, and ever since, the core functionality, which relies heavily on browser geolocation, has gone haywire.

Many, many users are reporting that the geolocation feature is either completely broken or, even worse, returning wildly inaccurate or stale data. The navigator.geolocation.getCurrentPosition() call specifically either times out completely or, when it does succeed, the callback gives us null or undefined coordinates. This is a nightmare for location accuracy!

I've been trying to debug this for hours. Here's what I've checked so far:

• Confirmed our SSL certificate is active and valid (no mixed content warnings).
• Scoured the browser console for errors – nothing obvious directly related to the geolocation API itself, just a lot of those frustrating timeout messages.
• Tested on multiple devices (desktops, various mobile phones) and across all major browsers (Chrome, Firefox, Safari) – the issue persists inconsistently across all of them.
• Checked for explicit permission denials, but users are prompted and usually grant access; the problem isn't a blanket denial.

This is a *critical* feature for our tool. Without reliable geolocation, 'What is My Location?' is essentially useless for a significant portion of our users. This is incredibly urgent, and I'm desperate for a solution.

Has anyone, *anyone* at all, experienced similar persistent issues with the Geolocation API recently? Are there any obscure fixes, server-side configurations, or debugging tips that I might be missing? I'm completely out of ideas. Anyone faced this before?