Images not working

[quote=Starrz][quote=Matt] Could you also run a tracert on edge1.mobafire.com? If you haven't done it before, on Windows just open a command prompt and run "tracert edge1.mobafire.com", and post or send me the results. This will help to see where the failure is occurring, whether it is happening within the host or somewhere between you and them. [/quote] First tracert: Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\E>tracert edge1.mobafire.com Tracing route to mobafire.criticalclicknet.netdna-cdn.com [69.174.57.112] over a maximum of 30 hops: 1 1 ms 1 ms <1 ms homeportal [mirror-ip] 2 26 ms 22 ms 23 ms [my-ip].lightspeed.miamfl.sbcglobal.net [my-ip] 3 * * * Request timed out. 4 24 ms 22 ms 33 ms 99.167.141.26 5 23 ms 23 ms 23 ms 12.83.70.13 6 24 ms 25 ms 24 ms fdlfl01jt.ip.att.net [12.122.81.29] 7 38 ms 47 ms 39 ms 192.205.32.18 8 40 ms 45 ms 40 ms po3-20G.ar1.MIA2.gblx.net [67.16.132.9] 9 39 ms 49 ms 39 ms packet-exchange.tengigabitethernet9-2.ar1.mia2.g blx.net [207.138.112.138] 10 44 ms 39 ms 49 ms te0-1.cr1.atl1.us.packetexchange.net [69.174.120 .46] 11 44 ms 39 ms 39 ms 69.174.38.2 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. ================================================== Second tracert: C:\Users\E>tracert edge1.mobafire.com Tracing route to mobafire.criticalclicknet.netdna-cdn.com [69.174.57.112] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms homeportal [mirror-ip] 2 24 ms 24 ms 23 ms [my-ip].lightspeed.miamfl.sbcglobal.net [my-ip] 3 * * * Request timed out. 4 * * * Request timed out. 5 24 ms 23 ms 23 ms 12.83.70.13 6 24 ms 25 ms 25 ms fdlfl01jt.ip.att.net [12.122.81.29] 7 42 ms 40 ms 41 ms 192.205.32.18 8 40 ms 46 ms 41 ms po3-20G.ar1.MIA2.gblx.net [67.16.132.9] 9 60 ms 50 ms 40 ms packet-exchange.tengigabitethernet9-2.ar1.mia2.g blx.net [207.138.112.138] 10 39 ms 50 ms 52 ms te0-1.cr1.atl1.us.packetexchange.net [69.174.120 .46] 11 40 ms 39 ms 39 ms 69.174.38.2 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. ============================================================ My friend is about to post his tracert. His mobafire works. He's the one who lives in Carol City and has Bellsouth.[/quote]

[quote=Xialnde]Hi, I'm Starrz friend in Carol City. I have no problems but here are my results. Tracing route to mobafire.criticalclicknet.netdna-cdn.com [69.174.57.112] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms homenetwork-ip 2 16 ms 15 ms 38 ms adsl-my-ip.mia.bellsouth.net [my-ip] 3 30 ms 16 ms 16 ms 205.152.108.1 4 17 ms 13 ms 15 ms ixc00mia-ge-0-2-2.bellsouth.net [205.152.145.25] 5 17 ms 13 ms 14 ms 12.81.8.20 6 17 ms 16 ms 16 ms 12.81.8.9 7 19 ms 20 ms 17 ms 74.175.192.174 8 27 ms 24 ms 24 ms cr81.fldfl.ip.att.net [12.122.106.94] 9 22 ms 18 ms 193 ms fldfl01jt.ip.att.net [12.122.81.25] 10 29 ms 32 ms 28 ms 208.178.58.145 11 21 ms 23 ms 23 ms po3-20G.ar1.MIA2.gblx.net [67.16.132.9] 12 41 ms 32 ms 34 ms packet-exchange.tengigabitethernet9-2.ar1.mia2.g blx.net [207.138.112.138] 13 49 ms 43 ms 46 ms te0-1.cr1.atl1.us.packetexchange.net [69.174.120 .46] 14 36 ms 34 ms 39 ms 69.174.38.2 15 41 ms 40 ms 42 ms 69.174.57.112 Trace complete.[/quote]

