b51s

We only found 100+ caches so far but we already had the experience that an automatic ghost TB removal feature is really missing. Half of the caches indicating TBs did not have one or at least had an inaccurate much too high number of items listed. Sometimes the last TB-Logs happend many month ago and with a lot of remarks that the TBs are missing. I like the idea of the original post and ask Groundspeak as well to implement such a mechanism. The named downsides are easy to prevent: No static timeframe for caches with little traffic. Just count a certain number of visitors. If noone discovered a TB, grabbed it or marked it as missing, it's obviously missing. Missing is no harm at all since anyone is able to rediscover the TB. No more disappointed faces of our little GeoCachers after a challenging hike should be worth the implementation. Please, Groundspeak ... look at these many comments. How can we all be wrong? Thanks in advance, B51s

Hy, I faced the same problem with a very slow gc.com site depending on the daytime I used it. And I can confirm that the Telekom routing theory seems to be right. Here's my observation: My DSL provider was German Telekom until 4th of may 2015. The geocaching.com site was often very slow, sometimes unusable. I am located nearby Nuremburg in the south of Germany. When I set my Smartphone to Wireless HotSpot mode and used the mobile data connection, gc.com was much faster. Since 2 days my new DSL provider is M-net and the problem is gone Summary: Performance problems with Telekom DSL, no performance problems with mobile data like LTE or M-Net DSL. Does not sound like a service problem on geoacaching.com side. Sounds like an internal Telekom routing and bottleneck issue. hope that helps, regards, f r e d