RE: Anyone from Facebook here?

> You may want to follow up on this email thread. > IPv6 vs IPv4 performance to m.facebook.com. Mark: Thanks. We saw this on bind-users and are tracking in t13843732. -- dsp

Re: Facebook Geo Routing Issues

Please send details of your mistargeting to me offlist and we'll take a look. Please include the ips of your rdns as observed by . -- dsp From: NANOG on behalf of Mike Hammett Sent: Wednesday, November 16, 2016 5:50:57 PM To:

Re: Facebook more specific via Level3 ?

> 31.13.70.0/24 > > This more specific is only visible via AS3356 ... Facebook > isn’t even announcing it via direct peering. This specific, and many others, are only announced to peers in the metro they originate in. To receive this prefix directly you'll need to peer with us in Los Angeles. It

Re: Facebook more specific via Level3 ?

> looks like this is also affecting other prefixes: Many of our prefixes are only announced to peers in the metro they originate in. Please stop obsessing about this detail; it's not the problem. > I understand that FB is using some type of DNS > geo-loadbalancing and other mechanism to redirect

RE: Facebook & Traceroute

> Why does Facebook spoof the source IP address > of the hop before this server? They spoof the > source IP address that is performing the traceroute. It's a known bug; apologies. I've asked again that we rollout the fix. -- dsp

Re: Facebook broken over v6?

We're actively investigating the v6 issues. We need more data though. If you're experiencing problems, please email me a tcpdump/pcap or any other debug data you think will help. Thanks, -- dsp