postimg.org timing out!

billbo · ‎04-04-2007

Hi gang,
Yes I know it's been awhile

I'm having problems reading on another forum that has links to images on http://www.postimg.org/
Most other forumites do not have an issue.
My question is do you have a problem with a timeout and if so is it a possible plusnet DNS issue?
Thanks for taking a look.
Quote....
ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://s5.postimg.org/
The following error was encountered:
Connection to 141.101.123.62 Failed
The system returned:
(110) Connection timed out
The remote host or network may be down. Please try the request again.
Generated Fri, 03 Apr 2015 16:17:20 GMT by pcl-iwfcache04.plus.net (squid)
Another location returned the same error from
"Generated Fri, 03 Apr 2015 16:56:26 GMT by pcl-iwfcache03.plus.net (squid)"

ejs · ‎10-06-2010

Probably the same issue as: https://community.plus.net/forum/index.php/topic,138250.0.html

billbo · ‎04-04-2007

Thanks ejs my search did not pick that one up.
I'll watch both threads with interest.
Cheers

npr · ‎21-01-2013

I think this says it all:

Quote
Tracing route to www.postimg.org [46.229.166.177]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 33 ms 36 ms 33 ms lo0.11.Central11.ptn-bng02.plus.net [195.166.130
.191]
3 33 ms 34 ms 33 ms irb.11.PTW-CR02.plus.net [84.93.249.18]
4 34 ms 33 ms 35 ms ae1.pcl-cr02.plus.net [195.166.129.3]
5 53 ms 34 ms 33 ms po2.pcl-gw02.plus.net [195.166.129.43]
6 34 ms 34 ms 33 ms tun0.pcl-gw01.plus.net [212.159.2.105]
7 flowers2.servers.plus.net.uk [212.159.2.98] reports: Destination net unrea
chable.

Never seen flowers2.servers.plus.net.uk before.

But I can access the site through a proxy server.
http://www.openproxy.co.uk

Apprentice · ‎04-11-2008

Quote
Tracing route to www.postimg.org [46.229.166.177]
over a maximum of 30 hops:
1 * * * Request timed out.
2 74 ms 48 ms 49 ms lo0-central10.ptn-ag02.plus.net [195.166.128.191]
3 49 ms 49 ms 48 ms link-a-central10.ptn-gw01.plus.net [212.159.2.132]
4 50 ms 51 ms 48 ms xe-1-2-0.ptw-cr01.plus.net [212.159.0.112]
5 48 ms 47 ms 49 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
6 48 ms 48 ms 48 ms tun0.ptn-gw01.plus.net [212.159.2.101]
7 48 ms 48 ms 48 ms te2-1.gr9.plus.net [212.159.2.110]
8 50 ms 49 ms 49 ms 195.99.126.138
9 51 ms 55 ms 56 ms 194.72.31.138
10 49 ms 49 ms 49 ms core4-te0-10-0-2.faraday.ukcore.bt.net [213.121.193.55]
11 50 ms 50 ms 49 ms peer2-et-8-3-0.faraday.ukcore.bt.net [62.6.201.197]
12 50 ms 53 ms 53 ms 213.137.183.102
13 50 ms 50 ms 50 ms t2c3-xe-1-3-2-0.uk-lof.eu.bt.net [166.49.237.28]
14 50 ms 51 ms 50 ms t2c3-xe-11-0-2-0.uk-lon1.eu.bt.net [166.49.208.18]
15 55 ms 50 ms 50 ms tge2-1-506.edge1.lon2.uk.as5580.net [195.66.237.111]
16 51 ms 50 ms 50 ms eth3-7.core1.lon1.uk.as5580.net [78.152.44.162]
17 134 ms 134 ms 135 ms eth4-2.core1.nyc1.us.as5580.net [78.152.44.135]
18 * * * Request timed out.
19 139 ms 146 ms 149 ms eth2-3.r1.ash1.us.as5580.net [78.152.35.41]
20 137 ms 137 ms 136 ms 78.152.46.202
21 136 ms 136 ms 135 ms 46.229.166.177
Trace complete.

Looks like my ADSL1 taxi took the tourist route just now

Oldjim · ‎15-06-2007

