Jul <var data-var='date'> 7</var>, <var data-var='time'>15:27</var> EDT Monitoring - The fix for the Open Area pipeline has been implemented. Data is expected to catch up throughout the day. An update will be provided on the morning of July 8 regarding the final resolution. Jul <var data-var='date'> 7</var>, <var data-var='time'>11:59</var> EDT Identified - On July 6 at 11 a.m. EST, OA tracks stopped populating in the historical pipeline. There will be no historical Open Area data available through the API/Atlas from that time until the issue is resolved. The cause of the problem has been identified, and a fix is currently underway. There is no expectation of data loss.

Open Area Historical Pipeline Outage

Jun <var data-var='date'>26</var>, <var data-var='time'>00:15</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>25</var>, <var data-var='time'>23:45</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>23</var>, <var data-var='time'>16:27</var> EDT Scheduled - Density has scheduled maintenance on June 25, from 11:59 p.m. - 12:30 a.m. ET to make changes to our backend systems. We expect minimal downtime while backend applications restart. During any downtime, your Entry sensor's data will remain intact. Entry sensors store count data locally and send time-stamped data back to the platform as soon as the platform comes back online. We do not anticipate a significant impact to any Open Area or Waffle data during the short timeframe our services may be offline.

June 25 Scheduled Maintenance

Jun <var data-var='date'>19</var>, <var data-var='time'>00:15</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>18</var>, <var data-var='time'>23:45</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'>17</var>, <var data-var='time'>12:37</var> EDT Scheduled - Density has scheduled maintenance on June 18, from 11:59 p.m. - 12:30 a.m. ET to make changes to our backend systems. We expect minimal downtime while backend applications restart. During any downtime, your Entry sensor's data will remain intact. Entry sensors store count data locally and send time-stamped data back to the platform as soon as the platform comes back online. We do not anticipate a significant impact to any Open Area or Waffle data during the short timeframe our services may be offline.

June 18 Scheduled Maintenance

Mar <var data-var='date'>23</var>, <var data-var='time'>16:06</var> EDT Resolved - The outage is now resolved. Mar <var data-var='date'>23</var>, <var data-var='time'>14:47</var> EDT Monitoring - A fix has been implemented, and services are restored. You may notice a slight lag as operations return to normal. No data was lost in this incident. Mar <var data-var='date'>23</var>, <var data-var='time'>11:08</var> EDT Identified - The issue has been identified, and the fix is being implemented now. Mar <var data-var='date'>23</var>, <var data-var='time'>10:36</var> EDT Investigating - We are currently investigating an issue affecting Atlas, Displays, APIs, and Websockets/Webhooks. You may experience longer load times or error messages. We will continue to update as we identify the cause.

All Density Services Degraded

Jan <var data-var='date'>29</var>, <var data-var='time'>08:00</var> EST 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 support@density.io. Jan <var data-var='date'>27</var>, <var data-var='time'>17:01</var> EST Monitoring - The outages have been resolved, and we are now processing the remaining data backlog. Live data, APIs, and the setup apps are operating normally. Historical data from January 23–27 will populate as the backlog clears. No data has been lost. Jan <var data-var='date'>27</var>, <var data-var='time'>11:36</var> EST Update - Our engineering team continues to make progress toward a resolution. The outages are intermittent and typically last 2–4 minutes. If you encounter an error, please wait a few minutes and refresh the page. Data access via Atlas, apps, and the API should resume after refresh. Displays may show delayed data. Jan <var data-var='date'>26</var>, <var data-var='time'>12:22</var> EST Update - Density is continuing to work on a fix for this issue. Outages remain intermittent, with improvements in uptime over the weekend. No data is expected to be lost. Outages continue to affect our APIs, Atlas, apps, and displays. Jan <var data-var='date'>23</var>, <var data-var='time'>14:50</var> EST Identified - We are currently experiencing intermittent outages affecting all Density APIs. As a result, Atlas and all display types may fail to load. No data will be lost. The issue has been identified, and our team is actively working to restore full service.

