Hello I noticed that https://data.sensor.community/airrohr/v1/sensor/{sensorId} returns empty list since 1 AM today.
Checking my device status I also noticed errors sending to API.
1 Like
Yes, might be they are under some kind of DoS attack.
The madavi API is still reachable although there are some drops in the graph:
I also noticed that the total number of sensors worldwide on the map has dropped to exactly 1173, from over 13.000 before. The sensors that are not on the map anymore are also not reachable through their API number, and an empty JSON list is produced () if you try reading them.
Also the number of 1173 total sensors seems “fixed”. It did’t change for over 24 hours…
The problem started Sat. 15/3 at +/- 1 AM, when suddenly all data from 26 sensors on my display in test disappeared.
Potentially over 12,000 sensors are affected by this issue, and are no longer reachable via the API, or no longer visible on the map.
@pjg @ricki-z Please acknowledge you’ve seen this network-wide problem ?
same fault in italy. exactly the same… only 1173 world wide fixed visible sensors. All my local sensors unable to reach the servers with api call… replay INTERNAL SERVER ERROR.
opensensemap.org instead is woking at the moment. same sensors are uploading data and still visible
Since saturday morning (or since 1 day 13 hours) the database server api.sensor.community is migrated to a new hardware node. We are waiting for the virtual server do be online again …
3 Likes
It looks like something is wrong with the data transmission. The gray dots are the stations that turned off during the night.
@ricky: Is there an explanation why the database server migration which “turned bad” allows the correct working of the fixed quantity of 1173 sensors ? Why are these 1173 working, while the others aren’t ? What is the difference ? Even now, exactly 1173 sensors, and only those, are working, and the +12.000 others aren’t.
The explanation is simple: they don’t.
Just click on one of these sensors mistakenly shown as active and you will see they also weren’t updated since 2025-03-15 01:15:00.
Note the Last update timestamp. The map shows the data at that time. No updates after that due to the database not being available.
This was the last data file the server wrote.
I’ve reset all the data files for the map. They shouldn’t show now any sensors.
I just looked and it’s still down
Any idea how long this outage will last?
besides the map which is not working,
whoever used aqicn and its widgets is off and grayed…
our sensors try to send to sensor.community but they timeout…
some kinda of toys, clocks, etc who change color reading sensor data from sensor.community of course they don’t work…
i am a member of this community the last 3 months, we had 2-3 outages, but never a such lengthy…
i’m also a sysadmin, and if i could help somehow, please ask me.
we are uptime-nerds, and this downtime is killing me… 
2 Likes
It’s true you’re typing here. It’s frustrating. This system is falling down more often than you written off. API It’s down 5 times per month, I’m trying to build my own webserver to receive API data from the sensor, because this is not stable
its not frustrated. its a free service, and sh*t happens.
i usually change servers in a couple of hours, so i believe its more serious than we think…
we just have to wait.
i made my own api, but i have only my 20 sensors 
be patient…
1 Like
It’s a free service provided and maintained by volunteers in their spare time, so think twice before complaining.
Despite this your can configure additional public endpoints in the API settings of your sensor so you will always have access to your data.
At least my sensor from Nettigo has native support for madavi, aqi.eco and OpenSenseMap:
Yes correct I understand. 
no blame just reaction.
2 Likes
Hi
I can see my sensor data on Grafana site, how is that possible if sensor.community is not working? Is it sending it via firmware externally or? Is there some other site that uses Grafana data that is more simple to use?