Why does the federal map show a provider that will not sell me service?

Because providers report where they believe they could complete a routine installation within 10 business days at standard charges, and nobody verifies that claim before the map is published. The rule they file against, 47 CFR 1.7001(a)(19), calls that a standard broadband installation. A claim that fails in practice stays on the map until somebody challenges it at that specific location.

How current is the National Broadband Map?

It runs on a six-month cycle. Under 47 CFR 1.7004(b) providers file data as of December 31 by March 1, and data as of June 30 by September 1. Publication can only come after the deadline, so the newest vintage on the map always describes a date that has already passed. The FCC notice for the current round (DA 26-630, released 26 June 2026) opened the window for June 30, 2026 data on 1 July 2026 with a 1 September 2026 deadline. Check the vintage label on the map before you trust any pin.

What evidence does an availability challenge require?

Section 1.7006(d)(1) lists it: your contact information, the street address or coordinates in dispute, the provider's name, a dispute category from the portal's list, evidence and details of a request for service (the date, method and content of the request and the provider's response, or evidence such as a screenshot or email showing no availability), a representation that you live or do business there, and a certification that your statements are true. A consumer has to make an initial showing by a preponderance of the evidence.

Internet Providers by Address: What Is Really Available

Q: Does a fixed wireless coverage map mean I will qualify?

No. Fixed wireless coverage on the federal map comes from a propagation model built to fixed parameters — a cell edge probability of not less than 75 percent of receiving the maximum advertised speeds, a cell loading factor of not less than 50 percent, and receiver heights of four to seven meters. That is a prediction about radio, not a decision about your account. Carriers gate sign-ups separately on how much capacity a sector has left, which is why a covered address can still be refused.

The federal map has this address down as served with gigabit fiber. Four providers, asked directly, have said no.

That gap is where this site starts, and the first thing worth saying about it is that the map is not simply lying. It is answering a narrower question than the one you typed into it. Once you know which question it answers, the map becomes useful again — as a list of companies to go make say no in writing, which turns out to be the only answer that means anything.

The map answers "could we, in theory," not "will you sell me this"

Providers file their coverage twice a year into the Broadband Data Collection. What they must submit, under 47 CFR 1.7004(c)(1) (read 18 August 2026), are the areas where they have "actually built out" network infrastructure such that they are able to provide service and are "capable of performing a standard broadband installation."

That last phrase is a defined term, and it is the whole ballgame. Section 1.7001(a)(19) defines a standard broadband installation as initiation of service "with no charges or delays attributable to the extension of the network of the provider," through routine installation "that can be completed not later than 10 business days after the date on which the service request is submitted."

So the pin at your house is a company's own assertion that it could hook you up inside ten business days without building anything unusual. No FCC engineer confirmed it before publication. The provider certified it, and it went on the map.

The filing rules also draw the edges of those polygons with a ruler rather than a wire. Terrestrial fixed providers may not report coverage beyond a maximum distance from an aggregation point: 6,600 route feet from the DSLAM for DSL at 25/3 Mbps or above, 12,000 route feet for hybrid fiber coax, 196,000 route feet for fiber to the premises, and generally no more than 500 feet from a deployed line to the parcel boundary of a served location. There are carve-outs — a current subscriber, a previous subscriber on the same technology, a universal service or other build obligation already underway, or a waiver. A polygon boundary is an engineering assumption with exceptions bolted to it, and your driveway may sit on the far side of the assumption.

Fixed wireless is modeled rather than measured. Providers submitting coverage maps have to run a propagation model on parameters the rule fixes for them: a cell edge probability of not less than 75 percent of receiving the maximum advertised download and upload speeds, a cell loading factor of not less than 50 percent, and receiver heights within a range of four to seven meters. Your trees, the hill behind the house, and a receiver mounted where you can actually reach it are not in that model.

One more field nobody reads: fixed providers must flag, for each shapefile or location, whether the reported service is available to residential customers, business customers, or both. A pin can be a business offering at a business price.

It is also old, and by design

The schedule sits in 1.7004(b): filings each year on or before March 1 for data as of December 31, and on or before September 1 for data as of June 30. Publication can only follow the filing deadline, never the date the data describes.

Follow one vintage through. The FCC opened the window for December 31, 2025 data on 2 January 2026 with a 2 March 2026 deadline (DA 25-1080, released 18 December 2025). The round running as I write this covers June 30, 2026 and does not close until 1 September 2026 (DA 26-630, released 26 June 2026). That fixes the ceiling on how fresh any pin can be today: the summer data has not been filed yet, let alone validated and published, so the newest picture the map can be showing you is one taken last December. The page labels the vintage. Read the label before you argue with the pin. DA 26-630 also sets a retention policy worth knowing: the four most recent vintages stay viewable on the map, which is two years of history, and older ones survive only as downloadable exports.

There is a quieter consequence in that notice. Providers must re-report locations that were previously removed through the challenge, verification or audit processes if service was available there as of the reporting date, and since 29 April 2026 there has been a formal coverage restoration process for putting removed locations back with infrastructure data behind them. A correction you win is a correction for that vintage. It is not a permanent finding, and re-checking your own address after each publication is not paranoia.

The map can be wrong in two completely different ways

They have different forms and different clocks, and people file the wrong one constantly.

The location itself is wrong. Your house is missing from the Broadband Serviceable Location Fabric, or it is there with the wrong address, wrong coordinates, wrong unit count for a duplex, or the wrong building type. That is a Fabric challenge. It runs on a deadline rather than a conversation: submissions must be in by 1 September 2026 to be reviewed ahead of the December 2026 Fabric revision. Since the FCC's Sixth Report and Order, effective 24 July 2026, providers are no longer notified of Fabric challenges during the development cycle or given a chance to respond to them there.

The service claim is wrong. Your location exists and a provider says it serves you. That is an availability challenge under 1.7006(d), and it is adversarial. The portal alerts the provider. Within 60 days the provider must either accept the allegation — and then file the correction within 30 days — or deny it and put evidence in the portal, and in front of you, that it serves or could and is willing to serve the location. A denial opens another 60 days for the two of you to try to resolve it. Silence is expensive for them: failure to respond within the applicable timeframe "shall result in a finding against the provider," with corrections due within 30 days or the Commission makes them itself. While all this runs, your location shows on the map as in dispute, pending resolution.

The standard of proof for a consumer is a preponderance of the evidence, lower than the clear and convincing showing a city or state has to make. And the evidence the rule asks a consumer for is not a speed test. It is the request you made and the answer you got, or evidence showing no availability at that location: a screenshot of the provider's own order page, an email.

The ninety minutes that produce a real answer

Do these in order. Steps three and four generate the paperwork everything later depends on.

Treat the map as a lead list. Open your address on broadbandmap.fcc.gov and write down every provider, the technology, the maximum advertised speeds, the residential flag, and the data vintage shown on the page. Screenshot it with the URL and today's date visible.
The provider's own address checker is fed from the same records. Expect the same optimism from it. Run the address anyway, exactly as the map spells it, then again as it appears on your electric bill. Different normalization produces different answers more often than it should, and a "not available" that is really a typo is worth catching before you build a case on it.
Convert every "available" into an order attempt. Chat or phone, and ask four things: is this a standard installation at published rates, is there any construction or line extension charge, what is the earliest date a technician can be here, and can I have that in writing. What you want is an artifact — an order number, a scheduled date, a quote, or a refusal.
Measure the answer against ten business days. That is the yardstick in the filing rule. An install date eight weeks out, or a construction quote of any size, means this is not a location where a standard broadband installation can be performed, which is the exact claim the provider filed. Save the transcript. Note the agent's name and the ticket number.
Local records reach where the federal map has nothing. Your city or county clerk holds the cable franchise agreement, its build-out obligations, and a named franchise contact. Your state broadband office almost certainly published something more granular during the BEAD challenge rounds. Your state public utility or public service commission keeps a list of certificated carriers and a consumer division that answers the phone. And regional wireless ISPs that never rank in search still show up in the provider list on the federal map.
Read the property. A pedestal at the lot line, tags on the pole, a weathered demarcation box left by a previous owner. Prior service at a location is one of the exceptions that lets a provider report coverage beyond those distance buffers, so evidence that someone was once connected here is both a clue and leverage.

A written refusal is the asset, not the setback

Capture four things from every contact: the date, the method, the content of your request, and the response. That is not my template. It is the list in 1.7006(d)(1)(v), and gathering it while you are already on the phone costs nothing.

The most valuable document you can walk away with is a construction quote. Charges or delays attributable to extending the network are precisely what the definition of a standard broadband installation excludes, so a quote for several thousand dollars of line extension is not evidence that service is available at your address. It is evidence that it is not, written by the provider, with a number on it.

Two timing notes if this check is part of a move or a switch. Verify the new address before you sign anything, because "fiber in the neighborhood" and "fiber to this unit" are different filings by the same company. And do not cancel the line you have until the replacement has a confirmed installation date — cancellation timing drives the early termination fee arithmetic and starts the equipment return clock, and neither is forgiving of a gap you did not plan for.

One date is already on the calendar

If the problem is your location — missing from the Fabric, wrong coordinates, a unit count that turns four apartments into one — the submission has to be in by 1 September 2026 to be considered for the December 2026 revision. That is two weeks from the day this posts.

If the problem is a provider's claim, there is no window, but there is a clock: file the availability challenge and the provider owes a reply in 60 days. Filing this week means an answer, or an automatic finding in your favor, by around the third week of October.

Either way the first move is the same, and it is one phone call. Ask a provider the map says serves you for an installation date, then write down what they said and when they said it.