republican-creole
Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » The Site » Old Forums » AT&T Broadband » attbi tiered pricing.
Search Topic:
Uniqs:
187
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Discount on Cable TV? »
« AT&T Digital Cable TV volume issue  
AuthorAll Replies


matt380
Dangit, Bobby.
Premium
join:2002-06-12
Kennesaw, GA
clubs:
attbi tiered pricing.

a few months ago, i read quite a bit about att introducing tiered pricing for higher speeds. now though, i can't seem to find any word about it. anybody know what's going on? thanks..


Holyearth
I Like This Forum

join:2002-07-18
Atlanta, GA
It's not here in GA...


matt380
Dangit, Bobby.
Premium
join:2002-06-12
Kennesaw, GA
clubs:
reply to matt380
any ideas as to when it may happen or even the rate of expansion out of the pacific northwest?


Count Hogula$
Notorious Dog
Premium
join:2002-06-19
Corona, CA

reply to matt380
A few months (well a lot a few months ago) they introduced Ultralink...the 3Mb service. It consists of a doubling of your subscription fee and a new config file for your modem lifting the cap to 3000/384. I have it and I like it.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson

lostdude

join:2002-10-11
Bellevue, WA
reply to matt380
Going through the www.attbroadband.com will not give you the latest information. Call them up to see if Ultralink is available. I heard the extra bandwidth will also reduce your ping somewhat but dont' count on it.

degauss1

join:2001-07-02
Hillsboro, OR
·ViaTalk
·Verizon FIOS
·Comcast
·Axvoice

Ultralink is available throughout the Pacific NW. It is twice the cash and here's my numbers...

2002-11-01 14:21:28 EST: 3156 / 355
Your download speed : 3156203 bps, or 3156 kbps.
A 385.2 KB/sec transfer rate.
Your upload speed : 355155 bps, or 355 kbps.
Seems like broadband .. above the 1mbit barrier!

Pinging www.google.com [216.239.39.100] with 32 bytes of data:

Reply from 216.239.39.100: bytes=32 time=110ms TTL=47
Reply from 216.239.39.100: bytes=32 time=77ms TTL=47
Reply from 216.239.39.100: bytes=32 time=77ms TTL=47
Reply from 216.239.39.100: bytes=32 time=78ms TTL=47
Reply from 216.239.39.100: bytes=32 time=112ms TTL=47
Reply from 216.239.39.100: bytes=32 time=78ms TTL=47
Reply from 216.239.39.100: bytes=32 time=80ms TTL=47
Reply from 216.239.39.100: bytes=32 time=79ms TTL=47
Reply from 216.239.39.100: bytes=32 time=91ms TTL=47
Reply from 216.239.39.100: bytes=32 time=76ms TTL=47
Reply from 216.239.39.100: bytes=32 time=119ms TTL=47
Reply from 216.239.39.100: bytes=32 time=80ms TTL=47
Reply from 216.239.39.100: bytes=32 time=90ms TTL=47
Reply from 216.239.39.100: bytes=32 time=125ms TTL=47
Reply from 216.239.39.100: bytes=32 time=109ms TTL=47
Reply from 216.239.39.100: bytes=32 time=79ms TTL=47
Reply from 216.239.39.100: bytes=32 time=77ms TTL=47
Reply from 216.239.39.100: bytes=32 time=134ms TTL=47
Reply from 216.239.39.100: bytes=32 time=104ms TTL=47
Reply from 216.239.39.100: bytes=32 time=94ms TTL=47
Reply from 216.239.39.100: bytes=32 time=135ms TTL=47
Reply from 216.239.39.100: bytes=32 time=78ms TTL=47
Reply from 216.239.39.100: bytes=32 time=78ms TTL=47
Reply from 216.239.39.100: bytes=32 time=78ms TTL=47
Reply from 216.239.39.100: bytes=32 time=79ms TTL=47
Reply from 216.239.39.100: bytes=32 time=80ms TTL=47
Reply from 216.239.39.100: bytes=32 time=76ms TTL=47

Ping statistics for 216.239.39.100:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 135ms, Average = 91ms

Pinging www.yahoo.akadns.net [64.58.76.177] with 32 bytes of data:

