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/[email protected]/

[db-wg] Reporting un-assigned but used ip-space

• Previous message (by thread): [db-wg] Reporting un-assigned but used ip-space
• Next message (by thread): [db-wg] RIPE DB updates service disruption

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Job Snijders job at ntt.net
Thu Jan 29 09:30:25 CET 2015

Dear Arnd,

On Wed, Jan 28, 2015 at 05:05:15PM +0800, Arnd Vehling wrote:
> today i recognized a spambot attack from "62.122.74.100" which lies in
> an un-assigned ip-range. How to correctly report this?

I'd report this to the upstream of this rogue BGP announcement and the
originator itself. https://stat.ripe.net/62.122.74.0%2F23#tabId=routing

example path: 62.122.74.0/23 BGP.as_path: 50156 35701 49964 1299 6453 46786 5577

46786 noc at iptransit.com
5577 abuse at as5577.net

The existance of this route means that both AS46786 and AS6453 are not
filtering their customers properly :-(

Kind regards,

Job

• Previous message (by thread): [db-wg] Reporting un-assigned but used ip-space
• Next message (by thread): [db-wg] RIPE DB updates service disruption

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]