Signal the attacked host or subnet with a standard BGP community and let TurkIX enforce the drop inside the exchange.
TurkIX BGP Blackholing gives public peering participants a fast way to signal attacked prefixes over their existing route server sessions and have matching traffic discarded inside the TurkIX fabric. It is designed for live DDoS response, keeping mitigation targeted to the affected destination while preserving capacity for the rest of the network.
Signal the attacked host or subnet with a standard BGP community and let TurkIX enforce the drop inside the exchange.
The blackhole applies only to the attacked destination and only for the member requesting protection, helping preserve unaffected services.
Because the routes are not redistributed, other members do not receive extra blackhole prefixes or unexpected routing changes.
Members announce the attacked host or subnet as a more-specific prefix tagged with the TurkIX blackhole community. If the prefix length matches policy, TurkIX suppresses matching traffic inside the exchange before it reaches the congested member-facing edge.
To activate BGP Blackholing, tag the attacked prefix with the TurkIX blackhole community and announce it through an existing route server session. Announcements outside the accepted ranges are ignored.
Use the narrowest attacked host or subnet that fits inside the accepted IPv4 more-specific range.
Announce the impacted IPv6 destination within the allowed range for blackhole signaling.
A typical BGP Blackholing workflow at TurkIX follows a short, predictable sequence during an attack event.
Confirm the impacted host or subnet and choose the narrowest more-specific prefix allowed by policy.
Tag the selected prefix with community 65535:666 and announce it to an existing TurkIX route server session.
Matching packets are discarded inside the exchange fabric before they continue toward the affected member-facing edge.
Remove the announcement after the event so normal traffic to the destination resumes through the standard routing path.
Blackholing is applied inside the TurkIX public peering environment and is not intended to interfere with private service delivery.
Other members do not receive blackhole announcements, which keeps their routing tables unchanged and avoids extra prefix pressure.
The drop is enforced toward the announcing member's port(s), keeping the action isolated even if a request is made in error.
Operators can activate the signal during an event and withdraw it when the attack subsides, using their existing BGP operations model.
TurkIX Communications Ltd
Str. Han Kubrat 1, floor 3 office 306, 4000 Plovdiv, Bulgaria
24/7 NOC — noc@turkix.bg
Sales — sales@turkix.bg
+359 877 75 5924
63 Shipchenski prohod Blvd. 1574 Sofia, Bulgaria