Re: Myspace contact needed

2011-07-12 Thread Walter Keen
I finally made contact using the information at 
http://whois.arin.net/rest/poc/NOC11562-ARIN.html  .  We were blocked 
for spamming (but there seemed to be some confusion, as we have 
69.10.192.0/19, and they asked if we had 69.10.0.0/16.  Makes me wonder 
if they lookup the RIR allocated blocks before blocking, or assume a /16


Walter Keen
Network Engineer
Rainier Connect

(P) 360-832-4024
(C) 253-302-0194


On 07/12/2011 08:50 AM, TProphet wrote:
I use a VPN from Beijing, where I reside. It's pretty common for 
myspace to blacklist any IP addresses that they believe belong to 
crawlers, linkbots, VPN services, etc. This appears to be an automated 
process. I've never had luck getting any of my VPN IPs unblocked.


Good luck getting in touch with anyone there, the company was just 
sold to a consortium of celebrities after massive News Corp. layoffs 
and it's left with walking zombies. I'd be surprised if anyone 
competent is still left...


-TProphet

On 7/12/2011 9:49 PM, Walter Keen wrote:


Sorry about the lack of details.

I'm looking for a Myspace contact, We're an ISP (AS20394) and all of our
users are getting a 302 redirect to google after contacting a myspace
server. If there is an appropriate contact on this list, or someone who
can forward this to such a contact, it would be greatly appreciated.
I don't have this issue from other ISP connections(such as my home
connection), but have not heard back from the website support portal as
of yet.




wkeen@tnwx-nms-3:~$ traceroute www.myspace.com
traceroute to www.myspace.com (216.178.39.11), 30 hops max, 40 byte 
packets
1 tnwx-core-1.rainierconnect.com (69.10.208.1) 0.409 ms 0.479 ms 
0.559 ms

2 74.50.203.97 (74.50.203.97) 1.772 ms 1.769 ms 1.805 ms
3 ge5-0-2d0.cir1.seattle7-wa.us.xo.net (216.156.100.41) 1.703 ms 1.708
ms 1.707 ms
4 4.59.232.53 (4.59.232.53) 2.064 ms 2.067 ms 2.056 ms
5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 11.408 ms 11.374 ms
11.484 ms
6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 19.095 ms 18.870 ms
18.997 ms
7 ae-34-34.ebr4.SanJose1.Level3.net (4.69.153.34) 20.638 ms 30.373 ms
30.333 ms
8 ae-5-5.ebr2.SanJose5.Level3.net (4.69.148.141) 19.631 ms 19.813 ms
19.803 ms
9 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 29.283 ms 28.981 ms
29.246 ms
10 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 29.091 ms
ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 29.461 ms 29.437 ms
11 ae-24-70.car4.LosAngeles1.Level3.net (4.69.144.70) 29.684 ms
ae-44-90.car4.LosAngeles1.Level3.net (4.69.144.198) 29.562 ms
ae-14-60.car4.LosAngeles1.Level3.net (4.69.144.6) 29.680 ms
12 ve202.lax.myspace.com (4.71.128.10) 29.351 ms 28.998 ms 29.203 ms
13 vl342.cs2.lax1.myspace.com (204.16.35.137) 29.431 ms 29.540 ms 
29.638 ms
14 vl3552.cs2.els2.myspace.com (216.178.35.77) 29.970 ms 29.717 ms 
29.726 ms

15 * * *
16 * * *
17 * * *
18 * * *
19 * * *

wkeen@tnwx-nms-3:~$ wget www.myspace.com
--2011-07-12 06:45:32-- http://www.myspace.com/
Resolving www.myspace.com... 63.135.80.46
Connecting to www.myspace.com|63.135.80.46|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com [following]
--2011-07-12 06:45:32-- http://www.google.com/
Resolving www.google.com... 72.14.213.106, 72.14.213.147, 
72.14.213.99, ...

Connecting to www.google.com|72.14.213.106|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.5'

[ <=> ] 9,908 --.-K/s in 0.009s

