Tinypic pictures never load

PikaPuff

I only get an eternal loading symbol if there's a tinypic picture on a page. The only thing google suggests is turning jumbo packets off, which I have done to no effect. Any ideas?

End

cam you at least load the tinypic main page? (http://tinypic.com/ or whatever)

PikaPuff

nope. I think a loaded a pic from n51 earlier. or whatever letter + 51.tinypic.com, like 52 and 53 didn't load.

japan

What browser?

Tinypic has had compatibility problems forever. I don't think it ever worked in Opera.

PikaPuff

every browser

so far chrome, firefox, ie

Sheep

Also, TinyPic is pretty much a dead service. They've been threatening to shut it down for years.

End

What error does your browser report for the main tinypic page? Or any images for that matter? Is it a time out? Connection refused?

What address does www.tinypic.com resolve to? What does traceroute show? (More detailed instructions: open a command prompt, run "nslookup www.tinypic.com". Personally, I get 209.17.70.143. Next try "tracert www.tinypic.com". What are the last few lines? Personally I don't get a lot of lines, but there's a small chance it could be illustrative)

PikaPuff

No error as it's eternally loading. I can leave the tab open for weeks and it will still continue to attempt to load.

Non-authoritative answer:
Name: www.tinypic.com
Address: 209.17.70.143

8 68 ms 66 ms 70 ms xe-8-2-0.edge1.LosAngeles6.Level3.net [4.26.0.13]
9 62 ms 63 ms 63 ms vlan90.csw4.LosAngeles1.Level3.net [4.69.144.254]
10 64 ms 63 ms 63 ms ae-92-92.ebr2.LosAngeles1.Level3.net [4.69.137.29]
11 73 ms 74 ms 75 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
12 91 ms 73 ms 69 ms ae-5-5.ebr4.SanJose1.Level3.net [4.69.148.142]
13 76 ms 77 ms 78 ms ae-34-34.ebr2.SanJose1.Level3.net [4.69.153.33]

14 106 ms 108 ms 108 ms ae-3-3.ebr1.Denver1.Level3.net [4.69.132.58]
15 * 806 ms 187 ms ae-11-51.car1.Denver1.Level3.net [4.69.147.67]
16 104 ms 107 ms 107 ms PHOTOBUCKET.car1.Denver1.Level3.net [4.53.1.42]

17 * * * Request timed out.
18 101 ms 118 ms 105 ms 209.17.70.143

Trace complete.

End

it never times out?
that's ...strange

End

I don't think I'm going to be able to reasonably determine where your problem is, but what OS are you using?

PikaPuff

win7

and uh. i think at the time of those commands tinypic was working for the first time this year

PikaPuff

http://i53.tinypic.com/orplk9.png

here's a picture that never loads.

>nslookup i53.tinypic.com
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: i53.tinypic.com
Address: 209.17.74.144


>tracert i53.tinypic.com

Tracing route to i53.tinypic.com [209.17.74.144]
over a maximum of 30 hops:


6 * * * Request timed out.
7 105 ms 69 ms 66 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
8 67 ms 153 ms 89 ms xe-4-1-0.edge1.LosAngeles6.Level3.net [4.26.0.73
]
9 65 ms 63 ms 63 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
10 63 ms 63 ms 63 ms ae-82-82.ebr2.LosAngeles1.Level3.net [4.69.137.2
5]
11 91 ms 70 ms 89 ms ae-6-6.ebr2.SanJose5.Level3.net [4.69.148.202]
12 77 ms 72 ms 89 ms ae-5-5.ebr4.SanJose1.Level3.net [4.69.148.142]
13 77 ms 79 ms 76 ms ae-34-34.ebr2.SanJose1.Level3.net [4.69.153.33]

14 140 ms 99 ms 95 ms ae-3-3.ebr1.Denver1.Level3.net [4.69.132.58]
15 100 ms 115 ms 98 ms ae-11-51.car1.Denver1.Level3.net [4.69.147.67]
16 97 ms 103 ms 108 ms PHOTOBUCKET.car1.Denver1.Level3.net [4.53.1.42]

17 95 ms 96 ms 95 ms 209.17.74.144

Trace complete.

Adus

Try manually setting your DNS? The Google ones are good: 8.8.8.8 and 8.8.4.4. Unless that's what you're using?

PikaPuff

it is

End

yeah dns looks correct

traceroute looks very similar to mine, but it's not completely identical. I don't think there's an issue there.

I suspect the issue is most likely related to being able to build a stable tcp connection to their server(s), but that would probably take some fiddling with the registry to fix? I don't have a ton of experience with that sort of thing.

PikaPuff

Either way, I thought this was an common issue. Looks like it's not. I'm done looking into it for now. Thanks for your help, guys.

L|ama

google DNS can cause problems with content distribution networks, a lot of the time tumblr images wouldn't load for me when I was using the google DNS but it's fine now that I've gone back to my ISP's. Might be the same thing.

PikaPuff

huh. i'll try that when i go home. just put it blank?

MKR

edit: misread