S4GRU

Migrated from Original Forum. Originally Posted 6 January 2012

Ben. Thanks for the compliments and welcome to the site. The Epic 4G Touch will do voice on 800MHz on Network Vision towers. It will also run 3G on 800MHz, when and if Sprint ever deploys 3G EVDO on 800MHz. However, to run in Sprint's LTE on 800 that will come out in 2013, you will need to upgrade your device.

Best Regards,

Robert Herron

Sprint 4G Rollout Updates

I hope to see you around the forums.

Migrated from Original Forum. Originally Posted 6 January 2012

The number that use WiMax? The last time I heard it was over 200. But I think it's in a steady decline now. It's not so much that LTE is a better technology, IMHO, it's that it offers WirelessCo's more control over their network (which is a good and bad thing) and, more importantly now has economies of scale behind it. LTE is cheaper than WiMax now. And it will be far cheaper next year. LTE prices are going down, while WiMax is trending up. And WiMax2 will be released before LTE Advanced.

However, none of that matters now. WiMax is dying. Someone just needs to pull the plug.

As for WiMax frequencies, about half the world uses 2.5-2.6GHz, like Clearwire. The other half are split between 2.3GHz, 3.3GHz and 3.5GHz. Some of those places that use higher frequencies use beamforming to transmit their signal. So, a 3.5GHz signal beamformed actually produces a stronger signal that penetrates walls better than Clearwire's 2.5GHz signal.

In fact, if Sprint used beamforming on Clearwire's spectrum, it wouldn't even need any more 800MHz spectrum. Beamforming a 2.5GHz signal would produce a usable signal pattern better than 1900PCS, nearly equaling 800MHz. Beamforming takes a lot more engineering and signal planning though than a conventional deployment, and also more antennas. So there is some cost associated with it. But to be able to cover more area with 2.5GHz, deliver better results (and higher speeds), have happier customers and not have to buy expensive spectrum at auction all more than counteract the additional costs associated with beamforming.

Migrated from Original Forum. Originally Posted 5 January 2012

Good, short read. And thanks for posting the source link!

Migrated from Original Forum. Originally Posted 12 January 2012

Although I'm probably not going to get one, I would love to have more choices on the Now Network.

Migrated from Original Forum. Originally Posted 12 January 2012

I have our article up now: Sprint VP: No more new WiMax phones, speculation of LTE devices selling in April and don't expect Windows Phones in the near future

Migrated from Original Forum. Originally Posted 12 January 2012

I'm working on this article right now actually, but I keep getting interrupted this morning. Thanks legion125.

Migrated from Original Forum. Originally Posted 15 January 2012

Awesome. Thanks for the post!

There are a few places that have coverage, but for some reason do not show up on Clear's Coverage Maps. I have added this sticky forum post to keep track of them. I will update this note as they appear (or disappear).

• Cloquet, Minnesota. The tower went live back in March 2011. It was initiallly on Clear's maps, but disappeared. The tower was recently confirmed as still operational, though not showing. You can view some of the coverage from Sensorly Android users at http://sensorly.com
  
• Allentown, Pennsylvania. I received an e-mail back in July that someone was able to get a WiMax signal just south of Bethlehem. Also, a poster in the official Sprint forums mentioned they received a WiMax signal on the south side of Allentown. Also, Sensorly.com shows one blip of WiMax coverage being reported. However, recent comments from folks in the area cannot substantiate this phantom site. Let me know if you are able to connect to it.
  

POSSIBLE OTHER PHANTOM SITES:

• Fallbrook, California. A blips appears on Sensorly's site along I-15 near the CA-76 exit, SE of Fallbrook towards Paia. Looking for confirmation that there is a signal in this location.
  
• Moreno Valley, California. A blip appears on Sensorly's site on I-215 on the west side of Moreno Valley near Edgemont. Looking for verification that this is real coverage from a protection site.
  
• Perris, California. A double blip of coverage has shown up on Sensorly on the I-215 corridor through Perris. Looking for verification of this protection site.
  
• Eaton Rapids/Springport, Michigan. In a remote spot between the South Central Michigan towns of Eaton Rapids and Springport, a blip of coverage is hown up on Sensorly's maps. Is this a legit prptection site? Or a GPS malfunction?
  
• Hobbs, New Mexico. This town is not showing on Clear's coverage maps, but there was a mysterious blip that showed up on Sensorly a few miles west of town. Looking for confirmation if any Sprint 4G users go through this area. Could be a GPS error on the device that reported it to Sensorly.
  
• Rocky Mount/Wilson Regional Airport, North Carolina. There is definitely confirmed Protection Sites in the cities of Rocky Mount and Wilson. However, there is a blip along I-95 that has shown up on Sensorly near the Rocky Mount/Wilson Regional Airport. This area would be out of range of the other two towers. Is this a Phantom Site not shown on Clear's Coverage Maps?
  
• Milford, Texas. Right along I-35E, between Dallas and Hillsboro, a blip of coverage is showing up on Sensorly's website, that is not shown on Clear's coverage maps. Looking for confirmation of this site.
  

HISTORY:

• Des Moines, Iowa. In November 2011, Des Moines was removed from the list. The two WiMax towers there have re-appeared back on the coverage maps at clear.com.
  
• Ventura/Oxnard, California. In October 2011, Ventura and Oxnard were removed from the list. The one WiMax tower there has appeared on the coverage maps at clear.com.
  
• Asbury Park, New Jersey. Removed from the list when coverage showed up on the evening of September 12th on Clear.com's website.
  
• Houghton/Hancock, Michigan. The twin burgs were removed from the list when they reaopeared back on Clear's Coverage Maps on August 16th, after being gone for 2 months.
  
• Kankakee, Illinois. Coverage finally showed up on coverage maps the evening of July 27th. Thanks to Rai Diaz who discovered this operating cell before Clear even showed it on their map!!!
  
• In early July, the tower in Fortuna Foothills, Arizona (just east of Yuma) disappeared from coverage. However, it re-appeared on July 26th. On one message board, it said that it was taken down temporarily because it interfered with an operator in Mexico and now has been rectified. I have been unable to confirm this mystery.
  

Migrated from Original Forum. Originally Posted 24 July 2011

What are Protection Sites?

by Sprint 4G Rollout Updates on Sunday, July 24, 2011 at 10:01am

You keep reading around S4GRU about "Protection Sites." But what are protection sites, you ask?

Sprint broadcasts it's 4G WiMax signal on 2.5GHz-2.65GHz (along with it's partner Clear/Clearwire). That's up to 150MHz of spectrum (variable by market). More than any other carrier in the country.

Before 2007, 2.5GHz-2.65GHz was allocated by the FCC as EBS and BRS spectrum (Educational Broadband Service/Broadcast Radio Service). EBS was used by any public education organization free of charge on a first come, first served basis. However, this spectrum was relatively little used. At it's peak, only 100 education institutions actually utilized the spectrum for educational purposes. Most actually leased their spectrum to Clearwire for their pre-WiMax network.

This was deemed a huge waste of spectrum by the FCC (and it was). When you consider the entire population of the U.S. and the total data capacity of the EBS spectrum, it was not even 1/100th of 1% utilized!

In 2004, the FCC decided to reallocate the EBS/BRS spectrum for mobile internet and gave notice to the EBS/BRS license holders that in 2007 they would be repurposing the spectrum. EBS license holders could reapply with the broadband carriers in the 2007 reallotment. It was a confusing mess. In reality in the way it was structured, EBS spectrum winners were subleasing spectrum from the schools and universities. BRS spectrum licenses were purchased outright.

In 2007 the EBS spectrum went out for bid. Two bidders ended up with the lion's share of the 150MHz of spectrum...Sprint and Clearwire. Sprint ending up with 60MHz of nationwide coverage. Clearwire with 90MHz of nationwide coverage. One of the conditions to the bidders is a clause called "Minimum Coverage Standards."