Intermittent Outages to Density APIs

Oct <var data-var='date'>20</var>, <var data-var='time'>05:00</var> EDT Resolved - 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.

AWS Outage Impact on Density

Oct <var data-var='date'>10</var>, <var data-var='time'>12:26</var> EDT Resolved - 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.

V2 API 404 Errors

Aug <var data-var='date'>15</var>, <var data-var='time'>21:00</var> EDT 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.

Density APIs Offline

Jun <var data-var='date'>16</var>, <var data-var='time'>08:00</var> EDT Resolved - 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 support@density.io.

Sensor Health Showed Incorrect Status

May <var data-var='date'> 5</var>, <var data-var='time'>13:07</var> EDT Resolved - This issue has been resolved. No data was lost during the Atlas Building Analytics outage. May <var data-var='date'> 5</var>, <var data-var='time'>12:50</var> EDT Identified - Atlas Building Analytics page is down. We have found the cause of the issue and are working to resolve the issue.

Atlas Building Analytics Down

Sep <var data-var='date'>18</var>, <var data-var='time'>09:38</var> EDT Resolved - The process to remove duplicate events has been completed. Events have been corrected for September 14 at 10:15 a.m. to September 16 at 11:25 a.m. EST. Sep <var data-var='date'>17</var>, <var data-var='time'>16:32</var> EDT Update - The next round of data corrections from multiple Entry sensors will run on September 18 at 4 a.m. EST to avoid conflicting with peak hours. Sep <var data-var='date'>17</var>, <var data-var='time'>10:40</var> EDT Update - We are continuing to work on a fix for duplicate event removal. Sep <var data-var='date'>16</var>, <var data-var='time'>15:59</var> EDT Update - The process to correct count duplications between multiple sensors over a single doorway is expected to run overnight (EST). We will provide more information on resolution timing tomorrow, September 17th. Sep <var data-var='date'>16</var>, <var data-var='time'>12:24</var> EDT Identified - A data pipeline delay from doorways with multiple Entry sensors (s5b and ELR) occurred from September 14 at 10:15 a.m. to September 16 at 11:25 a.m. EST. The data is processing but will come in two rounds. First, you will see inflated counts due to duplicates from multiple sensors, and then the process to remove duplicates will be run. We recommend not using historical data from September 14-16 until this is resolved. Live data (Safe Displays) counts will be impacted by the missing and duplicated data.

Multi-Sensor Doorways Data Delay

Jul <var data-var='date'>31</var>, <var data-var='time'>02:00</var> EDT Resolved - We experienced an AWS IoT connection outage today from 12:05 a.m. to 11:05 a.m. EST. During this time period, our Live displays for affected spaces would have shown the space as grey. These devices would be reported as unhealthy via our public API. The issue is resolved.

Live Outage

Jul <var data-var='date'>30</var>, <var data-var='time'>16:01</var> EDT Resolved - The intermittent outages with Density applications have been resolved. We saw brief outages between 9:43- 9:44 a.m. and from 10:00 -10:05 a.m. EST. The root cause has been identified, and a fix has been deployed. No data was lost during this time, but APIs may have returned a 404 error and need to be rerun. Jul <var data-var='date'>30</var>, <var data-var='time'>10:15</var> EDT Investigating - We are experiencing intermittent outages with our backend systems starting at 9:43 a.m. EST. This outage impacts Atlas and all APIs, but no data will be lost.

Intermittent Outages with Atlas and APIs

Jul <var data-var='date'>24</var>, <var data-var='time'>14:00</var> EDT Resolved - From 12 p.m. EST on June 24 - 11 a.m. EST on June 25, v2 experienced intermittent 404 errors. This was due to an issue on the backend that has been resolved.

v2 and v3 API Outage

Jun <var data-var='date'>18</var>, <var data-var='time'>12:51</var> EDT Resolved - The API documentation is back online. This did not impact any Density APIs, only the documentation. Jun <var data-var='date'>18</var>, <var data-var='time'>11:55</var> EDT Identified - Our API documentation is currently unavailable. We have discovered an issue with our hosting site for developers.density.io and are working with the partner to resolve it.

