2026-09-27

Phone line types from carriers' filings, a number formatter, and pages for every phone source, signal, carrier and state

Numbers of 28 more North American carriers answer mobile or voip from the carrier holding the block, and GET /v1/phone/block lists only the range's own time zones. New pages: a phone number formatter, one page per phone data source and per phone risk signal, new North American area codes, US states and Canadian provinces, network carriers and phone statistics from public data. France's, the Netherlands' and the UK's ranges get pages cut the way each numbering plan cuts them.

Line types from what carriers file. Phone lookups now type the numbers of 28 more carriers from what each files with the FCC. In North America a number's line type cannot be read from the number itself, so these numbers now answer from the carrier holding the block. Wireless carriers' numbers answer line_type mobile: Boost Mobile, T-Mobile's former Powertel companies, Bell Atlantic Mobile (now Verizon Wireless), Liberty Mobile in Puerto Rico and the US Virgin Islands, Southern Linc, STPCS Joint Venture, and Fido in Canada. Numbers of VoIP providers that sell numbers, SIP trunks or programmable voice now answer line_type voip and is_virtual: true. That adds the virtual signal (+40) to risk_score, so such a number that also carries a signal worth more than 20 now scores above 60 and is refused by the default SMS policy. Cable companies' phone lines and wireline carriers still answer fixed_line_or_mobile. On NANPA's file of 25 September 2026, the share of allocated US thousands-blocks with a settled line type rises from 63.8% to 67.0%.
Time zones on GET /api/v1/phone/block. timezones now lists only zones in the range's own country: the +1 709 report no longer names America/Puerto_Rico. For North American codes it reads every exchange rather than twelve sampled numbers, so +1 867 names all five of its zones.
Fictional ranges have a length. A number a digit short or long of one of Ofcom's drama ranges is no longer taken for a fictional number. It now answers valid: false with the numbering plan's own reason and is free, where it answered valid and fictional and was charged: invalid_number for 020 7946 001, a digit short, and too_long for 020 7946 00181.
A free phone number formatter. /tools/phone-number-formatter takes up to 200 numbers and gives each in E.164, national and international form, with its country, the numbering plan's line type, time zones and local time, and whether it fits the plan. Numbers that don't fit get the lookup's reason and did-you-mean suggestion. Results can be copied as CSV, and the numbers are not stored. The page also publishes two tables derived from libphonenumber 9.0.37: every region whose trunk prefix is not 0 or whose numbers keep a leading 0 after the calling code (the North American 1, the 8 of Russia and Kazakhstan, Hungary's 06, Italy's kept 0), and every international call prefix other than 00. It explains why +44 (0)20 is wrong, citing ITU-T E.123.
A page for every phone data source. /tools/phone-number-lookup/sources gives every publisher a phone answer reads its own page: the ten regulators whose allocation tables are synced (NANPA, CNAC, Ofcom, ARCEP, ACMA, ACM, NAD, the CRT, UKE and MIMIT), libphonenumber, the two SMS-receiving lists and the FTC's reported-calls files. Each page names the files and their format, how often they are published and refreshed here, the terms as the publisher states them, which numbers a table is complete for, and what the installed copy holds as counts by status and distinct holders, never rows or names. It also says what the table cannot tell you. The index lists the regulators whose tables are not synced (Germany, Spain, Brazil, Ireland, Denmark and Switzerland), each with a dated reason, and has a Markdown twin at /tools/phone-number-lookup/sources.md, also carried in llms-full.txt. The phone product page's data-sources table links each dataset to its publisher's page, and its Licence column is now Terms and states what each publisher actually publishes: no terms of use from NANPA, CC0 for ACM's register, Ofcom copyright with acknowledgement, terms not confirmed for ACMA and the CRT. The status page lists NANPA's NPA report, the table of every North American area code, synced daily and dated by the date NANPA puts on the file.
A page for every phone risk signal. Each of the 18 phone signals, from fictional (+80) to reported_unwanted_calls (+20), has its own reference page at /docs/signals/phone/{signal} with a Markdown twin: the weight, the dataset it is read from, the field it reads, whether the default SMS policy blocks on it, what it cannot tell you, what to do, and an example answer. /docs/signals now has an email section and a phone section, so a phone reader no longer lands on the email weight: disposable is +80 on an email answer and +70 on a phone one. The IP and address weights stay in their guides until they get pages of their own. The risk-score table in the phone intelligence guide and its Markdown twin show each signal's slug, linked to its page and anchored as #signal-{slug}.
North American area codes. Area-code pages now show NANPA's facts about the whole code: the state or province, the codes sharing its area, when it went into service, how local calls are dialled and whether relief planning is under way. They also show the rate centres its codes are assigned for, the codes and thousands-blocks assigned in the last 12 months and those not yet in service, and every assigned central office code with its rate centre and the code holder's network brand. Every table is original allocation, and there is no page per code. A code no number can ring in yet says so in NANPA's terms, with NANPA's dates, instead of "line types unknown": codes whose every assigned code waits for its effective date (357, 483, 837, 861), overlays in service with no code assigned (465, 471, 748 and seven more, now indexed) and planned codes (273), each with whether libphonenumber accepts its numbers yet. New and upcoming North American area codes, with a Markdown twin, lists from NANPA's NPA report the codes put in service in the last 24 months, those assigned but not yet in service and those in relief planning, each with its overlay, its central office code counts, its first dated code and whether libphonenumber accepts its numbers yet.
States and provinces. Each US state and Canadian province with more than one area code, about 50, has a page at /tools/phone-number-lookup/countries/{us|ca}/{state}: its area codes with overlays and in-service dates from NANPA's NPA report, the allocated central office codes counted by rate centre or exchange area, the pooled share (US), the codes and thousands-blocks assigned in the last twelve months, and the codes by network brand, as original allocation and as shares of the regulator's table.
Network carriers. /tools/phone-number-lookup/carriers has a page for each of about 45 brands in the US, Puerto Rico, Canada, the UK and France: the legal entities and codes the regulator lists, the numbers they were allocated (counted in numbers, as a share of the regulator's table), how a lookup reads those numbers, thousands-blocks held inside other brands' pooled US codes, assignments by year and the area codes with most of the brand's numbers. The carrier on a lookup is the block's original holder, not the caller or the network serving the number today. The pages are counted weekly from the NANPA, CNAC, Ofcom and ARCEP tables, on Mondays after the phone feed sync, and listed in sitemap-phone-carriers.xml.
Phone statistics from public data. /statistics/phone, with a Markdown twin and a CSV of Spaw's derived counts under CC BY 4.0, counts where the caller IDs consumers report to the FTC sit in the US numbering plan. On 26 September 2026, 60.8% of the 489,940 US-area-code numbers reported between 28 June and 23 September sat in blocks NANPA lists under VoIP providers, against 19.7% of all allocated US numbers; both shares are lower bounds, because they count only holders on Spaw's classification list. Toll-free numbers are 12.3% of reported caller numbers but 49.3% of those reported at least three times on two days. The page also gives the FTC counts by month, the codes and thousands-blocks NANPA, CNAC and ARCEP assigned in the last 7, 30 and 365 days, and SMS-receiving listings by calling code. Every FTC figure carries three statements: this is not the Do Not Call Registry, it says nothing about whether you may call or text a number, and the reports are unverified and caller ID is often spoofed.
Country pages. Each region's page now says how its numbers are dialled and written, read from libphonenumber's numbering metadata: the trunk prefix, the international prefix (and, where the metadata allows several and prefers none, every prefix it allows), the number lengths per line type, the digits every mobile number starts with, whether mobile and fixed-line numbers share ranges, and one number written nationally, internationally and as dialled from the US and the UK. SMS-receiving listings are counted for the region's own numbers, never worldwide or per calling code, with the listings that still score disposable first. The countries index lists each region's trunk and international prefix, and a page for a region with no synced table says what its carrier answer is: the range's original network in libphonenumber's carrier data, which a port never updates.
France, the Netherlands and the UK by the plan's own codes. France has one page per zone, 01 Île-de-France to 05 South-west France, named from ARCEP's plan, which since 2023 allows a 01 to 05 number anywhere in metropolitan France, and pages for its 08x and 09 ranges. The Netherlands has a page per area code (010, 0111, 0229 Hoorn …) and one 06 page. Old two-digit pages redirect where all their blocks moved to one page, and France's 06 and 07 mobile ranges no longer have indexed pages, because ARCEP's table misses part of them. The UK's non-geographic ranges have pages named by type, such as "074 mobile numbers" and "070 personal numbers": 03x, 055, 056, 070, 071 to 079, 080, 084, 087, 090, 091 and 098. The United Kingdom's country page lists its 07 numbers by original range holder, counted in numbers from Ofcom's table: VodafoneThree 38.0%, Virgin Media O2 28.9% and EE 27.5% of the allocated mobile numbers, with notes on 070 personal numbers, 076 pagers and the Crown Dependencies' 07 prefixes. Where a regulator's blocks differ in size, area-code pages rank holders and brands by the numbers their blocks cover rather than by rows, with a numbers column: on France's 01 that puts Orange at about 59% of the numbers, where the rows showed 4.5%. The GET /api/v1/phone/block report still counts rows. Outside North America and the UK's area codes, a range page with fewer than 100,000 allocated numbers still renders but is no longer indexed.

markdown version: /changelog/2026-09-27-phone-line-types-from-carrier-filings-a-number-formatter-and-pages-for-every-phone-source.md · atom feed: /changelog.atom

All releases