[NBLUG/talk] What other high speed internet options are there?

[Ed Rogers]

I have surewest and am pleased with it.
50 mbps symmetrical and connects directly to the router; no modem.


Quoting "Jordan Erickson" <jerickson at logicalnetworking.net>:

> There's got to be a Sonoma County "SURF LOCAL" sticker somewhere around
> here... ;)
>
>
>
> On 09/29/2011 08:34 AM, T wrote:
>> I also have AT&T, the uverse package. It was great until about 3-4
>> months ago. It goes through sporadic down times, especially during the
>> evenings and I will start getting packet floods equivalent to DDoS
>> attacks. In excess of 1-200k bad packets/5min, incoming. Mabey more,
>> been a while since i check the syslog, and it just cripples my
>> Internet making it unsuable.
>>
>> Comcast is also another option for you. The company I work for uses
>> it's business class services. It seems to be a bit more stable than
>> AT&T; however, it will also go through it's sporadic slow periods.
>>
>> ~ Travis
>>
>> On Sep 28, 2011, at 7:10 PM, Troy Arnold <troy at zenux.net> wrote:
>>
>>> On Wed, Sep 28, 2011 at 06:15:16PM -0700, Mr. Jan Hearthstone wrote:
>>>> Hi!
>>>>
>>>> What high speed internet (other than AT&T and satellite) options are
>>>> there?
>>>>
>>>> AT&T switched to fiber optics and I have more trouble with
>>>> connecting now than before they done this.
>>>
>>> I second Lincoln's recommendation for Sonic.net.  Their technical
>>> support
>>> is as good as it gets and if there is a problem with your line, Sonic
>>> will
>>> go to bat for you.  I'm having a hard time picturing how AT&T's
>>> switch to
>>> fiber would make a negative difference for you unless they screwed up
>>> the
>>> wiring in the process.
>>>
>>> I'm wondering also if perhaps you're seeing a DNS resolution problem?
>>> Large ISPs are notorious for having slow, unreliable resolvers (though I
>>> don't know about At&t's reputation).  The next time you're having
>>> trouble
>>> connecting, try pinging the IP address for www.sonic.net:
>>>
>>> $ ping 209.204.190.64
>>> PING 209.204.190.64 (209.204.190.64) 56(84) bytes of data.
>>> 64 bytes from 209.204.190.64: icmp_seq=1 ttl=247 time=7.91 ms
>>> 64 bytes from 209.204.190.64: icmp_seq=2 ttl=247 time=8.37 ms
>>> 64 bytes from 209.204.190.64: icmp_seq=3 ttl=247 time=7.82 ms
>>>
>>> --- 209.204.190.64 ping statistics ---
>>> 3 packets transmitted, 3 received, 0% packet loss, time 2004ms
>>> rtt min/avg/max/mdev = 7.821/8.035/8.375/0.263 ms
>>>
>>>
>>> If it works, but you can't connect to http://www.sonic.net/ then it's
>>> most likely DNS.  Reply back and we can help you switch over to better
>>> nameservers.
>>>
>>> Good luck!
>>>
>>> -troy
>>>
>>> _______________________________________________
>>> talk mailing list
>>> talk at nblug.org
>>> http://nblug.org/cgi-bin/mailman/listinfo/talk
>>
>> _______________________________________________
>> talk mailing list
>> talk at nblug.org
>> http://nblug.org/cgi-bin/mailman/listinfo/talk
>
>
> --
> Jordan Erickson (PGP: 0xDA470FF8)
> LNS: (707) 636-5678  - http://logicalnetworking.net
>
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/cgi-bin/mailman/listinfo/talk
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.