On 11/15/12 2:15 PM, james machado wrote:
On Thu, Nov 15, 2012 at 1:55 PM, Seth Mattinen <sethm@rollernet.us> wrote:
On 11/15/12 1:16 PM, Matthew Petach wrote:
On Thu, Nov 15, 2012 at 12:23 PM, <jrk1231-outml@nym.hush.com> wrote: ...
I should add that if I proxy my web connection through a server I have at ServerBeach, I have no issues accessing ooVoo.
Thoughts / comments on how to get this fixed?
I have found in the past that the most effective way to deal with the random traffic blackholing that ATT does was to stop buying service from them. Once I did that, those headaches vanished like the morning mists on a midsummers day.
Short of that, all I can say is that alcohol can sometimes help deaden the pain slightly.
Are we talking about residential DSL/u-verse or "business" Metro Ethernet (FastE, GigE, etc. over opt-e-man)?
blocked in SoCal from managed business service. a traceroute for www.oovoo.com gets dropped at the managed internet router. other traces work fine.
At an AT&T provided MIS router (on premise) or a hop or two past that? I'm curious to know if they're pushing a blocking ACL to MIS with managed (AT&T provided) routers or further up from that, which would mean that customers with their own router wouldn't be affected. ~Seth