RealTime Traffic assumes no data=no road

I live in rural Colorado and often plan trips on roads where there are large gaps with no cell service. I couldn't figure out why ABRP was trying to route me on massive detours… until I turned off real time traffic.

It's clear that ABRP’s real time traffic feature assumes that if there's no traffic data, then the road must not exist and thus will refuse to route on that road. But wait, it gets stupider - I can add guide points to try and force ABRP to use the road… but it refuses. It will route to the guide points, but then will then turn around, backtrack all the way and take the massive detour with cell service. Then, once the route gets to the other side of the road it should have taken, it will do the same thing - go to the guide points and then turn around. I can literally make it route down the entire road that lacks cell service, but it refuses to just route the whole way through, insisting that the better route is to take the first half of the obvious route w/out cell service, turn around, take a massive detour, go back and take the second half of the obvious route, turnaround again and then continue on. Absolutely, mind numbingly senseless behavior. All fixed if I turn off real time traffic. I've seen this on Android and web interfaces.

It's clear that while ABRP w/real time traffic will go into areas without cell service and thus without traffic data, it will refuse to go through those areas. Someone on the dev team made a bad assumption that cell service exists everywhere and thus they could assume a lack of real time traffic data meant a road was closed. Which means ABRP with realtime traffic on will fail to route on many, many roads throughout the rural American West (and I imagine many other places). It's a classic case of an all city-based development team that does not understand truly rural areas.

Please fix this bug and then have your whole dev team take some vacation where they're required to use ABRP hours away from any city or freeway. Maybe even hire some remote staff in rural areas that live differently and use ABRP differently vs city-based staff. Who knows what other bugs they might find or feature improvements they might think of.