FTC complaints
The FTC publishes the Do Not Call complaints of each weekday (weekends in Monday's file) and keeps about five weeks of files online. We download every file and add it to our archive, which starts on September 11, 2026. From each complaint we keep only the first three digits of the reported caller ID (the area code), the day the complaint was created, the subject, the robocall flag, the consumer's state and whether the consumer's own area code was the same. The phone numbers themselves are never stored or shown. A caller ID that is not a valid ten-digit North American number is counted in totals but not under any code. Consumers may leave the robocall question blank: robocall shares are of the complaints that answer it, and a blank never counts as “no”. Below 20 complaints a page prints counts, not percentages, and below 5 it does not show where the people who complained live. Headline counts cover the last 30 days (Sep 23 – Oct 22, 2026); once a whole calendar month is in the archive, the latest complete month is used instead.
Exchanges and places
NANPA lists every prefix with its rate center, an abbreviated exchange name such as “NWYRCYZN01”. We match rate centers to Census places of the same state by exact name, expanded abbreviations, the ten-letter truncation and, for names with dropped vowels, a unique in-order letter match; 162 matches are set by hand. 15,079 of 18,449 rate centers matched. Unmatched exchanges are shown under their NANPA name. A Census place can span several counties; the file does not say which county an exchange serves, so only places within one county count toward a code's counties. For about a hundred of the most searched codes the name a code is known by is set by hand from its largest rate centers or a public document (a state commission order or a NANPA planning letter), named on the code page; for the others the main place is the matched place with the most prefixes, if it holds at least a tenth of them.
Time zones
NANPA gives each code a time zone. An overlay serves the same exchanges as the codes it overlays, so a code shows every zone of its overlay group; a few zones NANPA leaves out (the Navajo Nation, Labrador, Nunavut, the western Aleutians, the Lower North Shore of Quebec) are added from the IANA tz database, each with its source. The clocks use your browser's copy of that database.
Forecasts
Exhaust years come from NANPA's twice-yearly NRUF forecast (April 2026 edition), and only from that edition: where it gives no date (Canadian codes with an exhaust beyond 2048, codes more than 100 years from exhaust) the page says so instead of repeating an older forecast. Forecasts move from one edition to the next; each code page shows the change.
Which pages search engines see
A geographic area code page is offered to search engines when it has a NANPA record with a start date and location, at least one exchange tied to a place, and FTC complaints at a pace of at least 120 a year over at least 28 days of the archive. FTC complaints also measure how long a code has been in use, so a code that started less than 36 months ago, or one searched in Bing at least as often as the least searched code the FTC pace admits (48 searches a month), is offered too. Toll-free code pages always; planned codes when NANPA lists a start date or planning letter; state and province pages with at least 2 codes; monthly reports with at least 100,000 complaints. Other pages stay available to visitors with a noindex tag. Today 444 of 468 area code pages pass.