This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Ecatel Network (Quasi Networks)
- Previous message (by thread): [anti-abuse-wg] Ecatel Network (Quasi Networks)
- Next message (by thread): [anti-abuse-wg] Ecatel Network (Quasi Networks)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Fri Jul 21 12:07:16 CEST 2017
What, you haven’t heard the “we are not the internet police” refrain yet, eh? :) From: anti-abuse-wg <anti-abuse-wg-bounces at ripe.net> on behalf of Sergey <gforgx at fotontel.ru> Date: Friday, 21 July 2017 at 3:28 PM To: "anti-abuse-wg at ripe.net" <anti-abuse-wg at ripe.net> Subject: Re: [anti-abuse-wg] Ecatel Network (Quasi Networks) I think this can only be resolved by RIPE NCC because both of its upstreams (AS3216 and AS12714) are huge Russian transit ISPs which would most likely be reluctant or maybe even resistant to abuse reports. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20170721/316b1252/attachment.html>
- Previous message (by thread): [anti-abuse-wg] Ecatel Network (Quasi Networks)
- Next message (by thread): [anti-abuse-wg] Ecatel Network (Quasi Networks)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]