API Documentation Down

May <var data-var='date'>17</var>, <var data-var='time'>16:40</var> EDT Resolved - This incident has been resolved. If your organization was impacted by our OA historical data downtime, you will receive an individual email with the next steps for API backfills. May <var data-var='date'> 9</var>, <var data-var='time'>15:42</var> EDT Update - We are continuing to work on a fix for this issue. Apr <var data-var='date'>22</var>, <var data-var='time'>11:19</var> EDT Identified - A number of Open Area sensors stopped uploading count data beginning April 22, 2024. To prevent data loss, all sensors began storing count data in backup local storage. We are actively working to fix the upload issue and expect to have historical data fully restored. There was no impact to live or Entry Density data at any point.

Open Area Data Delay

Apr <var data-var='date'>25</var>, <var data-var='time'>12:13</var> EDT Resolved - This incident has been resolved. If you use the API to feed a data lake or other record of Open Area count data, you will need to backfill the data from April 24th if it was pulled on April 25th. Please email support@density.io if you need any assistance with this. Apr <var data-var='date'>24</var>, <var data-var='time'>13:33</var> EDT Identified - There is a backlog in our historical OA pipeline causing a delay in OA data in Atlas and the API. We are implementing a fix, and no data will be lost. Entry data is not impacted.

Open Area Historical Data Delay

Feb <var data-var='date'> 5</var>, <var data-var='time'>04:00</var> EST Resolved - This incident has been resolved. Feb <var data-var='date'> 2</var>, <var data-var='time'>12:43</var> EST Identified - We're having an outage with our hosting site. The team is aware and is working to resolve it.

Maps Hosting Site Outage

Dec <var data-var='date'>20</var>, <var data-var='time'>00:00</var> EST Resolved - From December 12-20, webhooks were unavailable. This issue has now been resolved, and you do not need to do anything to resume receiving data. If you use webhooks to feed a data lake or other record of count data, you will need to backfill data from December 12-20, 2023. We recommend using the API query space events endpoint. If you need help downloading a CSV from the time frame, please let us know, and we can provide instructions.

Webhooks Outage

Dec <var data-var='date'>12</var>, <var data-var='time'>17:17</var> EST Resolved - When we cut over the live Entry data to our improved count database, the system ran into unexpected errors. This caused a backup in Entry count, which resulted in incorrect live count for about 20% of spaces. This issue was resolved at 4:30 p.m. EST. The only impact to historical data and APIs was a slight delay in arrival, resolved at 3:45 p.m. EST. There is no incorrect data populating in either location. The legacy Dashboard had a bug with timestamps. If you use the legacy platform for building-level data, this is now available. v2 APIs had a bug with representing timestamps on the response. If you ran into timestamp parsing errors on your end, you may have to re-pull data. Dec <var data-var='date'>12</var>, <var data-var='time'>11:34</var> EST Update - The Entry count backlog is currently clearing from the earlier outage. Until this is resolved, live data in Displays will be incorrect, and you may experience jumps in numbers. All v2 and v3 APIs are operating normally. If you use APIs to feed a data lake or other record of count data, and received API errors between 4-4:30 a.m. or 7-9 a.m., you will need to backfill your data. Not all customers received error messages, please check your API instance. Dec <var data-var='date'>12</var>, <var data-var='time'>09:58</var> EST Identified - Density performed scheduled maintenance this morning at 3 a.m. EST for v2 API changes and fixes to Entry Live (displays). -Between 4-4:30 a.m. EST there was a full outage across the platform due to the v2 cutover. This was resolved at 4:30 a.m. EST. -Between 7-9 a.m. EST a limited number of customers may have experienced v2 API errors. This was resolved at 9 a.m. EST. -At 5:30 a.m. EST, we began to experience issues with Entry data, related to the fixes for Entry Live. This is ongoing; updates to follow. Dec <var data-var='date'>12</var>, <var data-var='time'>09:28</var> EST Investigating - We are currently investigating a large number of errors in Entry data.

