Jump to content

Verizon, AT&T, Sprint and T-Mobile reveal network traffic stats from Super Bowl


IamMrFamous07

Recommended Posts

https://twitter.com/JohnLegere/status/563048576214114304/photo/1

 

Pretty sure they're only the fastest because they had the fewest amount of subscribers there. Phoenix is only a 10MHz FDD market for T-Mobile.

Considering the lower amount of subscribers and their backhaul largely provisioned at 40Mbps per sector throughout the Phoenix market, all they really had to do is increase their backhaul provisioning and max out the air interface. That alone will probably do it.
Link to comment
Share on other sites

Considering the lower amount of subscribers and their backhaul largely provisioned at 40Mbps per sector throughout the Phoenix market, all they really had to do is increase their backhaul provisioning and max out the air interface. That alone will probably do it.

 

Can you give me an example?

Link to comment
Share on other sites

I've ran into the 40 mbps limit Milan has mentioned, but it's all rural sites. The Perryville LTE site in town consistently gets 40 Mbps regardless of the time of day pretty much. Along the Interstate some of those sites have even less than 40 Mbps. On the Perryville site on the Interstate, it's 15 Mbps at midnight, meaning that's what the empty site gets more or less. I'd be shocked if there were very many subs there at all. Most people there use AT&T.

 

I wouldn't be shocked if St. Louis had a similar limit at the site but I don't know if T-Mobile ever had a large penetration there. The largest carrier here would be AT&T but Sprint and Verizon would be pretty close as far as sub numbers. This is a market where T-Mobile farmed their corporate stores off to Wireless Vision. There's no directly owned corporate stores in the St. Louis market to my knowledge.

Link to comment
Share on other sites

Can you give me an example?

I just did. But if you carefully read that fiercewireless article from the OP, you'll also notice what T-Mobile stated:

 

"Finally, T-Mobile said it "expanded backhaul capacity and put in place special event network parameters in and around the Glendale, AZ area to maintain T-Mobile's excellent 4G LTE coverage in this area."

Link to comment
Share on other sites

I just did. But if you carefully read that fiercewireless article from the OP, you'll also notice what T-Mobile stated:

 

"Finally, T-Mobile said it "expanded backhaul capacity and put in place special event network parameters in and around the Glendale, AZ area to maintain T-Mobile's excellent 4G LTE coverage in this area."

Special parameters?
Link to comment
Share on other sites

Special parameters?

 

John and Neville themselves rubbed the base stations with kosher chicken fat.

 

AJ

Link to comment
Share on other sites

Am I the only one that notes that Verizon handled 10x the data as T-Mobile, likely with a good chunk of older devices that didn't support AWS LTE, and was almost as fast?

 

This is a small sample size argument if there ever was one. Holy Macklemore. :lol:

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

    • Interesting, I saw this too on my AT&T S22 while roaming on US Cellular. I thought it was an Android bug since CellMapper was doing the same thing (didn't get a screenshot of that one). N66 makes more sense than N1. 
    • Thanks, that was good timing, I did see your report as I was buttoning up this latest update and added an override for that.. did it not work?   Ok, was that on AT&T also? Please send a report if you happen to see it again and safely have the opportunity. You can always do the long-press on the fly and then send a later one with an explanation pointing to the earlier one.. your username is attached to the long-press reports, so it's not an issue.
    • I sent a report in earlier, n66 reporting as n1. There should be two different reports, I couldn't find the button the first time so I just long pressed the connection type to send, then I remembered where it was. I put a note about the issue on the 2nd report. Both reports from me are for the same issue. Also, it might have been on a prior release but earlier this week I also saw n66 reported as n65 on the app. I was driving and wasn't able to send a report in for that one. 
    • One more SCP beta rolling out.. includes more bugfixes and minor improvements. Pending any major issues with this version, it will be released to the public within a few days. Thanks for all the help and feedback!
    • Passed by the former Sprint site at 1184 60th St in Brooklyn last week and noticed T-Mobile took down all of the Sprint equipment but it looked like they installed some new cabinets so conversion is likely in progress.
  • Recently Browsing

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