what i’m noticing here is that @jpmeijers seems not to be interested in a sort of discussion/help/envolvement/development of his one man show. it seems more like a decision that will happen some day. else there had been a sort reaction in 30 days and the amount of offers that i read here the last weeks…
1 Like
There have been responses, may-be not public. He is swamped with work and probably unable to respond to messages on the forum, public or private (of which there have been many).
Some information:
Heavy servers, plenty of RAM, CPU and (fast) storage, a number of large VMs with a lot of resources and Cloudflare are all part of the current setup.
1 Like
First of all, if JP had wanted to, there would certainly be much more information available…such as how large the database is, how much traffic is generated each day…all of this information is missing. Therefore, inquiries or offers such as “I have space in the data center but I don’t have a server” don’t really make sense. If so, JP needs to provide specific information here. In my opinion, it makes little sense to continue with his version otherwise.
I also find the integration of Cloudflare more than questionable. I can’t think of any reason why it would be needed.
I have now taken another look at getting JP’s Github version up and running. However, this has raised more questions than answers for me.
Of the 25,523 accessible gateways, I only get plausible values with latitude and longitude from 11,956.
So the data does not come solely from the stored path, which can be found in the repo. There seem to be other direct sources here that I cannot access.
Even though my second version is nowhere near as fancy as JP’s,
it works and is stable. My focus was primarily on creating an alternative functional version.
I’m done for now. If interest increases, then implementation and improvement will continue.
https://www.ttn-mapper.org
I wish you all the best for 2026.
2 Likes
May-be you could if you had been running the service for 10 years? Don’t you think there have been DDOS attacks on this service where Cloudflare could be used to mitigate the impact?
I don’t think it’s easy to deduce the why of things based solely on what is available in GitHub.
1 Like
The goal of this thread is to gauge the necessity of a service like TTN Mapper. That was made clear in the original post:
So, is it time to shut down TTN Mapper?
Please leave your comments, opinions or any ideas down below.
So far I have seen very few comments in this thread that truly needs a response from me. This thread is not for discussing technical decisions on how and why the service works as it does.
“I’ll offer free hosting” is not a solution. We’ve been there 9 years ago and it did not go well. I am not taking up offers like that anymore.
What we need is someone with the right technical skills and a passion for the project. Along with a model to fund the project. I have not seen any solutions like that being mentioned here yet. There are however also talks off-forum that could turn into long term solutions.
Do you expect someone here to draw up a business plan for this?
You have certainly sacrificed a lot of money and time over the past 10 years. And you certainly have a huge head start in terms of programming. But the way you want to end this or hand it over has not been well thought out.
I have been using TTNmapper for two years. During that time, I have not seen any indication that TTNmapper is owned by a private individual.
And before any questions arise, I have been a member of the forum since December 15, 2025. There was no reason for me to register on the forum beforehand.
How could anyone know that TTNmapper is a one-person project?
What would actually help to estimate the scale of the project. You could also mention the amount you last invested per month, but to be honest, that is only of secondary importance to me. For me, the technical factors are more important.
- Traffic
- Size of your database to date (10 years or even just 1 year)
- Measurement points per hour/day
There is a need for continuation. Regardless of whether your project continues or something new comes along.
And no matter who starts something here, they know that you have a 10-year head start.
Sorry, but that has nothing to do with a community.
1 Like
Er, no, as recently as the post directly before yours @jpmeijers said:
In a slightly different version of
“I’ll offer free hosting” is not a solution
many of the well meant but off the cuff offers here are self-eliminating because by carefully reading the thread and looking in detail at GitHub and bringing up the developer tools in your browser to see what is going on and using the back of an envelope to do some basic maths, there are many answers to many questions. And once you’ve got an idea of what might be needed, if you aren’t constructing a business plan, then you are potentially doomed to repeat a similar experience or you have deep pockets.
But, and I must confess I didn’t get the point until a few days ago, the question, the only real question is “is it time to shut down TTN Mapper?”
And the context is that gateways are cheap enough that we can provide our own coverage now and so mapping is not as useful as it once was.
If it’s not time to shut it down, then why not? What do you use it for and what will it mean to you if there isn’t general access to such information?
Given the slightly defensive tone at times towards people who seem keen to look at taking this on, I am not sure how productive this thread is becoming.
On the one hand, this started out as a simple check on demand for TTN Mapper, yes or no, and that feels largely answered. What seems a little odd is questioning people’s reasons for using it. If someone says it is important to them, that is probably best taken at face value.
It also appears that the thread is now being used to gauge who might be willing to take on the role of owner, maintainer, and bill payer. That is understandable, but it would help if that was made a bit clearer.
For anyone genuinely considering stepping in, it would be really helpful to have a clear overview of what sits behind TTN Mapper. A straightforward backend diagram showing the services and hardware currently used, along with an outline of the monthly running costs, would give people a realistic sense of the scale involved. If the thread is also being used to help assess who might be considered worthy of taking on stewardship, then having that information available feels entirely reasonable.
Finally, it is worth remembering that most people here are technical. People will hit hurdles, just as the original authors did, but they will learn and find solutions. It is 2026, and the world has moved on quite a bit in the last twelve years — a solution today may well look very different to that from a decade ago.
I’ll be honest, I have seen a number of people more than capable and just as keen to take it on, but if there are things we are not seeing, then I say just close it down — let another solution rise from the ashes.
4 Likes
Not by the OP who has requested if TTN Mapper is still needed. As I and @kersing have highlighted in the last couple of days per feedback to us from @jpmeijers and his direct statement in post 87
I am as guilty as the rest in thinking it was originally a polite plea for someone to take over. At this time it is not, particularly if it transpires that it’s not needed anymore, making offers moot.
If you do want to make an offer to assist or take on the whole project, there is enough in this thread & on the external resources to come up with an initial business plan which is about as far as JP has gone in mentioning anything like this in #87. Something concrete, not “I’ve a spare server”.
Anyone wishing to assist or contribute would have to know what the market demand is, so the original question is rather salient. No point investing in something that isn’t going to flourish.
My view from here in western Canada is that TTN Mapper has been and continues to be an invaluable resource. Here is this area we don’t enjoy the extensive coverage that others have. I use it daily to evangelize the adoption of TTN.
Thank-you to all who have contributed to it.
6 Likes
Thanks a lot for this kind and very useful feedback @BombayBill!
1 Like
Thanks to provide the service for so many years!
I am an active user of your platform and would be sad if things close. But big thanks to you for supporting the platform!
I can provide few $$ to run it more!
1 Like
Duluth, MN area here. Still figuring out the dead spots with the interesting geography and using ttn mapper to deploy a hotspot North of Cloquet and try to figure out if it will be able to reach any other hotspots, as its 10 miles from the closest one.
i’m really new at it, but is it an option to use Firebase as the server so you don’t have to carry about hardware and energy costs? I’m unsing TTN Mapper for the first time now but I like ist, it helped me to figure out that I don’t have to place an additional Gateway. Is a pop-up with a direct link to your Patreon an option?
just donated $10 to keep it running…
2 Likes
Hi, new user here - can’t post my own topic yet 
But it DOES concern the TTNMapper. I first heard about LoraWAN through a FLAT EARTHER (sorry!) posting about the world record 1336 km record from Portugal to the Canary islands.
I understand tropospheric ducting, and am aware that it is particularly strong and frequent along that corridor. That’s all fine and dandy.
What I am curious about now is that I can see beams in the TTNMapper that are much longer than that 1336 km, but for some reason, aren’t considered a new world record. For example, in the “things-virtual-balloon” experiment, there are a handful of packets between the Netherlands and a receiver in Seattle, WA.
Can anyone explain these records in the TTN Mapper? Are they errors?
I’m happy to throw $100 AUD as a donation to keep it running as well .. it’s a very cool resource.
1 Like
These “ultra-long-range” signals in TTNMapper are not actual, confirmed LoRaWAN connections, but artifacts.The reasons are usually as follows: geolocation error (incorrect gateway or device coordinates) virtual/test devices (such as things-virtual-balloon),packets that passed through the internet backend rather than over the radio,possible errors in data/logging.
Man i would not want to lose your service!
Yeah!
My rak signal meter sometimes sends a 0/0 cooridonates (ocean by africa)that ttn accepts as valid. As the odds of someone actually being there are low, maybe it can be rejected as not valid