IPv6
We have the technical capability of doing IPv6 mitigation and three of our locations. We currently however do not offer it, we just don't have enough commit to offer it standalone with any serious volume - primarily due to the need for such filtering being so small. IPv6 is barely used both by clients, and by attackers. We enquired with one of our upstreams a while ago who protect a lot of IRC servers, we asked if they had ever seen IPv6 attacks, the answer was rarely - its been over a year since the last one.
Personally, we will keep working on the capability - we still need to upgrade and test a lot of more of our software to work with IPv6. We will aim to be ready before IPv6 attacks become mainstream, we have a timeline for that and honestly I think thats the best thing to be doing at the moment.
If you experience an IPv6 attack, remove IPv6 while it is occuring. Swapping around addresses could also help (hell, run a round robin of 100+ addresses and make it difficult to attack....). If someone has a legitimate problem with IPv6 attacks, you can contact us. We would be happy to try and help you out if we can.
Graphing
@
drmike
While I must admit I like pretty things and to see the system working. I do know the difficulties costs involved in extracting the data for producing attack graphs. While it is possible in most cases to produce graphs, to produce them accurately usually produces extra load on systems, or requires additional hardware to measure flows. A lot of the time const cutting in order to meet the budgets of the desired audience can really impact this. There is usually a lot more to producing these graphs than just measuring the flow through the filters, most systems are able to send ACLs / rues to upstream routers to perform the heavy lifting (i.e a rule might be to drop fragmented UDP packets).
Now this is not to say we don't offer attack details where we can, but accurate graphs can be a challenge.
X4B.Net provides the following system data (currently)
Notifications:
Notification on Nullroute
Notification on Un-Nullroute
Planned Notification:
Notification on Network Level Mitigation start (some locations)
Notification on Software / Layer 7 Mitigation start (optional)
Data Available:
Software / Layer 7 mitigation state: As well as providing Layer7 mitigation this layer takes care of Layer 4 mitigation events < 80k PPS / 800mbps and cleans up network level mitigation significantly. Activation Times and Dates are provided for this location, type of attack is available if we can categorize the dynamic filter created into a named category (DNS Amp, SYN Flood etc). Layer 7 status is also available for most attack types (Wordpress, Joomla, GHP Food, Enhanced Mitigation etc).
Network Level Status: In some locations we can provide information, on the state of mitigation at the network level. This usually includes a table similar to the one provided for Software level mitigation events and in the case of Italy (and hopefully soon another location) a graph. We can also get attack details via ticket for the locations we dont currently have information on, if you have a reason to need it.
Our staff do have access to some data visualization (its actually a 100/s packet sample), customers do not yet have access to this - the lack of scale and fairly raw nature of the data makes it problematic to display without inducing support tickets (Why was I nullrouted when attack is as big as the previous one? etc).