For the EBS Spectrum, the FCC breaks up the 50 States and U.S. Territories into approx. 500 Basic Trading Areas, or BTA's (In other wireless spectrum, they use CMA's, or Cellular Market Areas). They use these to manage licenses for EBS spectrum. Licenses for each BTA are good for 10 years upon issuance. At 10 year intervals, they need to be renewed. At renewal, service provided is evaluated by the FCC. 99% of all renewals are approved. Some carriers have spectrum in all the BTA's (or CMA's). Some only have regions. Some have regions in one set of spectrum and other regions in other sections. It can be very messy and confusing to track FCC licenses.

In 2008, Sprint and Clearwire received FCC approval and merged their EBS/BRS spectrum holdings into a singular holding of the 150MHz block and formed the joint-venture company Clear.

Back to the Minimum Coverage Standards. The FCC mandated that a minimally acceptable amount of coverage be in every BTA by May 1, 2011. Clearwire started rolling out protection sites in earnest in early 2011. However, did not meet the Minimum Coverage Standards in all BTA's by May 1st, and started filing for extensions.

FROM CLEARWIRE 2010 ANNUAL REPORT:

 

The FCC also clarified the procedure by which BRS and EBS licensees must demonstrate minimum acceptable service, and required them to demonstrate minimum service by May 1, 2011. Minimum service showings demonstrate to the FCC that a licensee is not warehousing spectrum. If a BRS or EBS licensee fails to demonstrate minimum

service by May 1, 2011, its license may be canceled and made available for re-licensing.

 

For our spectrum, we

believe that we will satisfy the substantial service requirements for all owned and leased licenses associated with

each of our commercially launched markets, whether Pre-4G or 4G. For licenses covering areas outside of our

commercially launched markets, we are in the process of executing a (Protection Site Plan) to comply with the minimum service requirement by the deadline. Our ability, however, to meet the minimum service deadline for every owned or leased license in areas outside of our launched markets is uncertain, and we will likely seek waivers or extensions of the deadline from the FCC in some circumstances.

Any winning bidder who did not provide minimally acceptable service within a BTA, will be subject to having the license revoked and the original license holder will be unable to ever regain it.

This is very strong language about revocation. Minimum acceptable coverage to the FCC for this spectrum is:

• 30% of the BTA's Population Has Useable Service, or...
  
• 50% of the Geographical Area (Square Mileage) of the BTA has Useable Service.
  

If one of these two items is met, then the license holder has met the Minimum Acceptable Coverage Standards required by the FCC for the EBS spectrum.

Sprint/Clear 4G Basic Trading Area (BTA) Map showing all 500 BTA's in the U.S. The ones in green have at least (1) Sprint/Clear 4G tower in operation. The ones in white have no Clearwire service in operation.

In the map above, you can see all the 500 BTA's in the United States. What Sprint/Clear have decided was to put up at least one tower every in every BTA in the country. So in 2011, they broke from the conventional rollout. They are deploying "Protection Sites" in all the BTA's. These are sites intended to keep the FCC at bay with the intention of trying to meet minimum acceptable service to maintain licensing.

It appears that in larger population BTA's (250k+), they are deploying more than one protection site to meet the 30% population coverage minimum.

Sprint/Clear are well on their way to being complete with the BTA Protection Site rollout before the end of 2011. They are averaging about 7 to 10 towers per week. So largely the areas in white will all be filled in green in short order. There will be a few exceptions. BTA's that have Clearwire's Pre-WiMax technology (like Reno, Dayton and Anchorage) will not receive protection sites. They already meet the FCC Minimum Coverage Requirements as the Pre-WiMax is broadcast on the same 2.5GHz spectrum.

Most likely, the FCC will not give Sprint/Clear any grief over the minimum service clauses because they are attempting to do something. The clause is largely to prevent people from buying the spectrum and just sitting on it as an investment. The FCC really wants it just to be used. Most likely, the extension for Minimum Coverages will be given.

The service requirements on the 700MHz spectrum are far more stringent than they were on the 2.5GHz spectrum. Verizon, AT&T and MetroPCS have less time to roll out. And the terminology used in it's FCC licensing doesn't have vague words like "minimum acceptable", but rather "substantial coverage."

Migrated from Original Forum. Originally Posted 8 January 2011

In the past few months I've read a lot about beam forming. I wish they had used that in their deployment of 2.5GHz. WiMax would have never had the bad wrap and seen as inferior to LTE. Oh, what should have been.

NOTE: This thread is outdated. Protection Sites are no longer being deployed since Sprint and Clearwire have both announced they are migrating to LTE for it's 4G technology. The information below is no longer accurate and should not be used. It is being retained just for historical purposes...

BTA's Not Meeting FCC Minimum Service Mandates (where more Protection Sites are anticipated...)

by Sprint 4G Rollout Updates on Friday, August 19, 2011 at 9:39 pm

I've created this thread as a way to track upcoming Protection Sites. I will keep this thread updated, removing BTA's (Basic Trading Areas) once they meet FCC Minimum Service Requirements, or change categories. See BTA listings below...

High Likelihood of Protection Site

These BTA's do not have any 2.5GHz service from Clearwire and thus do not meet FCC Minimum Service Requirements. These are highly likely to get at least one tower of service between now and the FCC Extended Deadline of November 1, 2011.

• Arkansas > Harrison (BTA #182)
  
• California > El Centro/Imperial (BTA #124)
  
• California > San Luis Obispo (BTA #405)
  
• Idaho > Idaho Falls/Rexburg/Salmon and Jackson WY (BTA #202)
  
• Idaho > Pocatello/American Falls/Soda Springs (BTA #353)
  
• Idaho > Twin Falls/Burley/Sun Valley (BTA #451)
  
• Iowa > Burlington/Ft. Madison/Keokuk (BTA #61)
  
• Iowa > Cedar Rapids (BTA #70)
  
• Iowa > Dubuque (BTA #118)
  
• Iowa > Fort Dodge/Storm Lake (BTA #150)
  
• Iowa > Iowa City (BTA #205)
  
• Iowa > Mason City (BTA #285)
  
• Iowa > Ottumwa/Oskaloosa (BTA #337)
  
• Iowa > Sioux City (BTA #421)
  
• Kentucky > Corbin/London (BTA #98)
  
• Kentucky > Pikeville (BTA #474)
  
• Kentucky > Somerset (BTA #423)
  
• Michigan > Alpena (BTA #11)
  
• Michigan > Battle Creek (BTA #33)
  
• Michigan > Escanaba/Manistique (BTA #132)
  
• Michigan > Mt. Pleasant (BTA #307)
  
• Michigan > Midland/Saginaw/Bay City (BTA #390)
  
• Michigan > Petoskey/Cheboygan (BTA #345)
  
• Michigan > Traverse City (BTA #446)
  
• Minnesota > Brainerd (BTA #54)
  
• Minnesota > Willmar/Montevideo (BTA #477)
  
• Missouri > Poplar Bluff (BTA #355)
  
• Missouri > West Plains (BTA #470)
  
• Montana > Bozeman/Belgrade (BTA #53)
  
• Montana > Butte (BTA #64)
  
• Montana > Missoula (BTA #300)
  
• Nebraska > Hastings (BTA #185)
  
• Nebraska > McCook (BTA #270)
  
• New Hampshire > Keene & Brattleboro VT (BTA #227)
  
• New Mexico > Clovis/Portales (BTA #87)
  
• New Mexico > Gallup and St. John's/Eagar, AZ (BTA #162)
  
• New Mexico > Hobbs/Lovington (BTA #191)
  
• New Mexico > Roswell/Ruidoso (BTA #386)
  
• New York > Glens Falls/Lake George (BTA #164)
  
• New York > Jamestown/Dunkirk and Warren PA (BTA #215)
  
• New York > Oneonta/Delhi (BTA #333)
  
• New York > Plattsburgh (BTA #352)
  
• North Dakota > Dickinson (BTA #113)
  
• North Dakota > Grand Forks/Devils Lake and Thief River Falls MN (BTA #166)
  
• North Dakota > Minot (BTA #299)
  
• North Dakota > Williston (BTA #476)
  
• Ohio > Chillicothe (BTA #80)
  
• Ohio > Lima (BTA #255)
  
• Ohio > Zanesville (BTA # 487)
  
• Pennsylvania > Allentown/Bethlehem/Easton (BTA #10)
  
• Pennsylvania > Johnstown/Somerset (BTA #218)
  
• Pennsylvania > Meadville (BTA #287)
  
• Pennsylvania > Stroudsburg (BTA #435)
  
• South Carolina > Anderson/Toccoa GA (BTA #16)
  
• South Carolina > Greenwood (BTA #178)
  
• South Dakota > Aberdeen/Mobridge (BTA #1)
  
• South Dakota > Watertown (BTA #464)
  
• Tennessee > Cookeville (BTA #96)
  
• Texas > Del Rio/Eagle Pass (BTA #121)
  
• Texas > San Angelo/Brady/Ozona (BTA #400)
  
• Utah > Logan/Preston ID (BTA #258)
  
• Utah > St. George/Cedar City (BTA #392)
  
• Vermont > Rutland/Bennington (BTA #388)
  
• Virginia > Charlottesville (BTA #75)
  
• Virginia > Staunton (BTA #430)
  
• Virgin Islands > All Areas (BTA #491)
  
• Washington > Longview/Kelso (BTA #261)
  
• West Virginia > Beckley/Lewisburg (BTA #35)
  
• West Virginia > Clarksburg/Elkins (BTA #82)
  
• West Virginia > Fairmont (BTA #137)
  
• West Virginia > Logan (BTA #259)
  
• West Virginia > Morgantown (BTA #306)
  
• West Virginia > Princeton/Bluefield, VA/WV (BTA #48)
  
• West Virginia > Weirton/Steubenville OH (BTA #430)
  
• West Virginia > Wheeling/St. Clairsville OH (BTA #471)
  
• Wisconsin > Wisconsin Rapids/Stevens Point (BTA #432)
  

Moderate Likelihood of Additional Protection Site(s)

These BTA's have some 2.5GHz service deployed, but definitely not enough to meet the FCC Minimum Service Requirement of 30% of BTA Population covered with useable signal.

• California > San Diego County (BTA #482)
  
• Puerto Rico > Mayaguez/Ponce (BTA #489)
  

Slight Chance of Additional Protection Site(s)

These BTA's have a decent amount of 2.5GHz service deployed, but appear slightly below meeting the FCC Minimum Service Requirement of 30% of BTA Population covered with useable signal.

• Alaska > Juneau (BTA #221)
  
• American Samoa > All Areas (BTA #492) - I have this one as slight because they may allow this license to lapse.
  
• California > Fresno (BTA #157)
  
• California > Santa Barbara/Santa Maria (BTA #406)
  
• Guam > All Areas (BTA #490) - I have this one as slight because they may allow this license to lapse.
  
• Hawaii > Kauai/Lihue (BTA #254)
  
• Northern Mariana Islands > All Areas (BTA #493) - I have this one as slight because they may allow this license to lapse.
  
• Oregon > Coos Bay/North Bend (BTA #97)
  

Not Likely any Additional Protection Site(s)

These BTA's appear to meet the FCC Minimum Service Requirement of 30% of BTA Population covered with useable signal.

• Alaska > Anchorage (BTA #14)
  
• Alaska > Fairbanks (BTA #136)
  
• California > Bakersfield (BTA #28)
  
• California > Chico/Paradise (BTA #79)
  
• California > Eureka/Crescent City (BTA #134)
  
• California > Los Angeles (BTA #262)
  
• California > Merced (BTA #291)
  
• California > Modesto (BTA #303)
  
• California > Redding/Red Bluff (BTA #371)
  
• California > Sacramento/Northern Sierras (BTA #389)
  
• California > San Francisco/San Jose/Oakland (BTA #404)
  
• California > Stockton (BTA #434)
  
• California > Visalia (BTA #458)
  
• California > Yuba City/Marysville (BTA #485)
  
• Hawaii > Hawaii/Hilo & Kailua (BTA #190)
  
• Hawaii > Maui/Molokai/Lanai (BTA #222)
  
• Hawaii > Oahu/Honolulu (BTA #192)
  
• Idaho > Boise (BTA #50)
  
• Idaho > Lewiston/Moscow and Clarkston WA (BTA #250)
  
• Nevada > Reno/Carson City/Elko and Mammoth Lakes CA (BTA #372)
  
• Oregon > Bend/Redmond/Prineville (BTA #38)
  
• Oregon > Eugene (BTA #133)
  
• Oregon > Klamath Falls/Alturas CA (BTA #231)
  
• Oregon > Medford/Grants Pass (BTA #288)
  
• Oregon > Portland (BTA #358)
  
• Oregon > Roseburg (BTA #385)
  
• Oregon > Salem/Corvallis (BTA #395)
  
• Puerto Rico > San Juan (BTA #488)
  
• Washington > Aberdeen/Hoquiam (BTA #2)
  
• Washington > Bellingham (BTA #36)
  
• Washington > Bremerton (BTA #55)
  
• Washington > Olympia (BTA #331)
  
• Washington > Port Angeles (BTA #356)
  
• Washington > Seattle/Tacoma (BTA #413)
  
• Washington > Spokane/Pullman and Coeur d' Alene ID (BTA #425)
  
• Washington > Walla Walla/Pendleton OR (BTA #460)
  
• Washington > Wenatchee (BTA #468)
  
• Washington > Yakima (BTA #482)
  

The Sprint 4G/Clearwire FCC BTA Map as of August 19, 2011.

A full resolution image of this map can be found at: http://4g.herronweb....TAmap081911.jpg

Migrated from Original Forum. Originally Posted 10 January 2011

Thanks for the latest info. I've updated.

Migrated from Original Forum. Originally Posted 9 January 2011

Thanks for the info. I have updated the list above, accordingly. If you have data on other protection sites in South Carolina (or anywhere for that matter) feel free to post it here. Thanks for your contributions!

Not Operational:

• Florida > Belleview. Read complaints on message boards that users cannot connect to this tower. Sensorly is not reporting service.
  
• Illinois > Quincy. Read complains on message boards that users cannot connect to the tower. Sensorly is not reporting service.
  
• Illinois > Springfield. Read complains on message boards that users cannot connect to the tower. Sensorly is not reporting service.
  
• Missouri > Hannibal. Read complains on message boards that users cannot connect to the tower. Sensorly is not reporting service.
  
• Ohio > Marion. Received a complaint that a user could not connect to this new tower.
  

Confirmed (including confirmed phantom sites):

• Alabama > Athens. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Birmingham > Central. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Birmingham > Alabaster. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Birmingham > Bessemer. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Birmingham > Homewood. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Birmingham > Hoover. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Birmingham > Irondale. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Decatur. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Dothan. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Enterprise. Confirmed by a poster on the Sprint Message Boards and Sensorly. Do you have any performance data?
  
• Alabama > Huntsville > Huntsville Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Mobile > West Tower. Confirmed by Chris Burgess and Sensorly. Speeds up to 5.5MB download and 1MB upload observed.
  
• Alabama > Montgomery > East. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > The Shoals > Muscle Shoals Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Alabama > Tuscaloosa. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Bullhead City. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Casa Grande. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Kingman. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Lake Havasu City. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Phoenix > Northgate/North Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Phoenix > North Scottsdale/Airport Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Phoenix > Mesa Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Phoenix > Chandler Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Phoenix > Tolleson/West Tower. Confirmed by Ian Zelman and Sensorly. Speeds up to 3.1 MB download observed.
  
• Arizona > Phoenix > Ahwatukee/South Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Prescott. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Sierra Vista. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Tucson > Reid Park/South Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Tucson > Wilmot/East Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Tucson > Alvernon/North Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Yuma > Central. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Yuma > East. Confirmed by Sensorly. Do you have any performance data?
  
• Arizona > Yuma > Somerton. Confirmed by Message Board posting on Sprint Users forum. Mentioned low speeds around 1MB.
  
• California > Bakersfield. Confirmed by Sensorly. Do you have any performance data?
  
• California > Eureka > Eureka Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > Fresno. Confirmed by Sensorly. Do you have any performance data?
  
• California > Indio/LaQuinta. Confirmed by Sensorly. Do you have any performance data?
  
• California > Los Angeles > San Fernando/Sylmar Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > Oxnard. Confirmed by Sensorly. Do you have any performance data?
  
• California > Palm Springs > Cathedral City Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > Ridgecrest. Confirmed by Sensorly. Do you have any performance data?
  
• California > Salinas. Confirmed by Sensorly. Do you have any performance data?
  
• California > San Diego > SDSU/East Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > San Diego > National City Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > San Diego > UCSD/La Jolla Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > San Diego > Escondido Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > San Diego > San Marcos Tower. Confirmed by Sensorly. Do you have any performance data?
  
• California > Santa Barbara. Confirmed by Sensorly. Do you have any performance data?
  
• California > Santa Maria. Confirmed by Sensorly. Do you have any performance data?
  
• California > Santa Rosa. Confirmed by Sensorly. Do you have any performance data?
  
• California > Victorville/Hesperia. Confirmed by Sensorly. Do you have any performance data?
  
• California > Yuba City/Marysville. Confirmed by Sensorly. Do you have any performance data?
  
• California > Yucaipa/Calimesa. Confirmed by Sensorly. Do you have any performance data?
  
• Colorado > Colorado Springs > Downtown Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Colorado > Colorado Springs > Security-Widefield Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Colorado > La Junta. Confirmed by Sensorly. Do you have any performance data?
  
• Colorado > Pueblo. Confirmed by Sensorly. Do you have any performance data?
  
• Connecticut > New London/Groton > Central Waterford Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Connecticut > Torrington. Confirmed by Michael Mercier and Sensorly. Speeds up to 8.4MB download observed.
  
• Delaware > Dover > Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Delaware > Dover > South Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Ft. Myers/Cape Coral > North Cape Coral Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Ft. Myers/Cape Coral > South Ft. Myers Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Fort Walton Beach > Ocean City Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Fort Walton Beach > Niceville Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Gainesville. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Lady Lake/The Villages. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Lake City. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Lakeland. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Melbourne/Palm Bay > North Melbourne/Eau Gallie Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Melbourne/Palm Bay > Palm Bay Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Naples. Confirmed by Mark Tyler. Speeds up to 2.3MB download reported. Backhaul does not appear to have been upgraded at this location.
  
• Florida > Ocala. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Panama City. Confirmed by Users of this Fan Page, users in Sprint message boards and Sensorly. Kerry Cole reports 1MB speeds with a full signal. This is most likely caused by Clearwire using the existing 3G backhaul at this location.
  
• Florida > Pensacola. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Port St. Lucie > NE Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Port St. Lucie > West Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Sarasota/Bradenton > Central Sarasota Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Sarasota/Bradenton > Bee Ridge Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Sebring. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Tallahassee > North Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Tallahassee > Northeast Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Tallahassee > South/Lake Munson Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Venice. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Vero Beach. Confirmed by Sensorly. Do you have any performance data?
  
• Florida > Winter Haven. Confirmed by Sensorly. Do you have any performance data?
  
• Georgia > Albany. Confirmed by S4GRU Member owensri2 as operating. owensri2 observed up to 6 MB download and 1 MB upload speeds.
  
• Georgia > Americus. Confirmed by S4GRU Member owensri2 as operating. owensri2 observed up to 9 MB download and 1.5 MB upload speeds.
  
• Georgia > Moultrie. Confirmed by S4GRU Member owensri2 as operating. owensri2 observed up to 8 MB download and 1.5 MB upload speeds.
  
• Georgia > Thomasville. Confirmed by Sensorly and S4GRU Member owensri2 as operating. owensri2 observed 8 MB download and 1.5 MB upload speeds.
  
• Georgia > Tifton. Confirmed by S4GRU Member owensri2 as operating. owensri2 observed up to 6 MB download and 1 MB upload speeds.
  
• Georgia > Valdosta. Confirmed by S4GRU Member owensri2 as operating. Do you have any performance data?
  
• Hawaii > Island of Hawaii > Kailua-Kona Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Idaho > Coeur d' Alene. Confirmed by Sensorly. Do you have any performance data?
  
• Illinois > Carbondale. Confirmed by Sensorly. Do you have any performance data?
  
• Illinois > Jacksonville. Confirmed by Sensorly. Do you have any performance data?
  
• Illinois > Kankakee. Confirmed by Rai Diaz and Sensorly. Do you have any performance data?
  
• Indiana > Anderson. Confirmed by Brent David and Sensorly. Speeds up to 6.5 MB down and 1.4 MB upload were reported.
  
• Indiana > Elkhart. Confirmed by Jason Russ and Sensorly. Do you have any performance data?
  
• Indiana > Indianapolis > NE/Keystone Tower. Confirmed by Brent David and Sensorly. Do you have any performance data?
  
• Indiana > Muncie. Confirmed by Brent David and Sensorly. Do you have any performance data?
  
• Indiana > South Bend. Confirmed by Jason Russ and Sensorly. Speeds up to 7MB download and 1.5MB upload were observed.
  
• Iowa > Ames. Confirmed by Sensorly. Do you have any performance data?
  
• Iowa > Council Bluffs. This tower is confirmed by Sensorly. Do you have any performance data?
  
• Iowa > Des Moines > North Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Iowa > Des Moines > West Des Moines Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Iowa > Quad Cities > Davenport Tower. Confirmed by Christian Shroeder and Sensorly. Speeds up to 7.4MB download and 1.4 MB upload observed.
  
• Iowa > Waterloo. Confirmed as operating by a poster on the Sprint message boards and Sensorly. Max speeds of 8.4 MB download and 1 MB upload were reported.
  
• Kansas > Abilene. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Emporia. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Hutchinson. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Lawrence. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Liberal. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Manhattan. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Pittsburg. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Salina. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Topeka. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Wichita > Downtown Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Kansas > Wichita > Airport/West Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Kentucky > Ashland (Tri-Cities). Confirmed by Sensorly. Do you have any performace data?
  
• Kentucky > Lexington. Confirmed by Eric Murine, Ben Slade, Sensorly and many Message Boards. Speeds up to 6MB reported with full signal.
  
• Louisiana > Alexandria > Pineville Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Baton Rouge > East/BRCC Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Baton Rouge > Baker Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Hammond. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Houma. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Lafayette > West Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Lake Charles. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Monroe > SW/Bawcomville Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > New Iberia. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > New Orleans > CBD Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > New Orleans > Kenner Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Opelousas. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Shreveport. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Slidell. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Tallulah. Confirmed by Sensorly. Do you have any performance data?
  
• Louisiana > Thibodaux. Confirmed by Sensorly. Do you have any performance data?
  
• Maine > Bangor > Stillwater Ave./North Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Maine > Lewiston/Auburn. Confirmed by Sensorly. Do you have any performance data?
  
• Maine > Portland > South Waterfront/Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Maine > Portland > Riverton/NW Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Maine > Saco/Biddeford. Confirmed by Sensorly. Do you have any performance data?
  
• Maine > Sanford. Confirmed by Sensorly. Do you have any performance data?
  
• Maryland > Frederick. Confirmed by Sensorly. Do you have any performance data?
  
• Maryland > Salisbury. Confirmed by Sensorly. Do you have any performance data?
  
• Massachusetts > Fitchburg. Confirmed by Sensorly. Do you have any performance data?
  
• Massachusetts > Springfield > Central Springfield Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Massachusetts > Springfield > Westover/NE Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Massachusetts > Worcester > Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Massachusetts > Worcester > Millbury/South Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Adrian. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Benton Harbor/St. Joseph. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Detroit > Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Detroit > Garden City/Inkster Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Detroit > Highland Park Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Detroit > Southfield. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Detroit > Sterling Heights/Clinton Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Detroit > Warren/Greensbriar Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Flint. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Jackson. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Kalamazoo. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Lansing > Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Lansing > SE/MSU Tower. Confirmed by Sensorly. Do you have any performance data
  
• Michigan > Lansing > South/Holt Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Muskegon. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Plainwell/Otsego. Confirmed by Sensorly. Do you have any performance data?
  
• Michigan > Port Huron. Confirmed by Sensorly. Do you have any performance data?
  
• Minnesota > Mankato. Confirmed by Daniel Meyer and Sensorly. Do you have any performance data?
  
• Minnesota > Moorhead/Fargo. Confirmed as operating on Sensorly. Do you have any performance data?
  
• Mississippi > Biloxi. Confirmed by Sensorly. Do you have any performance data?
  
• Mississippi > Grenada. Confirmed by Jeff Keyseear. Speeds observed up to 6MB with full signal.
  
• Mississippi > Gulfport. Confirmed by Sensorly. Do you have any performance data?
  

• Mississippi > Hattiesburg. Confirmed by Message Board posting on Sprint Users forum. Do you have any performance data?
  
• Mississippi > Jackson > Central. Confirmed by Sensorly. Do you have any performance data?
  
• Mississippi > Meridian. Confirmed by Sensorly. Do you have any performance data?
  
• Mississippi > New Albany. Confirmed by Sensorly. Do you have any performance data?
  
• Mississippi > Newton. Confirmed by Sensorly. Do you have any performance data?
  
• Mississippi > Vicksburg. Confirmed by Sensorly. However, Sprint has spotty coverage in the area and you may not be able to connect if you have a roaming signal. Do you have any performance data?
  
• Nebraska > Columbus. Confirmed by Sensorly. Do you have any performance data?
  
• Nebraska > Grand Island. Confirmed by Sensorly. Do you have any performance data?
  
• Nebraska > Lincoln. Confirmed by Quentin King and Sensorly. 7Mbps download speeds and 1.2MB upload speeds were observed.
  
• Nebraska > Norfolk. Confirmed by Sensorly. Do you have any performance data?
  
• Nebraska > Omaha > Council Bluffs Tower. This tower is confirmed by Sensorly and covers parts of Downtown Omaha. Listed in Nebraska, but technically in Iowa. Do you have any performance data?
  
• Nebraska > Omaha > La Vista Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Nebraska > Omaha > Regency West Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Nebraska > Omaha > Marian/NW Tower. Confirmed by staff at Marian High School. Do you have any performance data?
  
• Nevada > Indian Springs. Confirmed by Sensorly. Do you have any performance data?
  
• New Hampshire > Lebanon. Confirmed by Sensorly. Do you have any performance data? This tower is likely the same as the one providing service in White River Junction, Vermont.
  
• New Hampshire > Manchester. Confirmed by Sensorly. Do you have any performance data?
  
• New Hamsphire > Nashua > Central Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New Hampshire > Nashua > Airport/NW Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New Hamsphire > Nashua > Merrimack/Litchfield Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New Jersey > Asbury Park. Confirmed by Anthony Arlaus and Sensorly. Download speeds up to 9Mbps were observed.
  
• New Jersey > Atlantic City > Pleasantville Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New Mexico > Alamogordo. Confirmed by message posts and Sensorly. This tower is reported as having limited backhaul with speeds between 1Mbps and 4Mbps.
  
• New Mexico > Albuquerque > Central. Confirmed by me and Sensorly. Speeds up to 8.8 Mbps download and 1.5 upload observed.
  
• New Mexico > Albuquerque > East Tower. Confirmed by me and Sensorly. This tower functions full speed 6MB to 8Mbps download and 1.5 upload with full signal.
  
• New Mexico > Carlsbad. Confirmed by Sensorly. Do you have any performance data?
  
• New Mexico > Farmington. Confirmed by Sensorly. Do you have any performance data?
  
• New Mexico > Las Cruces. Confirmed by message posts and Sensorly. Do you have any performance data?
  
• New Mexico > Las Vegas. Confirmed by me and Sensorly. Speeds originally limited to 1.5Mbps up and down, the first year of service. However, speeds were recently observed over 8Mbps download and 1.5Mbps upload.
  
• New Mexico > Santa Fe. Confirmed by me and Sensorly. Speeds up to 9.1 Mbps download and 1.5 Mbps upload observed.
  
• New York > Albany > St. Peters Hospital/New Scotland Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Albany > North/Bishops Gate Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Albany > West/SUNY Albany Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Albany > SE Schenectady Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Albany > Cohoes Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Albany > Nassau Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Bath. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Binghamton. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Buffalo > NE/Kensington Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Buffalo > North Tonawanda Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Corning. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Elmira > Horseheads Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Hornell. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Ithaca. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Rome. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Salamanca. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Saugerties. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Utica > South/New Hartford Tower. Confirmed by Sensorly. Do you have any performance data?
  
• New York > Utica > North Tower. Confirmed by Sensorly. Do you have any performance data?
  
• North Carolina > Albemarle. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Asheville > East/Black Mountain. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Eden. Confirmed as operating on Sensorly. Do you have any performance data?
  
• North Carolina > Fayetteville. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Goldsboro. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Greenville. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Hickory. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > New Bern. Confirmed by Sensorly. Do you have any performance data?
  
• North Carolina > Reidsville. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Roanoke Rapids. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Rocky Mount. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Wilmington. Confirmed at Sensorly. Do you have any performance data?
  
• North Carolina > Wilson. Confirmed at Sensorly. Do you have any performance data?
  
• North Dakota > Fargo/Moorhead. Confirmed as operating on Sensorly. Do you have any performance data?
  
• Ohio > Sandusky. Confirmed as operating by Bob Risner and Sensorly. Speeds of up to 7.4MB download and 1.1 MB upload were observed.
  
• Oklahoma > Ada. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Altus. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Davis/Sulphur. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Duncan. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Lawton. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Muskogee. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Oklahoma City > NW/Lyons Park Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Oklahoma > Oklahoma City > South/Crestline Park Tower. Confirmed by Richard McGee and Sensorly. Speeds up to 8.5MB were observed.
  
• Oklahoma > Oklahoma City > Edmond/Glen Eagles Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Oklahoma > Oklahoma City > Norman Tower. Confirmed by Sensorly. Do you have any performance data?
  
• Oklahoma > Stillwater. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Tahlequah. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Tulsa > Heritage Hill/North Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Tulsa > 44-244 Split/NE Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Tulsa > Bristol Park/SE Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Watonga. Confirmed at Sensorly. Do you have any performance data?
  
• Oklahoma > Weatherford. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Altoona. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > DuBois. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Erie. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Franklin/Oil City. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Milton. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > New Castle. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Scranton. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Shamokin. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Sharon. Confirmed at Sensorly. Do you have any performance data?
  
• Pennsylvania > Sunbury. Confirmed at Sensorly. Do you have any performance data?
  
• South Carolina > Charleston > Central Tower. Confirmed at Sensorly. Do you have any performance data?
  
• South Carolina > Charleston > Goose Creek/Summerville Tower. Confirmed at Sensorly. Do you have any performance data?
  
• South Carolina > Florence. Confirmed by S4GRU Member owensri2 as operating. owensri2 observed 5MB download and 1MB upload speeds.
  
• South Carolina > Greenville/Spartanburg > Greenville Tower. Confirmed at Sensorly. Do you have any performance data?
  
• South Carolina > Greenville/Spartanburg > Spartanburg Tower. Confirmed as operating by Jon Cooley. Speeds up to 9.3 MB download and 1.4 MB upload were observed.
  
• South Carolina > Hartsville. Confirmed by S4GRU Fan Clausell Colton and S4GRU Member owensri2 as operating. owensri2 observed 9MB download and 1.5MB upload speeds.
  
• South Carolina > Myrtle Beach > Red Hill/Conway Tower. Confirmed at Sensorly. Do you have any performance data?
  
• South Carolina > Myrtle Beach > South/Duck Pond Tower. Confirmed at Sensorly. Do you have any performance data?
  
• South Carolina > Orangeburg. Confirmed by a user on Sprint Forums. Do you have any performance data?
  
• South Carolina > Sumter. Confirmed at Sensorly. Do you have any performance data?
  
• South Dakota > Sioux Falls. Confirmed by Sensorly. Do you have any performance data?
  
• Tennessee > Chattanooga > East/Ridgeside Tower. Confirmed as operating on Sensorly. Do you have any performance data?
  
• Tennessee > Crossville. Confirmed as operating on Sensorly. Do you have any performance data?
  
• Texas > Bryan. Confirmed as operating on Sensorly and by Keith Rogers. This tower has slow speeds due to limited backhaul. Speeds around 1MB to 1.5MB down and up observed on 4G signal.
  
• Texas > El Paso > East Tower. Confirmed as operating on Sensorly. Do you have any performance data?
  
• Texas > Kerrville. Confirmed as operating on Sensorly. Do you have any performance data?
  
• Vermont > White River Junction. Confirmed as operating on Sensorly. Do you have any performance data? This tower is likely the same as the one providing service in Lebanon, New Hampshire.
  
• Virginia > Blacksburg. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Christiansburg. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Fredericksburg. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Harrisonburg. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Martinsville/Collinsville > Collinsville Tower. Confirmed by Jeremy Amos and Sensorly. Speeds up to 8.4MB download and 1.4MB upload reported.
  
• Virginia > Norfolk/Tidewater > Norfolk Central Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Norfolk/Tidewater > Virginia Beach/Expressway Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Norfolk/Tidewater > Newport News Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Onancock. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Radford. Confirmed at Sensorly. Do you have any performance data?
  
• Virginia > Winchester. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Moses Lake. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Olympia > Olympia Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Olympia > Lacey Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Port Angeles. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Spokane > Spokane Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Spokane > Spokane Valley Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Washington > Walla Walla. Confirmed at Sensorly. Do you have any performance data?
  
• West Virginia > Charleston > Central Tower. Confirmed at Sensorly. Do you have any performance data?
  
• West Virginia > Charleston > St. Albans Tower. Confirmed at Sensorly. Do you have any performance data?
  
• West Virginia > Huntington (Tri-Cities). Confirmed at Sensorly. Do you have any performance data?
  
• West Virginia > Martinsburg > NW Tower. Confirmed at Sensorly. Do you have any performance data?
  
• West Virginia > Martinsburg > Inwood. Confirmed at Sensorly. Do you have any performance data?
  
• West Virginia > Parkersburg > Downtown Tower. Confirmed at Sensorly. Do you have any performance data?
  
• Wyoming > Cheyenne. Confirmed at Sensorly. Do you have any performance data?
  

Unconfirmed Phantom Sites:

• California > Fallbrook. A blips appears on Sensorly's site along I-15 near the CA-76 exit, SE of Fallbrook towards Paia. Looking for confirmation that there is a signal in this location.
  
• California > Moreno Valley. A blip appears on Sensorly's site on I-215 on the west side of Moreno Valley near Edgemont. Looking for verification that this is real coverage from a protection site.
  
• California > Perris. A double blip of coverage has shown up on Sensorly on the I-215 corridor through Perris. Looking for verification of this protection site.
  
• California > Ventura/Oxnard. It appears as there is pretty extensive coverage from one or two protection sites in the Ventura and Oxnard areas as reported from Sensorly.com. Looking for some independent verification.
  
• Michigan > Eaton Rapids/Springport. In a remote spot between the South Central Michigan towns of Eaton Rapids and Springport, a blip of coverage is hown up on Sensorly's maps. Is this a legit prptection site? Or a GPS malfunction?
  
• Minnesota > Cloquet. This town is not showing up on Clear's coverage maps as having service. However, there are significant service infomation uploaded to Sensorly. Have you used this signal? Let us know!
  
• New Mexico > Hobbs. This town is not showing on Clear's coverage maps, but there was a mysterious blip that showed up on Sensorly a few miles west of town. Looking for confirmation if any Sprint 4G users go through this area. Could be a GPS error on the device that reported it to Sensorly.
  
• North Carolina > Rocky Mount/Wilson Regional Airport. There is definitely confirmed Protection Sites in the cities of Rocky Mount and Wilson. However, there is a blip along I-95 that has shown up on Sensorly near the Rocky Mount/Wilson Regional Airport. This area would be out of range of the other two towers. Is this a Phantom Site not shown on Clear's Coverage Maps?
  
• Pennsylvania > Allentown/Bethlehem. This city is not showing on Clear's coverage maps, but there was a mysterious blip that showed up on Sensorly just south of Downtown Bethlehem. I have now seen one post on a Sprint Message board regarding someone using this site. I'm looking for one more credible confirmation before I move this to "CONFIRMED."
  
• Texas > Milford. Right along I-35E, between Dallas and Hillsboro, a blip of coverage is showing up on Sensorly's website, that is not shown on Clear's coverage maps. Looking for confirmation of this site.
  

Unconfirmed Roaming Site:

(These towns do not have Sprint service. Sprint users roam in these areas. There is a known problem where Sprint Android devices will not connect to 4G WiMax when they are roaming. If you connect in one of these cities, let us know!!!)

• Alabama > Jackson.
  
• Alaska > Juneau.
  
• California > Avenal.
  
• California > Sonora.
  
• Colorado > Alamosa.
  
• Kansas > Beloit.
  
• Kentucky > Whitesburg.
  
• Maine > Belfast.
  
• Maine > Caribou.
  
• Maine > Paris/Norway.
  
• Maine > Presque Isle > North Tower.
  
• Maine > Presque Isle > South Tower.
  
• Maine > Rockland.
  
• Maine > Van Buren.
  
• Michigan > Houghton/Hancock.
  
• Michigan > Iron Mountain/Kingsford.
  
• Michigan > Ironwood/Hurley WI
  
• Michigan > Ishpeming/Negaunee
  
• Michigan > Marquette
  
• Mississippi > Kosciusko.
  
• Mississippi > Philadelphia.
  
• Mississippi > Ripley.
  
• Mississippi > Waynesboro.
  
• Mississippi > Yazoo City.
  
• Montana > Billings > Central Tower.
  
• Montana > Billings > North Tower.
  
• Montana > Great Falls.
  
• Montana > Helena.
  
• Montana > Kalispell.
  
• Nebraska > Fairbury.
  
• Nebraska > Lexington.
  
• Nebraska > O'Neill.
  
• Nebraska > Scottsbluff.
  
• New York > Ogdensburg.
  
• North Dakota > Bismarck.
  
• Oklahoma > Stigler.
  
• Pennsylvania > Emporium.
  
• Pennsylvania > Kane.
  
• South Dakota > Pierre.
  
• South Dakota > Rapid City.
  
• Vermont > St. Johnsbury.
  
• Wyoming > Green River.
  
• Wyoming > Riverton.
  
• Wyoming > Rock Springs.
  
• Wyoming > Sheridan.
  
• Wyoming > Thermopolis.
  

Need Confirmation:

• Alabama > Anniston > South Anniston/Oxford. Service needing confirmation.
  
• Alabama > Anniston > North Anniston/Alexandria. Service needing confirmation.
  
• Alabama > Anniston > East Tower/Iron City. New tower reported 7/26/2011. Service needing confirmation.
  
• Alabama > Auburn. Service needing confirmation.
  
• Alabama > Birmingham > Fairfield. Service needing confirmation.
  
• Alabama > Demopolis. Service needing confirmation.
  
• Alabama > Fort Payne. Service needing confirmation. However, Sprint has spotty coverage in the area and you may not be able to connect if you have a roaming signal.
  
• Alabama > Gadsden > East Gadsden Tower. Service needing confirmation.
  
• Alabama > Gadsden > Rainbow City Tower. Service needing confirmation.
  
• Alabama > Huntsville > Madison Tower. Service needing confirmation.
  
• Alabama > Jasper. Service needing confirmation.
  
• Alabama > Mobile > Airport/DiGrado Tower. Service needing confirmation.
  
• Alabama > Montgomery > Prattville. Service needing confirmation.
  
• Alabama > The Shoals > Florence Tower. Service needing confirmation.
  
• Alaska > Fairbanks. Service needing confirmation.
  
• Arizona > Flagstaff. Service needing confirmation.
  
• Arizona > Globe. Service needing confirmation.
  
• Arizona > Nogales. Service needing confirmation.
  
• Arizona > Yuma > Fortuna Foothills East. Service needing confrimation.
  
• California > Eureka > Arcata Tower. Service needing confirmation.
  
• California > Watsonville. Service needing confirmation.
  
• Colorado > Grand Junction. Service needing confrimation.
  
• Colorado > Sterling. Service needing confrimation.
  
• Connecticut > Norwich. Service needing confirmation.
  
• Delaware > Laurel/Seaford. Service needing confirmation.
  
• Florida > Bonita Springs. Service needing confrimation.
  
• Florida > Brooksville. Service needing confrimation.
  
• Florida > Fanning Springs/Old Town. Service needing confrimation.
  
• Florida > Key West. Service needing confrimation.
  
• Florida > Long Sound. This is an odd tower location as it's near the first bridge of the Overseas Highway to the keys. Service needing confirmation.
  
• Florida > Milton. Service needing confrimation.
  
• Florida > Newberry. Service needing confrimation.
  
• Florida > Sarasota/Bradenton > South Bradenton/Oneco Tower. Service needing confrimation.
  
• Georgia > Flowery Branch. Service needing confirmation.
  
• Georgia > Gainesville. Service needing confirmation.
  
• Hawaii > Island of Hawaii > Hilo Tower. Service needing confirmation.
  
• Hawaii > Island of Kauai > Lihue Tower. Service needing confirmation.
  
• Illinois > Carterville. New tower reported 7/17/2011. Service needing confirmation.
  
• Illinois > Marion. Service needing confirmation.
  
• Illinois > Murphysboro. Service needing confirmation.
  
• Illinois > Ottawa. New tower reported 7/27/2011. Service needing confirmation.
  
• Indiana > Shelbyville. New tower reported 7/17/2011. Someone posted on a message board that they couldn't connect to tower. Looking for corroboration.
  
• Iowa > Marshalltown. Service needing confirmation.
  
• Iowa > Oelwein. Service needing confirmation.
  
• Kansas > Atchison. Service needing confirmation.
  
• Kansas > Coffeyville. Service needing confirmation.
  
• Kansas > Concordia. Service needing confirmation.
  
• Kansas > Dodge City. Service needing confirmation.
  
• Kansas > Ellsworth. Service needing confirmation.
  
• Kansas > Garden City. Service needing confirmation.
  
• Kansas > Great Bend. Service needing confirmation.
  
• Kansas > Hays. Service needing confirmation.
  
• Kansas > Independence. Service needing confirmation.
  
• Kansas > Parsons. Service needing confirmation.
  
• Kansas > Pratt. Service needing confirmation.
  
• Kansas > Russell. Service needing confirmation.
  
• Louisiana > Leesville > South Leesville/Newllano Tower. Service needing confirmation.
  
• Louisiana > Leesville > Fort Polk South Tower. Service needing confirmation.
  
• Louisiana > Monroe > NE/University Tower. Service needing confirmation.
  
• Louisiana > Natchitoches. Service needing confirmation.
  
• Louisiana > Ruston. Service needing confirmation.
  
• Maine > Augusta > Gardiner Tower. Service needing confirmation.
  
• Maine > Bangor > Coldbrook/SW Tower. Service needing confirmation.
  
• Maine > Bangor > Orono Tower. Service needing confirmation.
  
• Maine > Bangor > Orrington Tower. Service needing confirmation.
  
• Maine > Ellsworth. Service needing confirmation.
  
• Maine > Waterville. Service needing confirmation.
  
• Maryland > Cumberland. New tower reported 8/2/2011. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with roaming in the area.
  
• Maryland > Hagerstown. Service needing confirmation.
  
• Massachusetts > Adams. Service needing confirmation.
  
• Massachusetts > Cape Cod > Barnstable Tower. Service needing confirmation.
  
• Massachusetts > Cape Cod > East Falmouth/Mashpee Tower. Service needing confirmation.
  
• Massachusetts > Cape Cod > Harwich Tower. Service needing confirmation.
  
• Massachusetts > Leominster. Service needing confirmation.
  
• Massachusetts > Pittsfield. Service needing confirmation.
  
• Massachusetts > Springfield > Holyoke Tower. Service needing confirmation.
  
• Michigan > Sault Ste. Marie. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with roaming in the area.
  
• Minnesota > Wadena. New tower reported 7/26/2011. Service needing confirmation.
  
• Mississippi > Amory. Service needing confirmation. Blip of coverage is showing on Sensorly.com, but appears out of range. May have connection issues as there is only 1xRTT in the area. Looking for someone to upload more data.
  
• Mississippi > Aberdeen. Service needing confirmation. Blip of coverage is showing on Sensorly.com, but appears out of range. May have connection issues as there is only 1xRTT in the area. Looking for someone to upload more data.
  
• Mississippi > Booneville. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Mississippi > Columbus. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Mississippi > Corinth. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Mississippi > Greenville. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Mississippi > Greenwood. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Mississippi > Jackson > NE/Ridgeland. Service needing confirmation.
  
• Mississippi > McComb. Service needing confirmation.
  
• Mississippi > Natchez. Service needing confirmation.
  
• Mississippi > Oxford. Service needing confirmation.
  
• Mississippi > Pascagoula. Service needing confirmation.
  
• Mississippi > Starkville. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Mississippi > Tupelo. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Nebraska > York. Service needing confirmation.
  
• New York > Olean/Allegany. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• New York > Poughkeepsie. Service needing confirmation.
  
• New York > Wellsville. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• North Carolina > Asheville > Central Tower. Service needing confirmation.
  
• North Carolina > Asheville > South/Fletcher. Service needing confirmation.
  
• North Carolina > Asheville > West/Candler. Service needing confirmation.
  
• North Carolina > Elizabeth City. Service needing confirmation.
  
• North Carolina > Hendersonville. Service needing confirmation.
  
• North Carolina > Jacksonville. Service needing confirmation.
  
• North Carolina > Kinston. Service needing confirmation.
  
• North Carolina > Laurinburg. Service needing confirmation.
  
• North Carolina > Lumberton. Service needing confirmation.
  
• North Carolina > Morehead City/Atlantic Beach. Service needing confirmation.
  
• North Carolina > Pinehurst/Southern Pines. Service needing confirmation.
  
• North Carolina > Rockingham. Service needing confirmation.
  
• North Carolina > Sanford. Service needing confirmation.
  
• North Carolina > Waynesville. Service needing confirmation.
  
• Ohio > Marietta. Service needing confirmation.
  
• Ohio > Marion. New tower reported 7/26/2011. Service needing confirmation.
  
• Oklahoma > Ardmore. Service needing confirmation.
  
• Oklahoma > Bartlesville. Service needing confirmation.
  
• Oklahoma > Checotah. Service needing confirmation.
  
• Oklahoma > Elk City. Service needing confirmation.
  
• Oklahoma > Enid. Service needing confirmation.
  
• Oklahoma > Frederick. Service needing confirmation.
  
• Oklahoma > McAlester. Service needing confirmation.
  
• Oklahoma > Miami. Service needing confirmation.
  
• Oklahoma > Okmulgee. Service needing confirmation.
  
• Oklahoma > Ponca City. Service needing confirmation.
  
• Oklahoma > Poteau. Service needing confirmation.
  
• Oklahoma > Woodward. Service needing confirmation.
  
• Oregon > Coos Bay. Service needing confirmation.
  
• Oregon > La Grande. New tower reported 8/2/2011. Service needing confirmation.
  
• Pennsylvania > Bradford. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > Clarion. New tower reported 8/9/2011. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > Ellwood City. Service needing confirmation.
  
• Pennsylvania > Frackville. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• Pennsylvania > Indiana. Service needing confirmation.
  
• Pennsylvania > Lewistown. Service needing confirmation.
  
• Pennsylvania > Lock Haven. New tower reported 8/2/2011. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > Punxsutawney. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > Ridgway. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > St. Marys. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > State College. Service needing confirmation.
  
• Pennsylvania > Schuylkill Haven. Service needing confirmation. May have connection issues as this is a limited 1xRTT data area with a lot of roaming.
  
• Pennsylvania > Williamsport. Service needing confirmation. May have connection issues as there is only 1xRTT in the area.
  
• South Carolina > Beaufort. Service needing confirmation.
  
• South Carolina > Greenville/Spartanburg > Greer Tower. Service needing confirmation.
  
• South Carolina > Greenville/Spartanburg > Inman Tower. Service needing confirmation.
  
• South Carolina > Hilton Head Island. Service needing confirmation.
  
• South Carolina > Newberry. Service needing confirmation.
  
• Tennessee > Athens. Service needing confirmation.
  
• Tennessee > Chattanooga > North/Red Bank-Hixson Tower. Service needing confirmation.
  
• Tennessee > Cleveland. Service needing confirmation.
  
• Tennessee > Tazewell. New tower reported 7/26/2011. Service needing confirmation.
  
• Tennessee > Tullahoma. Service needing confirmation.
  
• Texas > El Paso > North Tower. This tower on the north side near Fort Bliss has not been confirmed as working.
  
• Texas > Lamesa. New tower reported 7/26/2011. Service needing confirmation.
  
• Vermont > Burlington > Downtown Tower. Service needing confirmation.
  
• Vermont > Burlington > Essex Tower. Service needing confirmation.
  
• Virginia > Danville. This tower has not been confirmed as working for Sprint 4G users.
  
• Virginia > Gloucester Courthouse. Service needing confirmation.
  
• Virginia > Lynchburg. Service needing confirmation.
  
• Virginia > Martinsville/Collinsville > Axton Tower. New tower reported 8/2/2011. Service needing confirmation.
  
• Virginia > Roanoke > Salem Tower. Service needing confirmation.
  
• Virginia > Williamsburg. Service needing confirmation.
  
• Washington > Sequim. Service needing confirmation.
  
• West Virginia > Charles Town/Wheatland. Service needing confirmation.
  
• West Virginia > Hurricane/Teays Valley. Service needing confirmation.
  
• West Virginia > Parkersburg > WVUP/South Tower. Service needing confirmation.
  
• Wisconsin > Marinette/Menominee MI. Service needing confirmation.
  

This Note is a listing of every single Protection Site in America (work in progress) and a confirmation whether it is working or not. This note will be updated daily as information changes and/or is discovered. Do your part! If you live in or near one of the areas needing confirmation, confirm the signal and post results to Sensorly website via their Android app and post in this forum. Thanks!!!

Migrated from Original Forum. Originally Posted 15 January 2011

Let us know if you come across a WiMax signal. I think you'll get LTE first, though.

Migrated from Original Forum. Originally Posted 01 August 2011 - 10:47 AM

Protection Site Black List! These cities will not likely be getting protection sites. The reason is, in these cities Clearwire is already broadcasting on 2.5GHz. So they are meeting FCC licensing requirements for minimum coverages already in this spectrum. The problem for Sprint users, is that they are broadcasting their legacy Pre-WiMax signals here. Not WiMax. So your Sprint devices don't detect it!

• Aberdeen/Hoquiam WA
  
• Anchorage AK
  
• Anderson CA
  
• Bend OR
  
• Carson City NV
  
• Central Point OR
  
• Chico CA
  
• Chippewa Falls WI
  
• Clarkston WA
  
• Cohasset Beach/Wesport WA
  
• Corning CA
  
• Dayton OH
  
• Duluth MN
  
• Eagle River AK
  
• Eau Claire WI
  
• Fernley NV
  
• Grants Pass OR
  
• Hermantown MN
  
• Klamath Falls OR
  
• Incline Village NV
  
• Jacksonville OR
  
• Lewiston ID
  
• Longview TX
  
• Madras OR
  
• Medford OR
  
• Middletown OH
  
• Minden/Gardnerville NV
  
• Moscow ID
  
• Myrtle Creek OR
  
• Orland CA
  
• Paradise CA
  
• Prineville OR
  
• Proctor MN
  
• Pullman WA
  
• Red Bluff CA
  
• Redding CA
  
• Redmond OR
  
• Reno/Sparks NV
  
• Roseburg OR
  
• St. Cloud MN
  
• Shasta Lake CA
  
• Sisters OR
  
• South Lake Tahoe CA
  
• Springfield OH
  
• Stateline/Kingsbury NV
  
• Superior WI
  
• Wenatchee WA
  

When Clear first started deploying their WiMax networks, they started with their Pre-WiMax markets first. Many, like Boise, Idaho and Jacksonville, Florida had their towers coverted from pre-WiMax to WiMax. However, about halfway through these conversions, Sprint started releasing WiMax devices and pressuring Clear to switch to major metro areas (which of course makes a lot of sense).

And then, as we all know, about halfway through the major market rollout, Clear started running into financial problems. Since they were running out of time to meet FCC Minimum Coverage Standards, they have largely abandoned Major Market Rollouts and running around and setting up Protection Sites.

However, the cities listed above are likely not to ever get protection sites. The Old Clearwire Pre-Wimax signals are still being broadcast in these cities, and they have pretty substantial coverage areas. So Clearwire is just going to jump right over them.

And since Sprint (and likely Clear too) are migrating toward LTE, it is likely these cities WILL NEVER see WiMax signals. Sad!

Cities the size of Dayton, Anchorage and Reno are secondary markets. This is a major oversight by Clear and Sprint. Tsk, tsk! Not to mention the major oversights of the primary markets of San Diego, Phoenix, Detroit, Memphis, Indianapolis, Birmingham...

Welcome to the new Sprint 4G Rollout Updates (S4GRU) website and forums. We have now jumped over to IP.Board from Spruz to host our new website and forums.

We used Spruz for Betas 1.0, 1.1 and 1.2. This allowed us to get our feet wet and get established online. The initial response during these betas far exceeded my expectations. I appreciate all of our members who tagged along for the experience (and their patience). However, it became apparent quickly that Spruz was too limited in function, capability and performance for our needs.

However, I feel that I have located a new home for us here at IP.Board. We are now beginning Beta 2.0 here. IP.Board's performance thus far has been stellar! Additionally, IP.Board also has a mobile HTML 5 website enabled for S4GRU! We are also working on an iPhone and Android app with them. And the forums are also already represented on the Tapatalk app and Forum Runner support should be enabled very soon.

I am excited about the future here at S4GRU now teamed up with IP.Board. And now I come to the part where I am depending on you...

Please rant and rave below...

Robert Herron

S4GRU Administrator