August 2000 September 2000 Headlines October 2000

wpe18.jpg (915 bytes) requires to be viewed (Acrobat is Free)

>> Sep 6: KS: KCC Orders Geographic Split of 316
>> Sep 11: OH: 10-Digit Dialing In Line For State
>> Sep 12: MA: Verizon Gets Eastern Mass Ready For 4 New Codes & 10-D Dialing
>> Sep 13: TN: 731 To Split From 901
>> Sep 13: LA: 504 Splitting to 985 Outside New Orleans Metro Area
wpe18.jpg (915 bytes) Sep 15: ON: 289 To Overlay 905
>> Sep 15: MI: 517 Splitting To 989 - Plan Approved
>> Sep 19: NY: NeuStar Initiates Mandatory Pooling Trial In 518 Area
wpe18.jpg (915 bytes) Sep 20: NANPA PL: LA: Mandatory Dialing Of Wireless 337 Exchanges
wpe18.jpg (915 bytes) Sep 20: NY: 716 Split To Include Wireless Exchanges
>> Sep 21: TN: 731 Tagged As Split For 901 Outside Memphis Metro
>> Sep 21: KS: 620 To Split From 316 Outside Wichita Metro
>> Sep 21: CA: Backup Plan To Split 310 To 424 At Imperial Highway
>> Sep 22: KS: KCC Assigns 620 To Areas Outside Wichita Metro
>> Sep 26: FL: Consolidated Area Code Decision Due 9/29 On 4 Codes!
>> Sep 27: OH: Reminder That 10-Digit Dialing Is Coming To 330/234
>> Sep 27: OR: Information On New 971 Area Code
wpe18.jpg (915 bytes) Sep 28: TN: State Approves Number Conservation Plan
>> Sep 28: OH: 513 To Get Overlay; Franklin Exchange To Realign To 937
>> Sep 29: OH: Ten Digit Numbers Become Norm
>> Sep 29: FL: 561 To Split; New Code TBA
>> Sep 29: FL: 786 Overlay Of 305 Extended To Keys; 10-D To Follow
>> Sep 29: FL: 954 To Receive Overlay; New Code TBA
>> Sep 29: FL: 904 Discontiguous Split; 386 Recommended As New Code
>> Sep 30: FL: Ten Counties Must Adopt 386 Area Code

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.