On Sun, Aug 21, 2011 at 6:44 AM, Denis Spirin <noc@link-telecom.net> wrote:
Where do you see the permission of Internap to transit our AS31733?
aut-num: AS31733 as-name: LINKTEL-AS descr: Link Telecom PJSC org: ORG-LTP1-RIPE import: from AS8342 accept ANY import: from AS12695 accept ANY import: from AS44109 accept ANY export: to AS8342 announce AS31733 export: to AS12695 announce AS31733 export: to AS44109 announce AS31733 admin-c: LN1688-RIPE tech-c: LN1688-RIPE mnt-by: RIPE-NCC-END-MNT mnt-by: MNT-LINKTEL mnt-routes: MNT-LINKTEL changed: noc@link-telecom.biz 20080917 changed: hostmaster@ripe.net 20110414 source: RIPE
AS8342, AS12695, AS44109 can. AS12182 - can't.
We already in touch with RIPE NCC and Internap. But networks are continue to be hijacked. That is the reason I wrote to this list.
2011/8/21 Arturo Servin <arturo.servin@gmail.com>
On 21 Aug 2011, at 00:28, Denis Spirin wrote:
Yes, they are using our ASN 31733 to originate networks. All the visible paths are through AS12182. Internap was contacted about a week ago, but did nothing.
Which seems to be the right decision because the whois data backed it on.
No, I'm not a venture capitalist, but IT specialist.
I am too sleepy, so replied to Adrian directly while wanted to post in the list.
If you are claiming right over these prefixes I suggest you to contact RIPE NCC.
/as
2011/8/21 Arturo Servin <aservin@lacnic.net>
These prefix are originated by AS31733 which seems to be assigned to the same organisation than the ASN, which in turn seems to be you.
I can see AS12182 in the path but not originating the route. So I do not understand what are your claiming.
.as
On 20 Aug 2011, at 23:05, Denis Spirin wrote:
Right now there are: 46.96.0.0/16 83.223.224.0/19 94.250.128.0/19 94.250.160.0/19 188.164.0.0/24
/me puts on Internap hat. I don't see much of the goings-on in the NOC these days, but am looking into this. --chip -- Just my $.02, your mileage may vary, batteries not included, etc....