Under attack
Under attack? Start here.
If you have your own ASN and at least one /24, we can set up an emergency connection. Read the part about time first.
- noc@yam.network
01
What we can do now
With your own ASN and a prefix of /24 or larger, an emergency connection has three parts.
- 01
A BGP session. We set up a session between your network and AS208355, and agree how clean traffic comes back to you.
- 02
Route objects and ROAs. Your ASN goes into our AS-SET, AS208355:AS-CUSTOMERS, so our upstreams accept your routes. Your prefixes need valid ROAs and route objects.
- 03
Your announcement. You announce the prefixes under attack to us. We filter the attack and deliver the clean traffic back to you.
02
What to send us
Put all of it in the first message. Every answer we don't have to ask for saves a round trip.
- ASN AS64496
- Prefixes under attack 203.0.113.0/24
- Attack started date and time, in UTC
- Upstreams which providers, and which links
- Contact a name, a phone number and an email we can use tonight
Example values are documentation ranges (RFC 5737, RFC 5398).
03
How to reach us
Write to the NOC address, with the details above in the first message.
- noc@yam.network
04
How long it takes
A first connection can take hours. We won't promise a time we haven't measured.
Most of the wait is outside our hands. Upstream providers build their route filters from IRR data, and many rebuild them on a schedule, not on request. The BGP session and the link take time too.
So talk to your upstream as well. Asking them to filter the attack, or to blackhole only the one address under attack, can still be the right call for tonight. It keeps the rest of your network up while we connect.
No ASN of your own, or nothing as large as a /24? Then we can't connect you in an emergency. Talk to your upstream now, and write to us when it's over.