East Coast DDOS Filtering

[Francisco]

Looks like this will be online in the next 48 - 72 hours

Things are finally rolling and we're getting LOA's and such in place to get our session online.

Francisco

 

[drmike]

Glad to hear this.

 

[RiotSecurity]

Looks like this will be online in the next 48 - 72 hours


Things are finally rolling and we're getting LOA's and such in place to get our session online.


Francisco

make my life complete and add bitcoin as a payment method ?

 

[Francisco]

Hah!

Francisco

 

[Francisco]

Hardware is being provisioned as we speak

LOA has been submitted upstream to not only Staminus but to their upstream providers.

Francisco

 

[drmike]

So you are going live by this weekend?

 

[Francisco]

So you are going live by this weekend?

Morning

It's quite possible some of the ISP's will approve the LOA tonight.

The configuring on my end is only a few hours honestly. I'm spending most of my time waiting on compiles.

Francisco

 

[Francisco]

I'm handling the install now

IP's should already appear for sale in the panel and will start routing in the next couple hours.

Francisco

 

[NodeBytes]

Do you have a test IP for ping/traceroute?

 

[Francisco]

198.251.81.1

Got a few quirks to work out with the rest of the subnet but that should be done in just a little bit.

Francisco

 

[Aldryic C'boas]

Filtered IPs are now selectable in the billing panel.  Fran's putting on the finishing touches, should be 100% ready within the next hour or so.

 

[drmike]

Can you or Fran confirm the whole latency thing once everything is implemented?   Latency increase of filtering vs. unfiltered in Buffalo?   Yeah I know there were speculative numbers earlier.   Just wondering how it all adds up at the end.

 

[Francisco]

Can you or Fran confirm the whole latency thing once everything is implemented?   Latency increase of filtering vs. unfiltered in Buffalo?   Yeah I know there were speculative numbers earlier.   Just wondering how it all adds up at the end.

I'm seeing about 20 - 30ms difference from the west coast. I'm at < 120ms compared to a usual 90 - 95ms.

The latency bump makes sense from the west coast since it's going to NYC first then to Buffalo.

If you're on the east coast you should see no increase if not a decrease since you aren't backhauling to chicago first.

Francisco

 

[Rob T]

Fran - Did you ever announce who you are using for mitigation?  I didn't think Staminus had an east coast location, but they are the only provider I've seen mentioned.

 

[Francisco]

Fran - Did you ever announce who you are using for mitigation?  I didn't think Staminus had an east coast location, but they are the only provider I've seen mentioned.

Hey Rob!

Welcome to the forums

Staminus recently launched an east coast POP out of TELX.

The server is already online, as is our BGP session. We're just waiting for them to fix an ACL blocking the rest of our /24 from routing and we're good to go.

Francisco

 

[qps]

traceroute to 198.251.81.1 (198.251.81.1), 30 hops max, 40 byte packets

 1 ae1-40g.ar1.atl1.us.nlayer.net  (69.31.135.130) 36.558 ms 3.058 ms 4.029 ms 

 2 ae3-115.atl11.ip4.tinet.net  (199.229.231.217) 0.367 ms 

   ae3-113.atl11.ip4.tinet.net (173.241.128.245) 0.313 ms 

   ae3-115.atl11.ip4.tinet.net (199.229.231.217) 0.646 ms 

 3 xe-2-1-0.nyc34.ip4.tinet.net  (141.136.108.153) [AS 3257] 22.651 ms 

   xe-4-0-0.nyc30.ip4.tinet.net (213.200.81.90) [AS 3257] 22.428 ms 22.486 ms 

 4 * * * 

 5 * * * 

 6 (162.220.32.18) [AS 25761] 28.831 ms 22.754 ms 22.722 ms 

 7 198.251.81.1  (198.251.81.1) [AS 53667] 35.880 ms 35.778 ms 35.722 ms 

 

[Rob T]

Very cool.  I'm really surprised there isn't someone operating out of NoVa, Atlanta, or Miami doing mass-market filtering.

 

[Jack]

Up and running Fran?

 

[RiotSecurity]

198.251.81.1


Got a few quirks to work out with the rest of the subnet but that should be done in just a little bit.


Francisco

 4  xe-7-0-3.bar2.Toronto1.Level3.net (4.28.138.69)  54.491 ms  56.062 ms  58.333 ms


 5  ae-0-11.bar1.Toronto1.Level3.net (4.69.151.241)  61.348 ms  61.768 ms  62.889 ms


 6  ae-9-9.ebr1.Chicago1.Level3.net (4.69.151.110)  106.271 ms  61.357 ms  69.560 ms


 7  ae-6-6.ebr1.Chicago2.Level3.net (4.69.140.190)  72.689 ms  72.654 ms  73.398 ms


 8  ae-1-51.edge3.Chicago3.Level3.net (4.69.138.136)  72.659 ms  72.653 ms  72.654 ms


 9  xe-1-3-0.chi12.ip4.tinet.net (213.200.73.161)  72.634 ms  73.302 ms  74.064 ms


10  141.136.110.150 (141.136.110.150)  196.857 ms  197.450 ms 141.136.110.146 (141.136.110.146)  89.429 ms


11  * * *


12  * * *


13  . (162.220.32.18)  78.397 ms  78.391 ms  80.888 ms


14  198.251.81.1 (198.251.81.1)  90.406 ms * *

 

[Francisco]

I'm not sure if there's any ISP's pending applying our prefixes so I can't guarantee that paths will get better.

I am hoping that L3 is on tap, though

Francisco