There is something odd going on with that site
http://www.postimg.org/ redirects to http://postimage.org/
and either goes right round the houses
Tracing route to postimg.org [46.229.166.177] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 38 ms 37 ms 33 ms lo0-central10.pcl-ag05.plus.net [195.166.128.186]
3 33 ms 33 ms 32 ms link-a-central10.pcl-gw01.plus.net [212.159.2.176]
4 33 ms 60 ms 31 ms xe-1-2-0.pcl-cr01.plus.net [212.159.0.208]
5 34 ms 33 ms 32 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 32 ms 32 ms 33 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
7 33 ms 32 ms 32 ms tun0.ptn-gw01.plus.net [212.159.2.101]
8 32 ms 32 ms 32 ms te2-1.gr9.plus.net [212.159.2.110]
9 34 ms 34 ms 33 ms 195.99.126.138
10 36 ms 39 ms 39 ms core2-te0-0-0-10.ilford.ukcore.bt.net [109.159.254.133]
11 34 ms 34 ms 34 ms core4-te0-19-0-3.faraday.ukcore.bt.net [213.121.193.45]
12 33 ms 33 ms 33 ms peer2-et-10-3-0.faraday.ukcore.bt.net [62.6.201.199]
13 34 ms 36 ms 33 ms 213.137.183.98
14 33 ms 33 ms 34 ms t2c3-xe-1-3-3-0.uk-lof.eu.bt.net [166.49.237.72]
15 33 ms 34 ms 33 ms t2c3-xe-1-0-2-0.uk-lon1.eu.bt.net [166.49.208.16]
16 35 ms 43 ms 35 ms tge2-1-506.edge1.lon2.uk.as5580.net [195.66.237.111]
17 35 ms 37 ms 35 ms eth3-7.core1.lon1.uk.as5580.net [78.152.44.162]
18 119 ms 118 ms 118 ms eth4-2.core1.nyc1.us.as5580.net [78.152.44.135]
19 124 ms 123 ms 126 ms eth3-1.core1.ash2.us.as5580.net [78.152.45.193]
20 124 ms 123 ms 124 ms eth2-3.r1.ash1.us.as5580.net [78.152.35.41]
21 121 ms 120 ms 121 ms 78.152.46.202
22 115 ms 115 ms 116 ms 46.229.166.177
Trace complete.
C:\Users\Jim>tracert postimage.org
Tracing route to postimage.org [46.229.168.33]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.lan [192.168.1.254]
2 34 ms 33 ms 35 ms lo0-central10.pcl-ag05.plus.net [195.166.128.186]
3 33 ms 33 ms 32 ms link-a-central10.pcl-gw01.plus.net [212.159.2.176]
4 32 ms 32 ms 32 ms xe-1-2-0.pcl-cr01.plus.net [212.159.0.208]
5 33 ms 32 ms 36 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 33 ms 32 ms 32 ms te9-4.ptn-gw01.plus.net [195.166.129.33]
7 33 ms 32 ms 33 ms tun0.ptn-gw01.plus.net [212.159.2.101]
8 33 ms 33 ms 32 ms te2-1.gr9.plus.net [212.159.2.110]
9 33 ms 34 ms 33 ms 195.99.126.138
10 35 ms 34 ms 35 ms core2-te0-15-0-4.ealing.ukcore.bt.net [109.159.254.208]
11 34 ms 33 ms 34 ms host213-121-193-230.ukcore.bt.net [213.121.193.230]
12 34 ms 33 ms 33 ms 213.137.183.98
13 34 ms 33 ms 33 ms t2c3-xe-11-1-1-0.uk-lof.eu.bt.net [166.49.237.32]
14 36 ms 34 ms 33 ms t2c3-xe-11-0-2-0.uk-lon1.eu.bt.net [166.49.208.18]
15 47 ms 35 ms 38 ms tge2-1-506.edge1.lon2.uk.as5580.net [195.66.237.111]
16 34 ms 34 ms 34 ms eth1-1.core1.lon2.uk.as5580.net [78.152.44.92]
17 33 ms 34 ms 34 ms eth1-1.core1.lon1.uk.as5580.net [78.152.44.99]
18 119 ms 119 ms 118 ms eth4-2.core1.nyc1.us.as5580.net [78.152.44.135]
19 123 ms 126 ms 122 ms eth3-1.core1.ash2.us.as5580.net [78.152.45.193]
20 132 ms 124 ms 124 ms eth2-3.r1.ash1.us.as5580.net [78.152.35.41]
21 122 ms 121 ms 121 ms 78.152.46.202
22 121 ms 120 ms 120 ms 46.229.168.33
Trace complete.

Apprentice · ‎04-11-2008

Try some of the tools from the link:-
http://viewdns.info/

Quote
Pinging www.postimg.org [46.229.166.179] with 32 bytes of data:
Request timed out.
Reply from 46.229.166.179: bytes=32 time=135ms TTL=53
Reply from 46.229.166.179: bytes=32 time=135ms TTL=53
Reply from 46.229.166.179: bytes=32 time=135ms TTL=53
Ping statistics for 46.229.166.179:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 135ms, Maximum = 135ms, Average = 135ms

billbo · ‎04-04-2007

Well something has changed - the links appear to be working again (15:45 4/4/15)

postimg.org timing out!

postimg.org timing out!

Re: postimg.org timing out!

Re: postimg.org timing out!

Re: postimg.org timing out!

Re: postimg.org timing out!

Re: postimg.org timing out!

Re: postimg.org timing out!

Re: postimg.org timing out!