RE: Anyone from Facebook here?

[Doug Porter]

> 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

[Doug Porter]

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: John Cenile
Cc: nanog@nanog.org
Subject: Re: Facebook Geo Routing Issues

I'm in Chicago and I saw mine going to Miami as well (per rDNS). Haven't looked 
into it at all.

I did see a video where they said they occasionally purposely give people less 
than ideal facilities to test connectivity. Maybe that process buggered up?




-
Mike Hammett
Intelligent Computing Solutions
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ics-2Dil.com&d=DgICaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MF3a4wEnEeEz9tFgYNQ_0w&m=hGHpg7HEOs8pvyDgxRdzwrfx47z4OzMxGNVrLep7PPI&s=2h-7_wY816g9xPqBfaEhuKWLRyx-PulhMJqe3aHAZ4g&e=

Midwest-IX
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.midwest-2Dix.com&d=DgICaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=MF3a4wEnEeEz9tFgYNQ_0w&m=hGHpg7HEOs8pvyDgxRdzwrfx47z4OzMxGNVrLep7PPI&s=QalI7b2Q2U_Mxb_wP9sIsftaGWoqaSDcwbat8S1xp5U&e=

- Original Message -

From: "John Cenile" 
To: nanog@nanog.org
Sent: Wednesday, November 16, 2016 7:48:25 PM
Subject: Facebook Geo Routing Issues

Hello,

Does anybody have a contact I could use at Facebook to get a routing issue
resolved?

Some of our networks are being routed to Miami, rather than using the much
closer PoP of Sydney, and it's obviously causing significant performance
issues when browsing Facebook.

Re: Facebook more specific via Level3 ?

[Doug Porter]

> 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 appears you're in Austria though, which means there's likely
no use in you peering with us in LA.  We globally load balance
people to the best point of presence.  You shouldn't see much, if
any, traffic to or from the above prefix.

> Any Facebook admin on or off list available to get this
> debugged and tracked down?

Please reach out to n...@fb.com in the future.

Regards,
-- 
dsp

Re: Facebook more specific via Level3 ?

[Doug Porter]

> 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 users to
> (possibly) nearer mirrors.

We target traffic two ways.  One is relatively traditional dns
global load balancing, using the resolver ip.  The other
method---which steers the vast majority of our traffic---vends
urls that send people to a specific PoP based on their client ip.

It appears you're having a targeting problem.  Please reach out
to our NOC to get support.

-- 
dsp

RE: Facebook & Traceroute

[Doug Porter]

> 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?

[Doug Porter]

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