September 2000 October 2000 Headlines November 2000

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

>> Oct 3: AL: Mobile & Southwest To Split From 334; Possible Code 251? 
>> Oct 3: TX: 682 Overlay Begins October 7th
>> Oct 4: IL: CUB Wants Conservation Statewide, Avoiding New Codes In 815, 618, 217 & 309
wpe18.jpg (915 bytes) Oct 6: AL: 251 Selected To Split From 334 In Southwest
>> Oct 10: KS: 620 Relief Schedule Extended
>> Oct 11: CA: NeuStar Begins Number Pooling In 714
>> Oct 11: CT: NeuStar Begins Number Pooling In 860
>> Oct 11: CO: NeuStar Selected As Number Pooling Administrator In 303/720
>> Oct 13: PA: Number Pooling To Begin In March, 2001; Philly Or Pitt TBD
>> Oct 19: FL: Residents Vote By Ballot If They Will Switch Area Codes
wpe18.jpg (915 bytes) Oct 20: NANPA PL: LA: 985 To Split From 504
>> Oct 24: AZ: Public Opinion Sought On 520 Relief
>> Oct 24: MI: Ameritech Requests Delay Of 989 Implementation
wpe18.jpg (915 bytes) Oct 24: MO: Overlay Method Selected For 816 & 314 Relief
wpe18.jpg (915 bytes) Oct 25: NANPA PL: ON: 289 To Overlay 905
wpe18.jpg (915 bytes) Oct 26: NANPA PL: MI: 989 To Split From 517
wpe18.jpg (915 bytes) Oct 26: NANPA PL: KS: 620 To Split From 316
>> Oct 26: AZ: 520 Split In The Works
>> Oct 26: VA: Preliminary 540 Relief Plan Splits Area 3 Ways
>> Oct 27: IA: Utility Board Announces 319 Split
wpe18.jpg (915 bytes) Oct 27: NANPA PL: BC: 778 Will Partially Overlay 604
>> Oct 28: MISC: Canada Wonders If We Will Run Out Of Area Codes
wpe18.jpg (915 bytes) Oct 30: NANPA PL: TN: 901 Splitting To 731
>> Oct 31: FL: Ten Counties Must Adopt 386 Area Code
                           (Originally Published Sept. 30, 2000)

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.