problem with tile.openstreetmap.org #2223
Comments
|
Author: tom[at]compton.nu Yes - you were deliberately banned because you were bulk harvesting tiles. I believe the administrator of the tile server is looking into the details. The traceroute failing is normal - our host firewalls all ping and traceroute traffic at their border. Please don't mail our host about OSM issues by the way - just contact us and we will talk to the host if necessary. |
|
Author: krysha Replying to [comment:1 tom[at]compton.nu]:
It was TCPTraceroute, rather than the usual traceroute |
|
Author: tom[at]compton.nu Ah right - that will still fail in your case because you had been blocked in iptables. The point about contacting us and not our host still stands anyway. |
|
Author: jburgess777[at]googlemail.com I have removed your IP from the block list. Your IP was blocked after you downloaded in excess of 250k tiles on two occasions:
Normal web users only access a few thousand tiles per day. Bulk download tools place a big burden on our resources and we need to prioritize access to people actively viewing the map over those performing bulk downloads. Please remember this in future and try to restrict the numbers of tiles you download. There are no fixed limits but anything over 100k tiles per day might be seen as excessive and lead to an IP block. |
Reporter: krysha
[Submitted to the original trac issue database at 7.27am, Wednesday, 26th August 2009]
I have a problem with service tile.openstreetmap.org (does not
load layer mapnik).
Supposedly, the problem occurred while loading a large area maps using
TrekBuddy_Atlas_Creator.jar (~06 Aug 2009)
Here's the result of trace
tcptraceroute tile.openstreetmap.org 80
Selected device eth0, address 10.100.22.73, port 50402 for outgoing
packets
Tracing the path to tile.openstreetmap.org (128.40.168.99) on TCP port
80 (http), 30 hops max
1 10.100.22.1 0.637 ms 0.936 ms 0.708 ms
2 10.100.65.233 0.549 ms 0.664 ms 0.714 ms
3 10.100.65.242 1.596 ms 3.354 ms 3.683 ms
4 10.100.64.74 0.508 ms 0.519 ms 0.461 ms
5 94.25.124.105 2.776 ms 2.353 ms 2.384 ms
6 so-1-0-0.m10-igw1.msk.ip.rostelecom.ru (87.226.139.78) 3.058 ms
3.249 ms 2.490 ms
7 xe220-201.RT.V10.MSK.RU.retn.net (87.245.253.17) 3.033 ms 3.037 ms
3.049 ms
8 xe000-9.RT.TC2.LON.UK.retn.net (87.245.233.82) 53.703 ms 85.887 ms
54.003 ms
9 so-0-1-0.lond-sbr4.ja.net (146.97.35.129) 54.768 ms 54.720 ms
54.460 ms
10 so-6-0-0.lond-sbr1.ja.net (146.97.33.153) 57.620 ms 54.907 ms
55.217 ms
11 LMN-LMN1.site.ja.net (146.97.42.62) 55.106 ms 54.615 ms 54.655 ms
12 ucl.lmn.net.uk (194.83.102.82) 54.675 ms 54.966 ms 55.131 ms
13 128.40.125.13 55.366 ms 54.882 ms 55.490 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 *^C
The text was updated successfully, but these errors were encountered: