hi
in gateway side everything is working fine but i can not see my packets in application-data part.
is this a problem of mine or a general problem?
I see application traffic for my devices so suspect it’s your end… is node joined and transmitting ok, do you see activity in your gw log and traffic page etc.
it is working now,
i was not able to see packets on application part for about one hour but now it is ok,
thank you.
Looking deeper it depends on when you were checking - there was significant outage of V2 earlier which was recovered but then seemed to go into decline again
1 Like
yes i had difficulty exactly in the mentioned period
Things are up and down and up and down and up and down at present.
Rinse, repeat.
Etc
Nice day for a walk …
might be worth you bookmarking: https://status.thethings.network/ often doesnt show minor wrinkles but such outage usually pops up or is visible if you keep an eye on the graphs. also subscribe to the ttn slack ops channel…
1 Like
been there done that, phographed the bluebells, drank the coffee…nose now back on grindstone! 
Indeed.
I see at the status page that the incident in NOC is reported as “unreliable information”. Actually the entry point is unreachable since it times out.
I’ve read the thread and we also monitor our community gateways using NOC. @htdvisser: I’m upset when I read that it is not a “critical” component. It is for a lot of people. We might be enrolled in non-monetizing projects we still have the commitment to keep the gateways online and this makes us effectively blind to issues on the gateways.
Overall, The Things Network / The Things Industries is losing credibility with this rough transition to v3. I completely agree with @Jeff-UK post above. v2 breaking often, the lack of a well defined migration procedure and timing, information missing on the packet broker,… these won’t help us move faster to v3. For some people quite the opposite.
Back into now: I’m missing information on the status page about when you estimate NOC will be available again.
2 Likes
@htdvisser Will the NOC API be back or has this been permanently retired? - eg http://noc.thethingsnetwork.org:8085/api/v2/gateways/eui-00800000a000284e
No, we are not working on getting http://noc.thethingsnetwork.org:8085/api/v2 back online.
This endpoint is not part of our official API, and was never actually intended to be exposed/used publicly (otherwise we would have enabled https and documented it). Therefore we’re also not going to spend our time on getting it back online.
It is for me and a lot of other users a tool to measure if a gateway is online, now with V2 still operational and a lottt of users still havin gateways and devices running on v2 the NOC is a tool that can be missed.
Please give it a little effort to bring it back, and if v2 shuts down, send it off to the bin 
When.
As you do Node-Red, why not script something that looks at uplinks and checks for your gateway id’s.
IMO this is SEVERELY PROBLEMATIC to not fix V2 since many of us are using TTIG-915 gateways which AFAIK are STILL NOT SUPPORTED ON V3
So WTF are we supposed to do when we have issues? I have nearly 20 TTIG915 gateways deployed?!
Use the gateway console?
If you can politely explain what extra benefit you get from the NOC tool, it may be possible to find an alternative solution as an interim.
One can easily monitor gateway status by querying the gateway-data entrypoint (https://www.thethingsnetwork.org/gateway-data/country/es, for instance) and parse the response. The only thing I’m missing here is the info about received and transmitted packets I had using the NOC. Not a big deal thou.
Or to just get your own data:
https://www.thethingsnetwork.org/gateway-data/gateway/eui-de5ca70000000000
for instance.
As I was alluding to, @dnear1 and anyone else who’s getting agitated about the perfectly normal bit-rot in v2 that they use for free, solutions are out there, please ask nicely.
1 Like
Well you can monitor the gateways in your area, messages pre hour and see when your local community need to add more gateways.
I’ll have a think about how to capture that data in v3 - it should be feasible by having an account setup for the community and adding it as a collaborator in read-only mode - it can then grab the stats. Although getting stats may be public anyway.
In the interim as v2 won’t get any non-critical fixes, you may have to travel hopeful until the migration is complete.