**************Quote from Facebook at 08:50(UTC+7) on 20 August 2015
We have completed our investigation and I wanted to let you know our outcome and the steps we are taking to mitigate the situation where traffic overflows to the Comcast transit IP in San Jose.
After reviewing our routing policies we found that Comcast announces to the FNA deployment in San Jose the IP prefixes for all of its customers, including some IP blocks belonging to your customers.
Just as this works for your FNA it makes those prefixes "eligible" for traffic but we will only ever send traffic to that deployment if it has available capacity and has the best latency.
Unfortunately we ran into a situation where we were completely out of capacity with the Jastel network in Asia and our automated global load balancer had to resort to the 6th best location that had capacity and it just happened to be with
Comcast in San Jose.
After concluding the investigating we agree that it is unacceptable for this situation to happen and here are the steps that we are taking to make help mitigate this from happening in the future:
1. We have updated our global load balancing algorithms to make sure that the Comcast servers blacklist all ASNs except AS7922. This means that your prefixes should never be eligible to be sent to this deployment.
2. We have more FNA servers that are currently being configured and will be shipped out this month. This should be able to absorb more CDN traffic within your network.
3. We are going to work with you to add more PNI peering capacity. My colleague will be reaching out to you in the near future to figure out logistics.
4. We are continually adding capacity to our edge locations in Asia so that we can serve more traffic. The Asian market is very important to us and we want to be able to serve our users and the ISPs as best we can.
Again, my apologies for the issues you have had and we all want to thank you for working with us to fix this situation.
**************End quote from Facebook at 08:50(UTC+7) on 20 August 2015