I can no longer navigate to Delaware from my house in Maryland. I get a “No Network: Map May Not Be Accurate” message.
However, I can navigate to places in Maryland, VA, or DC from my house in Maryland so it does not appear to be a network issue. This problem occurs on home WiFi and on 5g cellular service.
The only work around I’ve found is to navigate to somewhere in Maryland and then navigate to Delaware as an additional stop. That works and provides a route. It will not work if I select “new drive” instead of “add a stop” when I insert the Delaware address.
I’ve tried different addresses and towns in Delaware and I can get as far as the Chesapeake Bay Bridge but no further before the error pops up. In addition to trying different locations and networks and methods of asking for the routing, I’ve uninstalled and reinstalled the app and checked my settings for tolls and intersections. The problem persists after ensuring that I don’t have a setting to avoid tolls and it re-appeared even after re-installing the app. Given that i can get it to work but only with this workaround I think this may be a Waze issue and not an issue on my phone.
I welcome any feedback or discussion about this. I noted that another user had a problem navigating to Rehoboth from northern NJ in 2021 but I didn’t see a resolution for that.
Thank you -Daphne
I’m having the exact same issue trying to travel east bound over the Chesapeake Bay Bridge. It will not calculate. I’ve even turned in a ticket and all Waze says is “they cannot recreate the error.” Um, okay. So then how come every single Waze user can, but you can’t???
Moved this topic from the Delaware forum to the Maryland forum, as it sounds like in both cases, the trip involves an origin in Maryland somewhere west of the Chesapeake Bay and getting bottlenecked at the Bay Bridge eastbound.
Maryland is served by a different region of map editors from Delaware, who may be able to provide better solutions and/or insights to the experience you described.
Suddenly this problem appears to have gone away. It did reappear briefly when I stopped and started navigation several times. But just stopping again and starting the search from scratch resulted in a valid route. I’m not convinced it won’t come back, since there’s no dataset behind why it appeared or disappeared, but for now it’s resolved.
I did experiment with it more before it had been fixed and it did not just appear to be a Delaware issue. Most places that were further away resulted in similar error messages for me. So trying to generate routes to Philly or down to North Carolina also were generating the same error. But, again, it’s not mysteriously working.
I made no changes to settings or the phone or the app, so something changed on the Waze/server side of things.
Suddenly this problem appears to have gone away. It did reappear briefly when I stopped and started navigation several times. But just stopping again and starting the search from scratch resulted in a valid route. I’m not convinced it won’t come back, since there’s no dataset behind why it appeared or disappeared, but for now it’s resolved.
I did experiment with it more before it had been fixed and it did not just appear to be a Delaware issue. Most places that were further away resulted in similar error messages for me. So trying to generate routes to Philly or down to North Carolina also were generating the same error. But, again, it’s not mysteriously working.
I made no changes to settings or the phone or the app, so something changed on the Waze/server side of things.