Entry Live Errors

Dec <var data-var='date'> 6</var>, <var data-var='time'>13:18</var> EST Resolved - We faced an hour-long outage for our Entry count data into Atlas and APIs due to an AWS issue. This has been resolved. If you use our v3 API to feed a data lake or other record of count data, you will need to backfill data from 12:09-1:04 EST. We recommend refreshing the data for that time frame using the same endpoints. Dec <var data-var='date'> 6</var>, <var data-var='time'>12:00</var> EST Investigating - Our Entry counts API is down, which is impacting Atlas and APIs. We will update as we uncover the cause.

Entry Counts Outage

Nov <var data-var='date'>20</var>, <var data-var='time'>10:18</var> EST Resolved - From November 14-20, webhooks were unavailable. This issue was resolved on November 20 at 5 a.m. EST. You do not need to do anything to resume receiving data. We have also put monitoring in place to prevent this from happening again. If you use webhooks to feed a data lake or other record of count data, you will need to backfill data from November 14-20. We recommend using the API query space events endpoint. If you need help downloading a CSV from the time frame, please let us know, and we can provide instructions. Nov <var data-var='date'>14</var>, <var data-var='time'>00:00</var> EST Identified - We have identified a backlog in our webhooks, which is in the process of being cleared.

Webhooks Backup

Oct <var data-var='date'>14</var>, <var data-var='time'>11:01</var> EDT Resolved - All systems have been restored and are operating normally. Oct <var data-var='date'>12</var>, <var data-var='time'>17:40</var> EDT Identified - Backend systems will be running overnight to restore normal functionality. All Entry data is available, but may experience delays or intermittent issues during this time. Oct <var data-var='date'>12</var>, <var data-var='time'>14:51</var> EDT Investigating - We are currently experiencing downtime with our Entry live availability features, including Displays. There will also be a delay in Entry historical data until the issue is resolved. The cause has been identified, and we are working to resolve the issue.

Live Entry Count Down

Oct <var data-var='date'>12</var>, <var data-var='time'>12:54</var> EDT Resolved - This incident has been resolved. If you use the v2 API to feed a data lake or other record of count data, you will need to backfill the data during this outage. Please let us know if you need any assistance in this. Oct <var data-var='date'>12</var>, <var data-var='time'>10:23</var> EDT Monitoring - The Entry count system is down, impacting Dashboard, Displays and v2 count APIs. A fix has been implemented, and we are monitoring.

Entry Count Pipeline is Down

Sep <var data-var='date'>14</var>, <var data-var='time'>14:18</var> EDT Resolved - This incident has been resolved. Sep <var data-var='date'>14</var>, <var data-var='time'>14:08</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Sep <var data-var='date'>14</var>, <var data-var='time'>13:37</var> EDT Identified - Our database provider is currently experiencing an outage, and our analytics API has been affected. No data has been lost, however, space analytics are currently unavailable. Sep <var data-var='date'>14</var>, <var data-var='time'>12:30</var> EDT Investigating - We are currently investigating this issue.

Is Density down?

Density status is PARTIAL OUTAGE

Components with issues

Lastest published events

Open Area Historical Pipeline Outage

June 25 Scheduled Maintenance

June 18 Scheduled Maintenance

Density Services, Components and Regions

Recent Density events

Open Area Historical Pipeline Outage

June 25 Scheduled Maintenance

June 18 Scheduled Maintenance

All Density Services Degraded

Intermittent Outages to Density APIs

AWS Outage Impact on Density

Get your FREE account now,
5 monitors included!

Is Density down?

Density status is PARTIAL OUTAGE

Components with issues

Lastest published events

Open Area Historical Pipeline Outage

June 25 Scheduled Maintenance

June 18 Scheduled Maintenance

Density Services, Components and Regions

Recent Density events

Open Area Historical Pipeline Outage

June 25 Scheduled Maintenance

June 18 Scheduled Maintenance

All Density Services Degraded

Intermittent Outages to Density APIs

AWS Outage Impact on Density

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!