Area codes

Area codes with multiple time zones

According to NANPA, 26 of the 433 area codes in service in the US and Canada span more than one time zone: 24 in the US and 2 in Canada. For a number in one of these codes, the area code alone can't tell you the contact's local time, which is the time that counts for calling-hour rules.

Source: NANPA NPA database, file dated October 10, 2026. Part of the US and Canada area code list.

All 26 area codes that span time zones

By time zone: 14 straddle Eastern and Central (Florida, Indiana, Kentucky, Michigan, Ontario (807) and Tennessee); 6 straddle Central and Mountain (Kansas, Nebraska, North Dakota, South Dakota and Texas); 5 straddle Mountain and Pacific (Idaho, Nevada and Oregon); one code, 867, spans Central, Mountain and Pacific (Northwest Territories, Yukon and Nunavut).

Notes

• 775: Mountain Time only in the West Wendover rate center (NANPA).
• 867: Iqaluit uses Eastern time, which NANPA doesn't list for 867.
• 930: NANPA's row lists Eastern only. Its overlay 812 serves the same area and is also listed with Central, so we list both.
• 986: NANPA's row lists Pacific only. Its overlay 208 serves the same area and is also listed with Mountain, so we list both.

Why it matters for calling hours

The FCC's TCPA rules say no one may make a telephone solicitation to a residential subscriber "before the hour of 8 a.m. or after 9 p.m. (local time at the called party's location)" (47 CFR 64.1200(c)(1)). The clock that counts is the one where the person you're calling is, not yours.

For most numbers, the area code is a reasonable first guess at that clock. For the 26 codes above it isn't: one area code covers places an hour or more apart, and the number alone doesn't say which side of the line the person is on. State laws can add their own limits on calling hours; this page covers only the federal rule. It is general information, not legal advice.

How to handle these codes

• Use a better location signal when you have one. A CheckThatPhone lookup returns timezone (an IANA name such as America/Chicago) and tzOffset (the UTC offset in hours). Pass the contact's IP address as ip and the location can come from the IP (geoSource: "ip"); without one it comes from the number's area code (geoSource: "area-code"). For a code on this page, an area-code time zone is one of the possibilities, not the answer.
• Otherwise, use the window that fits every zone. Treat the number as if it could be in any of the code's zones, and call only when it is between 8 a.m. and 9 p.m. in all of them. For an Eastern and Central code such as 219, that's 9 a.m. to 9 p.m. Eastern (8 a.m. to 8 p.m. Central).
• Keep the data's limits in mind. NANPA lists each code's predominant zones, so a code can have pockets in a zone NANPA doesn't list for it (parts of Labrador, parts of British Columbia, Iqaluit in 867, Alaska's western Aleutians in 907). NANPA's zones are standard time, with nothing on daylight saving: most of Arizona and most of Saskatchewan don't change their clocks.

The API docs list every location field. For the wider compliance picture, see the TCPA litigator scrub, the state DNC scrub and the other use cases, or read how GeoIP and time zone data improve SMS and call campaigns.