[quote=Papuchongo]Hello, I'm Starrz' other friend :] Confirming that Mobafire works fine for me. I live less than 2 blocks away using Comcast, here's the tracer... Tracing route to mobafire.criticalclicknet.netdna-cdn.com [MY IP] over a maximum of 30 hops: 1 4 ms 6 ms 9 ms CISCO38236 [LOCAL IP] 2 14 ms 13 ms 10 ms 73.230.143.1 3 14 ms 75 ms 15 ms xe-0-2-0-0-sur01.hialeahwest.fl.pompano.comcast. net [68.85.125.33] 4 19 ms 21 ms 24 ms te-0-2-0-6-ar03.northdade.fl.pompano.comcast.net [68.87.162.129] 5 20 ms 35 ms 28 ms he-0-8-0-0-cr01.miami.fl.ibone.comcast.net [68.8 6.93.85] 6 30 ms 29 ms 35 ms pos-1-9-0-0-cr01.atlanta.ga.ibone.comcast.net [6 8.86.85.1] 7 30 ms 40 ms 34 ms pos-0-2-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.86.166] 8 31 ms 32 ms 37 ms 66.208.229.54 9 30 ms 34 ms 29 ms 69.174.38.2 10 33 ms 29 ms 30 ms 69.174.57.112 Trace complete.[/quote]

[quote=Bolo][quote=Anhedonist] I'm in Birmingham, Alabama receiving the same issue for the past 2-3 days now. Of course, I also tried clearing cache several times with no luck. (I even had to wait for the missing image icon to pop up to hit send) [/quote] I also live in B'ham, AL, and it's been doing this to me for about 2 weeks now. I've completly switched from Firefox to Chrome because I thought it was Firefox messing up, but the same problem persists on Chrome.[/quote]

[quote=Matt]Thanks guys this is proving to be massively helpful!! One more question, if you don't mind, could all of you post your City and what ISP you are on? This may help the host isolate any routing issues that you seem to be having.[/quote]

[quote=evanxcs]Nashville, TN. AT&T U-verse.[/quote]

[quote=Matt]I've sent all this new information to the CDN provider, hopefully they get back to me quickly. Unfortunately I'm not seeing any patterns. I thought it might be region and/or ISP related but I've had reports from users on Bellsouth, AT&T and Comcast, and from users on both the east and west coasts. The two of you with failing tracerts both failed at the exact same place, while your friends got past it. I believe this may be one of their internal routing servers. Starrz and evanxcs can you do me a favor, and try pinging those two addresses? 69.174.38.2 and 69.174.57.112? I'm guessing you will actually be able to ping both fine. Which leads me to believe that you are just not getting routed properly.[/quote]

[quote=Matt]@LaCorpse, since you are in Cali, it would be great to get a tracert from you as well. Just open a command prompt and "tracert edge1.mobafire.com" and paste your results here. I'd like to see where yours fails, and if it's also on one of the CDN's routing servers, and if so which one.[/quote]

[quote=tainted07]Hey, I'm having the same problem as everyone else. I live in Milton Florida. I have At&t U-verse. I did a tracert of both edge1.mobafire.com and edge2.mobafire.com since a lot of people were saying they had problems with edge2 as well. [IMG]http://i472.photobucket.com/albums/rr84/soulhawk30/trace-1.jpg[/IMG] I hope this can get fixed sometime soon![/quote]

[quote=evanxcs]I actually got through to the first one fine, but couldn't ping the second one at all: C:\Documents and Settings\Evan>ping 69.174.38.2 Pinging 69.174.38.2 with 32 bytes of data: Reply from 69.174.38.2: bytes=32 time=29ms TTL=50 Reply from 69.174.38.2: bytes=32 time=28ms TTL=50 Reply from 69.174.38.2: bytes=32 time=28ms TTL=50 Reply from 69.174.38.2: bytes=32 time=28ms TTL=50 Ping statistics for 69.174.38.2: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 29ms, Average = 28ms C:\Documents and Settings\Evan>ping 69.174.57.112 Pinging 69.174.57.112 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 69.174.57.112: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),[/quote]