2011-07-12 06:45:32 (1.01 MB/s) - `index.html.5' saved [9908]

wkeen@tnwx-nms-3:~$



 wrote:
> My apologies all, I meant to say myspace contact
>

You're more likely to get a response if you give some indication
of what the issue is; for example, saying "I'm looking for a MySpace
contact because there is an attack coming from their servers that
appears to indicate they may have been compromised" will likely
get you a faster reaction from the security people. Or, if it's a
network issue, saying "I'm looking for a MySpace network contact
because it appears they are announcing the following blocks which
really belong to me, which is causing reachability issues" will more
likely get you a reaction from an appropriate network person.

Without an indication of the nature of the problem, I think you'll find
most people on the list tend to ignore generic requests like this.

Thanks!

Matt





Re: Myspace contact needed

2011-07-12 Thread TProphet
I use a VPN from Beijing, where I reside. It's pretty common for myspace 
to blacklist any IP addresses that they believe belong to crawlers, 
linkbots, VPN services, etc. This appears to be an automated process. 
I've never had luck getting any of my VPN IPs unblocked.


Good luck getting in touch with anyone there, the company was just sold 
to a consortium of celebrities after massive News Corp. layoffs and it's 
left with walking zombies. I'd be surprised if anyone competent is still 
left...


-TProphet

On 7/12/2011 9:49 PM, Walter Keen wrote:


Sorry about the lack of details.

I'm looking for a Myspace contact, We're an ISP (AS20394) and all of our
users are getting a 302 redirect to google after contacting a myspace
server. If there is an appropriate contact on this list, or someone who
can forward this to such a contact, it would be greatly appreciated.
I don't have this issue from other ISP connections(such as my home
connection), but have not heard back from the website support portal as
of yet.




wkeen@tnwx-nms-3:~$ traceroute www.myspace.com
traceroute to www.myspace.com (216.178.39.11), 30 hops max, 40 byte packets
1 tnwx-core-1.rainierconnect.com (69.10.208.1) 0.409 ms 0.479 ms 0.559 ms
2 74.50.203.97 (74.50.203.97) 1.772 ms 1.769 ms 1.805 ms
3 ge5-0-2d0.cir1.seattle7-wa.us.xo.net (216.156.100.41) 1.703 ms 1.708
ms 1.707 ms
4 4.59.232.53 (4.59.232.53) 2.064 ms 2.067 ms 2.056 ms
5 ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150) 11.408 ms 11.374 ms
11.484 ms
6 ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49) 19.095 ms 18.870 ms
18.997 ms
7 ae-34-34.ebr4.SanJose1.Level3.net (4.69.153.34) 20.638 ms 30.373 ms
30.333 ms
8 ae-5-5.ebr2.SanJose5.Level3.net (4.69.148.141) 19.631 ms 19.813 ms
19.803 ms
9 ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201) 29.283 ms 28.981 ms
29.246 ms
10 ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18) 29.091 ms
ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22) 29.461 ms 29.437 ms
11 ae-24-70.car4.LosAngeles1.Level3.net (4.69.144.70) 29.684 ms
ae-44-90.car4.LosAngeles1.Level3.net (4.69.144.198) 29.562 ms
ae-14-60.car4.LosAngeles1.Level3.net (4.69.144.6) 29.680 ms
12 ve202.lax.myspace.com (4.71.128.10) 29.351 ms 28.998 ms 29.203 ms
13 vl342.cs2.lax1.myspace.com (204.16.35.137) 29.431 ms 29.540 ms 29.638 ms
14 vl3552.cs2.els2.myspace.com (216.178.35.77) 29.970 ms 29.717 ms 29.726 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *

wkeen@tnwx-nms-3:~$ wget www.myspace.com
--2011-07-12 06:45:32-- http://www.myspace.com/
Resolving www.myspace.com... 63.135.80.46
Connecting to www.myspace.com|63.135.80.46|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com [following]
--2011-07-12 06:45:32-- http://www.google.com/
Resolving www.google.com... 72.14.213.106, 72.14.213.147, 72.14.213.99, ...
Connecting to www.google.com|72.14.213.106|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.5'

[ <=> ] 9,908 --.-K/s in 0.009s

2011-07-12 06:45:32 (1.01 MB/s) - `index.html.5' saved [9908]

wkeen@tnwx-nms-3:~$



 wrote:
 > My apologies all, I meant to say myspace contact
 >

You're more likely to get a response if you give some indication
of what the issue is; for example, saying "I'm looking for a MySpace
contact because there is an attack coming from their servers that
appears to indicate they may have been compromised" will likely
get you a faster reaction from the security people. Or, if it's a
network issue, saying "I'm looking for a MySpace network contact
because it appears they are announcing the following blocks which
really belong to me, which is causing reachability issues" will more
likely get you a reaction from an appropriate network person.

