We Still Have Great Cyber Week Deals: Check out our $5 and under smartphone deals!
Need help with your equipment?
JefferMC's profile
JefferMC
20th Community Anniversary
ACE service 9 years
ACE service 8 years
ACE - Expert

ACE - Expert

 • 

30.2K Messages

Thu, Oct 8, 2015 2:41 AM

Bad Facebook Photo performance (again)

Yes, we do seem to have returned to poor Performance with Facebook retreiving photos.

 

I am again being routed by Facebook to a Miami server (when I think they also have servers in Atlanta, which is a lot closer, and my traffic is probably being routed through).

 

I don't think the entire performance problem is Facebook's but if they're routing my traffic through to Miami (when Atlanta would do), you have to wonder who else's traffic they're routing to Miami and what load that's placing on the servers and netwokt there.

 

For those who complain about AT&T routers not responding on trace routes, look at Level3's between Atlanta and Miami:

 

 


Tracing route to scontent-mia1-1.xx.fbcdn.net [31.13.73.7] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms homeportal [192.168.1.254] 2 * * * Request timed out. 3 21 ms 20 ms 20 ms 99.168.xxx.xx 4 24 ms 23 ms 21 ms 12.83.113.xx 5 27 ms 27 ms 32 ms 12.122.117.121 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 80 ms * * 4.15.152.70 10 * 82 ms 80 ms po102.psw01d.mia1.tfbnw.net [74.119.79.225] 11 82 ms 83 ms 113 ms msw1at.01.mia1.tfbnw.net [173.252.64.96] 12 80 ms 82 ms 81 ms xx-fbcdn-shv-01-mia1.fbcdn.net [31.13.73.7] Trace complete. C:\>tracert scontent-mia1-1.xx.fbcdn.net Tracing route to scontent-mia1-1.xx.fbcdn.net [31.13.73.7] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms homeportal [192.168.1.254] 2 * * * Request timed out. 3 21 ms 21 ms 21 ms 99.168.xxx.xx 4 24 ms 23 ms 25 ms 12.83.113.xx 5 30 ms 29 ms 29 ms 12.122.117.121 6 907 ms * * ae15.edge5.atlanta2.level3.net [4.68.62.225] 7 * * * Request timed out. 8 * * * Request timed out. 9 82 ms 80 ms 82 ms 4.15.152.70 10 80 ms 80 ms * po102.psw01d.mia1.tfbnw.net [74.119.79.225] 11 83 ms * 81 ms msw1at.01.mia1.tfbnw.net [173.252.64.96] 12 80 ms * 80 ms xx-fbcdn-shv-01-mia1.fbcdn.net [31.13.73.7] Trace complete.

 

So, right now, I'm blaming Facebook and Level3. 

Award for Community Excellence 2021 Achiever*
*I am not an AT&T employee, and the views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Guru

 • 

1.1K Messages

7 years ago


@JefferMC wrote:

Yes, we do seem to have returned to poor Performance with Facebook retreiving photos.

 

I am again being routed by Facebook to a Miami server (when I think they also have servers in Atlanta, which is a lot closer, and my traffic is probably being routed through).

 

I don't think the entire performance problem is Facebook's but if they're routing my traffic through to Miami (when Atlanta would do), you have to wonder who else's traffic they're routing to Miami and what load that's placing on the servers and netwokt there.

 

For those who complain about AT&T routers not responding on trace routes, look at Level3's between Atlanta and Miami:

 

 


Tracing route to scontent-mia1-1.xx.fbcdn.net [31.13.73.7] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms homeportal [192.168.1.254] 2 * * * Request timed out. 3 21 ms 20 ms 20 ms 99.168.xxx.xx 4 24 ms 23 ms 21 ms 12.83.113.xx 5 27 ms 27 ms 32 ms 12.122.117.121 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 80 ms * * 4.15.152.70 10 * 82 ms 80 ms po102.psw01d.mia1.tfbnw.net [74.119.79.225] 11 82 ms 83 ms 113 ms msw1at.01.mia1.tfbnw.net [173.252.64.96] 12 80 ms 82 ms 81 ms xx-fbcdn-shv-01-mia1.fbcdn.net [31.13.73.7] Trace complete. C:\>tracert scontent-mia1-1.xx.fbcdn.net Tracing route to scontent-mia1-1.xx.fbcdn.net [31.13.73.7] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms homeportal [192.168.1.254] 2 * * * Request timed out. 3 21 ms 21 ms 21 ms 99.168.xxx.xx 4 24 ms 23 ms 25 ms 12.83.113.xx 5 30 ms 29 ms 29 ms 12.122.117.121 6 907 ms * * ae15.edge5.atlanta2.level3.net [4.68.62.225] 7 * * * Request timed out. 8 * * * Request timed out. 9 82 ms 80 ms 82 ms 4.15.152.70 10 80 ms 80 ms * po102.psw01d.mia1.tfbnw.net [74.119.79.225] 11 83 ms * 81 ms msw1at.01.mia1.tfbnw.net [173.252.64.96] 12 80 ms * 80 ms xx-fbcdn-shv-01-mia1.fbcdn.net [31.13.73.7] Trace complete.

 

So, right now, I'm blaming Facebook and Level3. 


Same problem here. Facebook just seems to always have some kind of problem.

JefferMC

ACE - Expert

 • 

30.2K Messages

7 years ago

Today my photo requests are being made to a server in the Washingon, DC area (IAD).  Not much better than Miami, Facebook. 

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.