AT&T Apparently Blocking ooVoo -- WAS: Re: ooVoo WebSite Outage?
Okay, I hate to reply to my own posting, but... There are apparently multiple complaints about AT&T blocking ooVoo. I opened a case and have received responses that indicate others on AT&T networks are having issues where ooVoo is unreachable and it appears to be blocked by AT&T. The www.oovoo.com address still falls off the face of the Earth as indicated below, but the other ooVoo IPs will trace to the destination IP, but it appears that 80 and 443 are being filtered by AT&T. ("secure" was passing HTTPS traffic the other day, but hasn't for the past 2 days.) Nmap scan report for secure.oovoo.com (63.111.29.147) Host is up (0.056s latency). Not shown: 996 filtered ports PORT STATE SERVICE 21/tcp open ftp 113/tcp closed auth 554/tcp open rtsp 7070/tcp open realserver 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? TIA! Jon Kibler -- Jon R. Kibler +001-843-813-2924 On 11/12/2012 at 4:26 AM, jrk1231-outml@nym.hush.com wrote:Hum... now the traceroute for www.oovoo.com fails, but secure.oovoo.com -- same netblock -- works. traceroute to www.oovoo.com (63.111.29.132), 64 hops max, 52 byte packets 1 2 3 4 72.157.38.25 (72.157.38.25) 29.267 ms 33.898 ms 30.331 ms 5 12.81.68.48 (12.81.68.48) 33.433 ms 29.274 ms 29.826 ms 6 12.81.68.24 (12.81.68.24) 30.588 ms 28.439 ms 29.987 ms 7 12.81.104.215 (12.81.104.215) 30.120 ms 28.449 ms 29.889 ms 8 12.81.98.2 (12.81.98.2) 30.571 ms 29.612 ms 30.823 ms 9 12.81.104.217 (12.81.104.217) 30.217 ms 27.658 ms 30.235 ms 10 12.81.100.58 (12.81.100.58) 30.597 ms 30.295 ms 28.487 ms 11 12.81.56.52 (12.81.56.52) 34.060 ms 29.545 ms 32.002 ms 12 12.81.56.65 (12.81.56.65) 27.708 ms 28.939 ms 30.072 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * traceroute to secure.oovoo.com (63.111.29.147), 64 hops max, 52 byte packets 1 2 3 4 72.157.38.25 (72.157.38.25) 30.038 ms 29.951 ms 29.441 ms 5 12.81.68.48 (12.81.68.48) 30.508 ms 29.833 ms 29.451 ms 6 12.81.68.56 (12.81.68.56) 30.831 ms 30.399 ms 29.220 ms 7 12.81.104.107 (12.81.104.107) 38.712 ms 27.908 ms 31.213 ms 8 12.81.98.26 (12.81.98.26) 29.921 ms 29.054 ms 33.225 ms 9 12.81.104.99 (12.81.104.99) 26.889 ms 31.831 ms 29.541 ms 10 12.81.100.0 (12.81.100.0) 37.266 ms 28.673 ms 30.798 ms 11 12.81.104.210 (12.81.104.210) 30.944 ms 30.888 ms 31.435 ms 12 12.81.56.63 (12.81.56.63) 26.724 ms 28.490 ms 29.224 ms 13 74.175.192.58 (74.175.192.58) 30.658 ms 28.843 ms 29.918 ms 14 cr2.rlgnc.ip.att.net (12.123.152.110) 43.235 ms 39.251 ms 39.338 ms 15 cr1.wswdc.ip.att.net (12.122.3.170) 43.000 ms 43.378 ms 40.628 ms 16 gar13.n54ny.ip.att.net (12.122.81.245) 71.120 ms 74.416 ms 65.208 ms 17 192.205.36.142 (192.205.36.142) 37.763 ms 61.242 ms 37.282 ms 18 0.so-6-1-0.xt2.atl5.alter.net (152.63.82.5) 48.017 ms 45.382 ms 46.031 ms 19 pos5-0.ur2.atl7.web.wcom.net (157.130.80.18) 45.436 ms 44.624 ms 45.610 ms 20 198.5.128.142 (198.5.128.142) 46.025 ms 48.440 ms 44.161 ms 21 199.170.227.134 (199.170.227.134) 46.546 ms 45.945 ms 45.566 ms 22 63.111.5.249 (63.111.5.249) 46.002 ms 47.047 ms 46.471 ms 23 secure.oovoo.com (63.111.29.147) 60.406 ms 64.308 ms 66.307 ms -- Jon R. Kibler +001-843-813-2924 On 11/11/2012 at 10:34 PM, "Josh Luthman" wrote: Redirects to the Android mobile page on my phone. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Nov 11, 2012 10:20 PM, "Mitch" wrote: Loaded up for me, seemed a bit slow, but loaded up. (I'm in ohio) On Sun, Nov 11, 2012 at 8:44 PM, wrote: No problem accessing www.oovoo.com through the Internet... traceroute is find. But, www.oovoo.com times out. Anyone else seeing this? Any idea what's up? THANKS! Jon Kibler -- Jon R. Kibler +001-843-813-2924 -- Jon R. Kibler +001-843-813-2924 _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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. Best of luck!! Matt
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)? ~Seth
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. james
~Seth _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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
On 11/15/12 2:22 PM, Seth Mattinen wrote:
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.
In our case it dies at the AT&T directly-connected BGP peer. We manage the router on our side. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
Same here... -Mike On Thu, Nov 15, 2012 at 2:28 PM, Jay Hennigan <jay@west.net> wrote:
On 11/15/12 2:22 PM, Seth Mattinen wrote:
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.
In our case it dies at the AT&T directly-connected BGP peer. We manage the router on our side.
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Mike Lyon 408-621-4826 mike.lyon@gmail.com http://www.linkedin.com/in/mlyon
Why on earth would they block it? Sent from my iPhone On Nov 15, 2012, at 15:05, Seth Mattinen <sethm@rollernet.us> wrote:
On 11/15/12 2:35 PM, Mike Lyon wrote:
Same here...
That's certainly disturbing. Have you broached the topic with you account manager or opened a trouble ticket?
~Seth _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On 11/15/12 3:06 PM, Mike Lyon wrote:
Why on earth would they block it?
One possibility is that ooVoo peers with AT&T, was being DoSed, and triggered RTBH but that doesn't seem likely as traces to adjacent IPs don't show a direct connection. Alternatively, this may have something to do with it, but it seems like an awfully big hammer, and applied in the wrong place.... http://www.informationweek.com/services/data/att-no-iphone-facetime-without-... -- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
The phrase "Never attribute to malice that which is adequately explained by stupidity" might be good to remember when dealing with ATT. Not saying that they never having any of the former, but organizationally they seem to have a lot of the latter. (Not a slam at everyone at ATT, I know plenty of good people there; their organization structure can be frustrating to no end to deal with though). Oliver On Thu, Nov 15, 2012 at 6:26 PM, Jay Hennigan <jay@west.net> wrote:
On 11/15/12 3:06 PM, Mike Lyon wrote:
Why on earth would they block it?
One possibility is that ooVoo peers with AT&T, was being DoSed, and triggered RTBH but that doesn't seem likely as traces to adjacent IPs don't show a direct connection.
Alternatively, this may have something to do with it, but it seems like an awfully big hammer, and applied in the wrong place....
http://www.informationweek.com/services/data/att-no-iphone-facetime-without-...
-- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On 11/15/12 3:26 PM, Jay Hennigan wrote:
On 11/15/12 3:06 PM, Mike Lyon wrote:
Why on earth would they block it?
One possibility is that ooVoo peers with AT&T, was being DoSed, and triggered RTBH but that doesn't seem likely as traces to adjacent IPs don't show a direct connection.
Alternatively, this may have something to do with it, but it seems like an awfully big hammer, and applied in the wrong place....
http://www.informationweek.com/services/data/att-no-iphone-facetime-without-...
AT&T doesn't support RTBH, either. ~Seth
Once upon a time, Seth Mattinen <sethm@rollernet.us> said:
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.
It appears to be dropped in their entire network. I tried it from route-server.ip.att.net (telnet); I can trace to 63.111.29.131 and 63.111.29.133 (at least into AS 11486), but trace to 63.111.29.132 dies after 1 hop. -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
I do not have AT&T as an ISP. However, my ISP does have them as one of their upstream providers. It appears BGP is trying to route packets destined for 63.111.29.0/24 via the AT&T upstream and I can see it failing as soon as it hits AT&T's network. Jim On Nov 15, 2012, at 5:41 PM, Chris Adams wrote:
Once upon a time, Seth Mattinen <sethm@rollernet.us> said:
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.
It appears to be dropped in their entire network. I tried it from route-server.ip.att.net (telnet); I can trace to 63.111.29.131 and 63.111.29.133 (at least into AS 11486), but trace to 63.111.29.132 dies after 1 hop. -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Let's move this to outages-discussion. Jim: I would suggest having your ISP send traffic for 63.111.29.0/24 to one of their other upstream providers, to route around the issue, and then open a ticket with AT&T. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Network Operations Sent: Thursday, November 15, 2012 5:15 PM To: outages Subject: Re: [outages] AT&T Apparently Blocking ooVoo -- WAS: Re: ooVoo WebSite Outage? I do not have AT&T as an ISP. However, my ISP does have them as one of their upstream providers. It appears BGP is trying to route packets destined for 63.111.29.0/24 via the AT&T upstream and I can see it failing as soon as it hits AT&T's network. Jim On Nov 15, 2012, at 5:41 PM, Chris Adams wrote:
Once upon a time, Seth Mattinen <sethm@rollernet.us> said:
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.
It appears to be dropped in their entire network. I tried it from route-server.ip.att.net (telnet); I can trace to 63.111.29.131 and 63.111.29.133 (at least into AS 11486), but trace to 63.111.29.132 dies after 1 hop. -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On Thu, Nov 15, 2012 at 2:22 PM, Seth Mattinen <sethm@rollernet.us> wrote:
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?
on premise AT&T provided and managed MIS router.
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 _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Yes they block it, can't get to it from a mpls connection or their uverse service. ----- Original Message ----- From: jrk1231-outml@nym.hush.com To: outages@outages.org Sent: Thu, 15 Nov 2012 15:23:49 -0500 (EST) Subject: [outages] AT&T Apparently Blocking ooVoo -- WAS: Re: ooVoo WebSite Outage? Okay, I hate to reply to my own posting, but... There are apparently multiple complaints about AT&T blocking ooVoo. I opened a case and have received responses that indicate others on AT&T networks are having issues where ooVoo is unreachable and it appears to be blocked by AT&T. The www.oovoo.com address still falls off the face of the Earth as indicated below, but the other ooVoo IPs will trace to the destination IP, but it appears that 80 and 443 are being filtered by AT&T. ("secure" was passing HTTPS traffic the other day, but hasn't for the past 2 days.) Nmap scan report for secure.oovoo.com (63.111.29.147) Host is up (0.056s latency). Not shown: 996 filtered ports PORT STATE SERVICE 21/tcp open ftp 113/tcp closed auth 554/tcp open rtsp 7070/tcp open realserver 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? TIA! Jon Kibler -- Jon R. Kibler +001-843-813-2924 On 11/12/2012 at 4:26 AM, jrk1231-outml@nym.hush.com wrote:Hum... now the traceroute for www.oovoo.com fails, but secure.oovoo.com -- same netblock -- works. traceroute to www.oovoo.com (63.111.29.132), 64 hops max, 52 byte packets 1 2 3 4 72.157.38.25 (72.157.38.25) 29.267 ms 33.898 ms 30.331 ms 5 12.81.68.48 (12.81.68.48) 33.433 ms 29.274 ms 29.826 ms 6 12.81.68.24 (12.81.68.24) 30.588 ms 28.439 ms 29.987 ms 7 12.81.104.215 (12.81.104.215) 30.120 ms 28.449 ms 29.889 ms 8 12.81.98.2 (12.81.98.2) 30.571 ms 29.612 ms 30.823 ms 9 12.81.104.217 (12.81.104.217) 30.217 ms 27.658 ms 30.235 ms 10 12.81.100.58 (12.81.100.58) 30.597 ms 30.295 ms 28.487 ms 11 12.81.56.52 (12.81.56.52) 34.060 ms 29.545 ms 32.002 ms 12 12.81.56.65 (12.81.56.65) 27.708 ms 28.939 ms 30.072 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * traceroute to secure.oovoo.com (63.111.29.147), 64 hops max, 52 byte packets 1 2 3 4 72.157.38.25 (72.157.38.25) 30.038 ms 29.951 ms 29.441 ms 5 12.81.68.48 (12.81.68.48) 30.508 ms 29.833 ms 29.451 ms 6 12.81.68.56 (12.81.68.56) 30.831 ms 30.399 ms 29.220 ms 7 12.81.104.107 (12.81.104.107) 38.712 ms 27.908 ms 31.213 ms 8 12.81.98.26 (12.81.98.26) 29.921 ms 29.054 ms 33.225 ms 9 12.81.104.99 (12.81.104.99) 26.889 ms 31.831 ms 29.541 ms 10 12.81.100.0 (12.81.100.0) 37.266 ms 28.673 ms 30.798 ms 11 12.81.104.210 (12.81.104.210) 30.944 ms 30.888 ms 31.435 ms 12 12.81.56.63 (12.81.56.63) 26.724 ms 28.490 ms 29.224 ms 13 74.175.192.58 (74.175.192.58) 30.658 ms 28.843 ms 29.918 ms 14 cr2.rlgnc.ip.att.net (12.123.152.110) 43.235 ms 39.251 ms 39.338 ms 15 cr1.wswdc.ip.att.net (12.122.3.170) 43.000 ms 43.378 ms 40.628 ms 16 gar13.n54ny.ip.att.net (12.122.81.245) 71.120 ms 74.416 ms 65.208 ms 17 192.205.36.142 (192.205.36.142) 37.763 ms 61.242 ms 37.282 ms 18 0.so-6-1-0.xt2.atl5.alter.net (152.63.82.5) 48.017 ms 45.382 ms 46.031 ms 19 pos5-0.ur2.atl7.web.wcom.net (157.130.80.18) 45.436 ms 44.624 ms 45.610 ms 20 198.5.128.142 (198.5.128.142) 46.025 ms 48.440 ms 44.161 ms 21 199.170.227.134 (199.170.227.134) 46.546 ms 45.945 ms 45.566 ms 22 63.111.5.249 (63.111.5.249) 46.002 ms 47.047 ms 46.471 ms 23 secure.oovoo.com (63.111.29.147) 60.406 ms 64.308 ms 66.307 ms -- Jon R. Kibler +001-843-813-2924 On 11/11/2012 at 10:34 PM, "Josh Luthman" wrote: Redirects to the Android mobile page on my phone. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Nov 11, 2012 10:20 PM, "Mitch" wrote: Loaded up for me, seemed a bit slow, but loaded up. (I'm in ohio) On Sun, Nov 11, 2012 at 8:44 PM, wrote: No problem accessing www.oovoo.com through the Internet... traceroute is find. But, www.oovoo.com times out. Anyone else seeing this? Any idea what's up? THANKS! Jon Kibler -- Jon R. Kibler +001-843-813-2924 -- Jon R. Kibler +001-843-813-2924 _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Elijah Savage wrote:
Yes they block it, can't get to it from a mpls connection or their uverse service.
How soon we forget... http://arstechnica.com/uncategorized/2005/10/5498-2/
participants (12)
-
Chris Adams -
Elijah Savage -
Frank Bulk -
james machado -
Jay Hennigan -
jrk1231-outml＠nym.hush.com -
Matthew Petach -
Michael Painter -
Mike Lyon -
Network Operations -
Oliver Garraux -
Seth Mattinen