Density.io Outage History

The outage is now resolved.

This incident has been resolved. The majority of historical data from January 23–27 was backfilled by the evening of January 28. We are continuing to run quality checks to ensure data accuracy. If you have any questions or concerns, please contact your account manager or reach out to [email protected].

On October 20, 2025, AWS’s US-East-1 region experienced a major outage starting around 07:00 UTC, with full recovery confirmed by 17:00 UTC. Our infrastructure runs on AWS, so we saw temporary API connection timeouts and latency, which may have affected the Space App and Atlas. Our live data pipeline was never disrupted. While some device data was delayed during the incident, no data was lost. Systems have now fully recovered, and all services are operating normally.

Today at 2:30–3:30 a.m. and 7:50-8:30 a.m. PST v2 APIs experienced a temporary 404 error due to a backend issue. The following APIs were impacted: public-api -> /v2/sensors/events public-api -> /v2/spaces/counts public-api -> /v2/spaces/events oa-api => /v2/presence/status No data was lost during this time. The issue has been identified and resolved.

We experienced an outage on the public API service between 23:14 UTC on August 15 and 00:30 UTC on August 16 due to an out-of-memory condition, which resulted in a degraded state of the service. The impact was limited to API availability, no customer data was lost. You may need to retry to access the results from this time period. This was a shared service issue, meaning any customer accessing the API during the incident could have been impacted. As a next step, we will work on: Improving scaling strategy to better handle spikes. Adding profiling to better understand memory usage across the different APIs. Improving Traefik routing so that during degraded states it returns 503 Service Unavailable instead of 404 Resource Not Found.

From June 16 at 6:00 a.m. through June 18 at 10 a.m., our offline status experienced backend pipeline delays. This resulted in incorrect offline emails sending out to impacted customers. If you have received offline sensor emails between June 16-18, please check Atlas > Settings > Sensors to see if they are back online before you begin troubleshooting. If you have any questions about your sensor status and bringing sensors online, please reach out at [email protected].