July 1999 Headlines

requires to be viewed (Acrobat is Free)

July 1: CA: One Or Two Codes Required To Relieve 530
July 1: NY: Manhattan Confronts New 646 Area Code
July 1: NY: Manhattan's Coveted 212 Area Code Nearly Exhausted
July 1: TX: 469 Begins Use In Dallas
July 1: CA: Overlay Selected As Relief Method For 818
July 1: IL: New Area Codes Halted
July 7: NE: Relief Planning Begins In 402
July 8: CA: CPUC Approves 760 Split
July 10: CA: Bill Would Force Split In 310
July 10: CA: Panel Debates Planned 818 Overlay
July 11: CA: PUC Could Learn From Maryland's Experience
July 11: CO: Denver City Hall To Change To 720
July 11: CA: Hold, Please
July 15: CA: Panel OKs Limits On New Area Codes
July 15: CA: Senate Vote A Victory Over Area Code Chaos
July 15: MN: Phone Snafu Angers Local Business Owners
July 16: CA: Hearing On Overlay May Be Postponed
July 16: MI: 586 Selected As Overlay For 810
July 17: MI: 810 Soon To Share Space With 586
July 21: CA: Corporate Convenience Underlies Overlays?
July 21: CA: Meeting Set On New 818 Area Code Overlay Plan
July 21: NANPA PL: FL: 941 Area Code Will Split To 863
July 21: NANPA PL: OR: 971 To Partially Overlay 503
July 21: IL: Firms Told To Release 847 Data -- Or Else
July 21: NANPA PL: TN: 865 Will Split From 423
July 22: NANPA PL: NY: Long Island's 516 Will Split To 631
July 23: NANPA PL: NY: 347 To Overlay 718 In New York City
July 24: MN: 952 & 763 Assigned To Relieve 612 In Minneapolis
July 24: MN: 952 & 763 Added To Twin Cities
July 26: CA: 442 Selected For 760 Split
July 27: NANPA PL: TX: Extraordianry Jeopardy Declared in 817
July 28: NANPA PL: LA: Urgent Reminder To Convert 225/504 Wireless Numbers

NOTICE TO ALL PARTIES: This is a FREE ACCESS site. No profit is derived from this contents or articles displayed herein. Selected materials contained herein may be copyrighted by their respective owners and are presented herein for research and/or reporting purposes only pursuant to Article 17, Section 107 of the United States code dealing with copyright law. Anyone with questions concerning content should direct them to the site administrator. Likewise, we do not warrant the accuracy, reliability, or timeliness of any information in this public access system, and shall not be liable for any losses caused by such reliance on the accuracy, reliability, or timeliness of such information. Portions of such information may be incorrect or not current. Any person who relies on any information obtained from this system does so at his or her own risk.