Recieved the gateway today. Thanks for all the work TTN team. Finally a gateway will be available in my region, very happen that i now can start to recieve data from my home build nodes.
And the best timing ever, week of holiday coming up. Will be a busy holiday 
For those who are interested, @jpmeijers setup a twitter bot where you can see all the gw activations real time.
@ttn_gateways
Nice!
Note that “Powered by TTN Mapper” might imply that new gateways will only show if someone is mapping coverage around that gateway using TTN Mapper?
Like https://ttnmapper.org vs https://www.thethingsnetwork.org/map for Haarlem, where no mapping was done after the gateway in the south-east was added recently:
So, go mapping already! 
(Please correct me if I’m wrong, @jpmeijers, like maybe the Twitter feed is using http://noc.thethingsnetwork.org:8085/api/v2/gateways instead of relying on mapping?)
Maybe not from the mapper data. If you observe a new gateway it is listed as “Likely a Single Channel Gateway.” because of something similar to this: “Channels heard on: 2” which is obviously a result of it’s newness.
Anyway, whip out those mapper nodes and start moving! Go outside the house
…and, to me, indicates it is using mapper data. But you got that from the pins on the https://ttnmapper.org website, right? The Twitter feed might use something different. (The few gateways from the Twitter feed I checked were all also shown on the TTN Mapper maps, but of course @jpmeijers can easily tell us so I only checked a few. 
)
Ah, the one from the latest tweet, https://twitter.com/ttn_gateways/status/957206651840487424 is not shown on TTN Mapper, so I might be wrong! (But then, I don’t know if TTN Mapper is realtime? So many questions! 
)
The things is, a gw only pops up on the map after it has been mapped by a node it seems, while the twitter feed also shows a gw that is not on the mapper yet (after all, how?).
For instance this one:
I’m currently at work really close to it so I will go map it after an hour or so. It is not yet on the mapper so it will be fun to see it appear.
Similar goes for b827ebfffe8b0a59 near here which I mapped because I can actually receive it inside this building.
Great fun.
The Twitter bot shows all newly activated gateways that have a public location configured on the console. Not only mapped ones.
But it is anyway a good idea to go out and map your gateway!
Yes… but have these gateways been able to connect to the network? Or are DOA gateways, which users have registered but which are not yet able to connect, also shown?
I checked: http://noc.thethingsnetwork.org:8085/api/v2/gateways only lists gateways with rx_ok (correctly received packets) > 0. So they must be able to connect to the network.
Yes exactly. They must have communicated with the network to show up on the NOC and consequently on the Twitter feed.
Hi, @arjanvanb, actually my 2nd gateway that I ordered thru the webshop was delivered yesterday with NO extra payment due (yet). Whereas the 1st gateway I ordered as part of the Kickstarter has already cost me an extra 80 euro in custom duties and after being in transit for over a month is STILL stuck in Poland (shipping is by Skynet) 
Yesterday our Kickstarter order arrived 
A few gateways, nodes and uno’s, so we will be busy.
It took a ‘little’ longer that expected 
but activating the first gateways went smooth.
Only ‘disappointment’ with the Kickstarter campaign is that we had to pay an additional 21+% to receive our shipment 
I rather had spend it on getting more devices, etc.
If that’s the Dutch The Things Products webshop, then I assume you’ve already paid Dutch VAT when ordering?
Since last Friday the status of my order is according to the Smooth Parcel website
Address query
The address provided with your parcel is not correct, click here for more info (link)
The retailer is Whistl and when I check the delivery status it is still in transit with the latest update
Item Processed by Carrier - Weight Captured
Should I take any action to have my address verified or should I just wait?
2050 Gateways listed in Europe late friday
2207 Today (sunday)
can you give us any details with regards to firmware versions etc? in hope to track down issue of DOA gatways
I listed my entire boot log in the other topic… but here goes:
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 917719b9, timestamp: 1498499973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jun 26 2017 19:59:53
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 86 D0 0E 90 F5 21 02 9D 41 60
thanks, but for those of us that don’t have a FDTI? what is displayed on the /info page?
This:
Version Info
Hardware: v1
Bootloader: r1-7167873a (2017-06-02T13:48:18Z)
Firmware: v1.0.0-917719b9 (2017-06-26T17:59:33Z)