Re: DOS for hire issues

Hai! Many hosting providers and esp's experience that same issue. After many discussions at maawg (www.maawg.org) a community efford was founded and supported by a few very big esp's helping to optimize their signup proces and implementing customer vetting. Much can be done on that end to

Re: ChangeIP.com has been down for 20+ hours

See their twitter: https://twitter.com/changeipcom ChangeIP.com ‏@ChangeIPcom Dec 13 DNS Service functions restored, website, dynamic dns, and control panel functions remain offline as we continue DB restore process. On Mon, Dec 12, 2016 at 11:35 AM, Brian J. Dent wrote:

DOS for hire issues

Hello, One of the hosting brands we recently acquired is overrun with DOS for hire providers and individuals. We kill them as they alert however I'm curious if there's a discussion group or location, contacts, etc we might be able to coordinate in about the actors behind these accounts (assuming

Re: Cogent NOC

If the loss is seen towards a terminating webserver maybe spool curl response times over the course of a day and correlated that to observed loss via a smokeping service. Support may be more responsive with some hard statistics. Regards, Andrew Paolucci Sent with

ChangeIP.com has been down for 20+ hours

Re: Cogent NOC

On 12/14/2016 3:42 pm, Bryan Holloway wrote: Odd, though, that they didn't respond for three days. I've typically had good luck with that, although admittedly it's been months since I've opened an e-mail ticket with their NOC. Spam-filter? No, I got a confirmation and ticket ID immediately.

Re: Cogent NOC

Odd, though, that they didn't respond for three days. I've typically had good luck with that, although admittedly it's been months since I've opened an e-mail ticket with their NOC. Spam-filter? On 12/14/16 2:18 PM, Mike Hammett wrote: I think people are just going to see a traceroute

Re: Cogent NOC

I think people are just going to see a traceroute determining packet loss and not going to read the rest of what happened. Just going to shortcut to an answer. - Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com -

Re: Cogent NOC

Walking the line, so to speak. Starting with our directly connected cogent peer. Loss begins at the same hop and carries through to the end host. I'm only using cogentco as an example, but the results are the same anywhere. [root@mon ~]# ping -c 1000 -f 38.88.249.209 PING 38.88.249.209

Re: Cogent NOC

I was going to reply and repeat Job Snijders's indications of Thu, 7 Jul 2016 to Please review the excellent presentation from RA{T,S}: https://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf https://www.youtube.com/watch?v=a1IaRAVGPEE esp the pdf there,

Re: Cogent NOC

On 12/14/2016 11:53 am, Kurt Kraut wrote: > Hello, > > mtr packet loss column has no scientific precision and should not be > considered. It is not mtr fault but forwarding routers have a low priority to > respond to ICMP requests. The only way you can prove there is a problem is a > end to

Re: Cogent NOC

Hello, mtr packet loss column has no scientific precision and should not be considered. It is not mtr fault but forwarding routers have a low priority to respond to ICMP requests. The only way you can prove there is a problem is a end to end ping, the regular ping command, not mtr. Best

Cogent NOC

Hi all, Anyone beyond front line support at cogento on list? Nanog is the last place I'd look for assistance but it seems support over at cogentco is not nearly what it used to be. Example MTR to cogen't own website (support doesn't utilize or understand MTR at all apparently): Host