Without an indication of the nature of the problem, I think you'll find
most people on the list tend to ignore generic requests like this.

Thanks!

Matt





Myspace contact needed

2011-07-12 Thread Walter Keen

Sorry about the lack of details.

I'm looking for a Myspace contact, We're an ISP (AS20394) and all of our users 
are getting a 302 redirect to google after contacting a myspace server.  If 
there is an appropriate contact on this list, or someone who can forward this 
to such a contact, it would be greatly appreciated.
I don't have this issue from other ISP connections(such as my home connection), 
but have not heard back from the website support portal as of yet.




wkeen@tnwx-nms-3:~$ traceroute www.myspace.com
traceroute to www.myspace.com (216.178.39.11), 30 hops max, 40 byte packets
 1  tnwx-core-1.rainierconnect.com (69.10.208.1)  0.409 ms  0.479 ms  0.559 ms
 2  74.50.203.97 (74.50.203.97)  1.772 ms  1.769 ms  1.805 ms
 3  ge5-0-2d0.cir1.seattle7-wa.us.xo.net (216.156.100.41)  1.703 ms  1.708 ms  
1.707 ms
 4  4.59.232.53 (4.59.232.53)  2.064 ms  2.067 ms  2.056 ms
 5  ae-31-51.ebr1.Seattle1.Level3.net (4.69.147.150)  11.408 ms  11.374 ms  
11.484 ms
 6  ae-7-7.ebr2.SanJose1.Level3.net (4.69.132.49)  19.095 ms  18.870 ms  18.997 
ms
 7  ae-34-34.ebr4.SanJose1.Level3.net (4.69.153.34)  20.638 ms  30.373 ms  
30.333 ms
 8  ae-5-5.ebr2.SanJose5.Level3.net (4.69.148.141)  19.631 ms  19.813 ms  
19.803 ms
 9  ae-6-6.ebr2.LosAngeles1.Level3.net (4.69.148.201)  29.283 ms  28.981 ms  
29.246 ms
10  ae-62-62.csw1.LosAngeles1.Level3.net (4.69.137.18)  29.091 ms 
ae-72-72.csw2.LosAngeles1.Level3.net (4.69.137.22)  29.461 ms  29.437 ms
11  ae-24-70.car4.LosAngeles1.Level3.net (4.69.144.70)  29.684 ms 
ae-44-90.car4.LosAngeles1.Level3.net (4.69.144.198)  29.562 ms 
ae-14-60.car4.LosAngeles1.Level3.net (4.69.144.6)  29.680 ms
12  ve202.lax.myspace.com (4.71.128.10)  29.351 ms  28.998 ms  29.203 ms
13  vl342.cs2.lax1.myspace.com (204.16.35.137)  29.431 ms  29.540 ms  29.638 ms
14  vl3552.cs2.els2.myspace.com (216.178.35.77)  29.970 ms  29.717 ms  29.726 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *

wkeen@tnwx-nms-3:~$ wget www.myspace.com
--2011-07-12 06:45:32--  http://www.myspace.com/
Resolving www.myspace.com... 63.135.80.46
Connecting to www.myspace.com|63.135.80.46|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.com [following]
--2011-07-12 06:45:32--  http://www.google.com/
Resolving www.google.com... 72.14.213.106, 72.14.213.147, 72.14.213.99, ...
Connecting to www.google.com|72.14.213.106|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.5'

[ <=>   ] 9,908   --.-K/s   in 
0.009s  

2011-07-12 06:45:32 (1.01 MB/s) - `index.html.5' saved [9908]

wkeen@tnwx-nms-3:~$ 



 wrote:
> My apologies all, I meant to say myspace contact
>

You're more likely to get a response if you give some indication
of what the issue is; for example, saying "I'm looking for a MySpace
contact because there is an attack coming from their servers that
appears to indicate they may have been compromised" will likely
get you a faster reaction from the security people.  Or, if it's a
network issue, saying "I'm looking for a MySpace network contact
because it appears they are announcing the following blocks which
really belong to me, which is causing reachability issues" will more
likely get you a reaction from an appropriate network person.

Without an indication of the nature of the problem, I think you'll find
most people on the list tend to ignore generic requests like this.

Thanks!

Matt