P: Map module keeps flashing "map offline" when it's not

Yep, same here. Incredibly frustrating and renders Map module virtually unusable.  My system is Lightroom 2015.10.1 Release Camera Raw 9.10.1, MacOS 10.12.5, iMac Late 2013, 16GB memory.

Same issue for me. Every time the map needs a refresh, it goes to the world offline screen.
Here is my dirt. Lightroom 2015.10.1 Camera Raw 9.10.1 MacBookPro9,1, Memory 8GB,  MacOS 10.12.5 on SSD 1TB with 59% available. Plug-ins are disabled in LR also. I seem to recall odd behavior when loading a tract and tagging photos, I may have had to do it twice to get it to tag. Mac OS with two monitors and all of Mission Control turned on.

This is incredibly annoying.

 

Lightroom version: CC 2015.10 [ 1111918 ]

License: Creative Cloud

Operating system: Mac OS 10

Version: 10.12 [5]

Application architecture: x64

Logical processor count: 8

Processor speed: 2.6 GHz

Built-in memory: 8,192.0 MB

Real memory available to Lightroom: 8,192.0 MB

Real memory used by Lightroom: 420.7 MB (5.1%)

Virtual memory used by Lightroom: 4,024.3 MB

Memory cache size: 954.7MB / 1,856.4MB (51.4%)

Maximum thread count used by Camera Raw: 8

Camera Raw SIMD optimization: SSE2,AVX

Camera Raw virtual memory: 673MB / 4095MB (16%)

Displays: 1) 1440x900

 

Graphics Processor Info: 

NVIDIA GeForce GT 650M OpenGL Engine

With more than nine million cloud subscribers and 1.5 billion profit it's time for Adobe to get this bug fixed after almost ten days now. To my knowledge there is no bug in my monthly subscription fee to Adobe Creative Cloud.

There's good reason to be dubious about the proxy explanation because it's objectively false.  We didn't all simultaneously change our network settings just before this started.

@9647363 Burke - agreed.  My work internet is connected directly (speed tests are always at a minimum 800Mbps up and down) to the same server farm that houses a LOT of high end stuff - think a certain gaming console from a foreign company.  The maps module doesn't work there nor at home with Cox Cable.

I'm rather dubious about the proxy explanation. I can see the logic - I work in an IT related field - but I thought it might be sensible to test this notion. As I had to go into work yesterday (Saturday) morning, I took the laptop in and connected it to the network.  The problem was still evident. It seems unlikely to me that my ISP and my work network, connected to the UK academic network made a similar change at roughly the same time. It looks to me like the most logical explanation is some change in the way that the Google maps API is working.

While we all would like to see it fixed ASAP, my guess is they won't issue an update for a single bug (however widespread it is).  Most updates address multiple bugs.

Unfortunate, but probably what we'll have to deal with.

Basically the Map module is unusable. I understand this may be complicated issue, but still.. bunch of high-end coders and no solution for more than a week??? So disappointing!

Would be nice if this can be quickly resolved. Not only is it causing irritation and interrupts workflows, there also seems to be confusion at Adobe (a certain Mr Singh via Helpdesk chat suggested it's a proxy issue with my ISP provider, and when calling the German hotline, there was hesitant admission that the issue can be reproduced...). An rapid update that restores smooth operation is most appreciated!