Reply from 64.58.76.177: bytes=32 time=78ms TTL=239
Reply from 64.58.76.177: bytes=32 time=79ms TTL=239
Reply from 64.58.76.177: bytes=32 time=80ms TTL=239
Reply from 64.58.76.177: bytes=32 time=126ms TTL=239
Reply from 64.58.76.177: bytes=32 time=100ms TTL=239
Reply from 64.58.76.177: bytes=32 time=94ms TTL=239
Reply from 64.58.76.177: bytes=32 time=82ms TTL=239
Reply from 64.58.76.177: bytes=32 time=81ms TTL=239
Reply from 64.58.76.177: bytes=32 time=82ms TTL=239
Reply from 64.58.76.177: bytes=32 time=77ms TTL=239
Reply from 64.58.76.177: bytes=32 time=81ms TTL=239
Reply from 64.58.76.177: bytes=32 time=77ms TTL=239
Reply from 64.58.76.177: bytes=32 time=77ms TTL=239
Reply from 64.58.76.177: bytes=32 time=80ms TTL=239
Reply from 64.58.76.177: bytes=32 time=97ms TTL=239
Reply from 64.58.76.177: bytes=32 time=79ms TTL=239
Reply from 64.58.76.177: bytes=32 time=78ms TTL=239
Reply from 64.58.76.177: bytes=32 time=79ms TTL=239
Reply from 64.58.76.177: bytes=32 time=78ms TTL=239
Reply from 64.58.76.177: bytes=32 time=106ms TTL=239
Reply from 64.58.76.177: bytes=32 time=89ms TTL=239
Reply from 64.58.76.177: bytes=32 time=79ms TTL=239
Reply from 64.58.76.177: bytes=32 time=75ms TTL=239
Reply from 64.58.76.177: bytes=32 time=76ms TTL=239
Reply from 64.58.76.177: bytes=32 time=76ms TTL=239
Reply from 64.58.76.177: bytes=32 time=78ms TTL=239
Reply from 64.58.76.177: bytes=32 time=79ms TTL=239
Reply from 64.58.76.177: bytes=32 time=95ms TTL=239

Ping statistics for 64.58.76.177:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 126ms, Average = 84ms

Decent pings but could be better....


Count Hogula$
Notorious Dog
Premium
join:2002-06-19
Corona, CA


reply to lostdude
I did my inquiry and upgrade through an ATTBi support chat session took less than 5 minutes. The only thing painful was the price. Personally I would only recommend Ultralink if you can currently get advertised speeds all the time otherwise there's no point. My pings are in the teens...but they were with the 1.5Mb service too. I don't think it the speed does much of anything for the pings.
--
The democracy will cease to exist when you take away from those who are willing to work and give to those who would not. -Thomas Jefferson

[text was edited by author 2002-11-01 14:28:06]


Drag0nzeyez
Premium
join:2002-10-04
Grand Rapids, MI

 reply to matt380
the higher tier is not going to improve your ping speeds, the small size of the ping will go just as fast through a 1.5 meg pipe as it will through a 3.0 meg pipe. the difference will be with large downloads as you can download more at a time. also, the average website is limited to 300k or lower upload speed so you cant download any faster than that.
--
DISCLAIMER: Any comments made by myself are representative of my personal view points and not those of my employer, AT&T Broadband, or my job functions relating to Cable TV(VIDEO), Internet(HSD), or Local Phone (TELEPHONY).
Forums » The Site » Old Forums » AT&T BroadbandDiscount on Cable TV? »
« AT&T Digital Cable TV volume issue  


Friday, 27-Nov 16:03:30 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.
page compression OFF
Most commented news this week
· [119] Time Warner Cable Fires Broadside At Broadcasters
· [109] New AT&T Ad Campaign Hits Back At Verizon
· [95] Apple Joins AT&T Verizon Snark Fest
· [87] New Bill Takes Aim At Higher Verizon ETFs
· [70] TiVo Sees Record Customer Losses
· [68] In-Flight Internet Headed For Bumpy Landing?
· [60] Thanksgiving Open Thread
· [49] Verizon CEO: Hulu Will Be Dead Soon
· [38] EFF Wages War On Fine Print
· [38] ICANN Slams DNS Redirection
Most people now reading
· 3.x Feral Druid - Bear Tanking Guide [World of Warcraft]
· Windows 7 boot manager editing questions [Microsoft Help]
· Newegg Black Friday Sale started [Users Find Hot Deals]
· Bell Response to PIPEDA Request [TekSavvy]
· SSD [Computer Hardware Discussion/Reviews]
· Not strictly "Home" related - but WOW anyways... [Home Repair & Improvement]
· Connecting to Google Voice Via SIP [VOIP Tech Chat]
· HOW-TO: QoS and Tomato (fixes "choppy voice") [MagicJack]
· [Newsgroups] Newzleech down? [Filesharing Software]