Jump to content

Coverage map updated to 10/10


dkyeager

Recommended Posts

The Sprint  coverage map was updated to 10/10.  Previously updated on 10/9 and 9/11, so we have a likely have more changes.  Duluth MN shows LTE along with Sacramento CA.  Fresno CA still shown as 3G, but likely no longer true (waiting for market launch). The Samsung portion of Sprint is really done with NV except cleanup and GMOs, both dependent on backhaul.   If you live in an unlaunched market, please review map and comment. http://coverage.sprint.com/IMPACT.jsp?INTNAV=SJS:HE:Cov

 

In Ohio, the Hocking Hills continues to show LTE which is not accurate.  Coshocton has LTE, but is shown as 3G only.  The LTE specks shown are likely true, as Band 26 LTE appears on many hilltops in the southern part of the state, however 1x800 covers even more and likely under-reported based on my travels.  US Route 23  now has extensive 1x800 coverage from Cambridge to Stuebenville OH, thanks to Wintersville (it's LTE not on map) and many sites along I-70 adding 1x800 (most are not documented well since they belong to Pittsburgh -- a market without a spreadsheet).  The gaps on US 23 are mainly around Piedmont Lake to Cadiz. As soon as you are on the freeway east of Cadiz heading east you are covered by 1x800.  Sensorly's coverage of 1x800 is questionable.

 

 

 

  • Like 1
Link to comment
Share on other sites

All I see in my area is black in both Chrome and Firefox, and it's amazingly slow and failing to load pieces.  Anyone else having these problems?

 

attachicon.gifSprintSiteSlow.png

 

- Trip

 

I was just looking at it today.  It does NOT show black for me.  Also, it is not slow for me either.

 

I also notice that for the past few days, it's been saying the last updated date as the current date.

Link to comment
Share on other sites

Glens Falls, N.Y. is finally showing up with LTE coverage more than a year after I first started experiencing it in parts of the area. Makes sense since I noticed expanded coverage through most parts of th city (that I frequent) within the last couple of weeks. Now they just need to expand a little farther north to cover where I live, though I suspect the towers that cover me are mostly GMOs.

Link to comment
Share on other sites

I was just looking at it today.  It does NOT show black for me.  Also, it is not slow for me either.

 

I also notice that for the past few days, it's been saying the last updated date as the current date.

 

If you search by zip code for 20554 (where I work), does it show you black or color?  I'm trying to figure out how two different browsers at home and at work (Internet Explorer is refusing to load the page at all) can all show me black at the default zoom level but nobody else sees it.

 

- Trip

Link to comment
Share on other sites

If you search by zip code for 20554 (where I work), does it show you black or color?  I'm trying to figure out how two different browsers at home and at work (Internet Explorer is refusing to load the page at all) can all show me black at the default zoom level but nobody else sees it.

 

- Trip

 

When I look for that zip code it shows green for voice and orange for data.  I'm using Firefox 32.0.3

Link to comment
Share on other sites

Some Spark Android devices still show "no service" in Verizon roaming areas :(

 

For example, claim your device is an "LG G3" and type "Wolverine, MI" into the map. The *map* claims Verizon 1x data roaming, but the icon says "No Coverage"

Link to comment
Share on other sites

My thing is when sprint Extended the already overstated LTE coverage I thought it was due to band 26...but it shows the same for single band as well as triband devices. Hopefully will be fixed.

Link to comment
Share on other sites

The Sprint  coverage map was updated to 10/10.  Previously updated on 10/9 and 9/11, so we have a likely have more changes.  Duluth MN shows LTE along with Sacramento CA.  Fresno CA still shown as 3G, but likely no longer true (waiting for market launch). The Samsung portion of Sprint is really done with NV except cleanup and GMOs, both dependent on backhaul.   

 

Coverage hasn't changed since the last update. As someone else said, it's been displaying the current date as the "updated on:" date. 

  • Like 1
Link to comment
Share on other sites

Sad to say...But I've actually found that the B25 coverage around here (Ericsson Market) actually more closely represents the Voice coverage map more than the Data Coverage Map. I'm assuming that is due to the fact that B26 isn't going to be turned on for awhile, but still, should be more accurate...:-/

Link to comment
Share on other sites

Sad to say...But I've actually found that the B25 coverage around here (Ericsson Market) actually more closely represents the Voice coverage map more than the Data Coverage Map. I'm assuming that is due to the fact that B26 isn't going to be turned on for awhile, but still, should be more accurate...:-/

 

This has also been my experience too, for both B25 and B26.

 

In my experience, the voice map is generally accurate for data in upgraded areas, with these assumptions :

- "Best" Voice = B25 + B26

- "Good" Voice = B26 LTE only

- "Fair" Voice = 1x800 Only.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • It’s a neat and seemingly valid / effective strategy that, at least from my understanding, is only really used by VZW
    • Those are usually left over from the initial AWS deployment, so all run B13/B66 with support for BC0/BC1 (although that’s been shut off on most sites). No NR. Sites with the later Ericsson radios got an OTA update and broadcast B2. On those sites, a B5 OTA update was also available (and tested), but ultimately rolled back. Putting up all that power/spectrum severely degraded the B13 output.  The site atop Crystal Mountain is another story and uses the same setup as the site on the ridge near Neilton. These antennas were selected for their vertical beamwidth. Most modern directional antennas have small vertical beamwidths and would require extreme downtilt to cover the road next to a steep ridge. Thus, they would have a severely limited coverage footprint beyond the road. Omnis can be a better choice in these instances, especially when there’s LoS to the coverage objective (since they’ll generally have lower gain figures). Omnis also don’t run in to the horizontal sector edge problem, which can be difficult to optimize for with directional antennas that have complex or irregular 3D gain profiles. That’s why on a lot of sites on mountains, you’ll see wider antennas used. For example, the Verizon site on Joyce Ridge has three sectors with 80-degree HBW antennas. 
    • Do you know what RAN is behind those Omni's? LTE (bands?) are they pushing any NR through them? Very curious   edit: I guess I could check cellmapper etc but you might know more nuance!
    • N41 here has been expanded from 140Mhz to 180Mhz.  Speeds seem the same so they just need to work on backhaul
    • I noticed today that T-mobile has shut of B41 LTE in the Louisville area and widened the 2nd n41 carrier to 80MHz. That just leaves them with 5x5 B12, 10x10 B2, and two 10x10 B66 carriers on LTE, everything else is in NR (besides their 2G network). They have 20x20 n71, 20x20 n25, 5x5 n25, and 180MHz n41. 
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...