Northbeam had 13 outages in the last 2 years totaling 725h 16m of downtime — averaging 0.5 incidents per month.
There were 13 Northbeam outages since April 15, 2026 totaling 725h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are aware of an issue affecting the creation of new exports from the Sales page. Attempts to create a new export from this page may fail. The following remain operational: Data Export API, Running existing export reports, Touchpoint export creation. We will provide another update as more information becomes available.
Google Cloud Platform (GCP) is currently experiencing an outage impacting Northbeam. As a result, dashboards may fail to load and data processing is delayed. Data collection is not impacted, and no data is being lost. Some data may take additional time to catch up once service is restored. We’re actively monitoring the outage and will share updates as they become available.
Northbeam dashboards are now back online and should be accessible. Data processing is still delayed due to the ongoing GCP outage. Data collection remains unaffected, and no data is being lost. Some data may take additional time to catch up as services recover. We’ll continue monitoring and share another update as processing returns to normal.
We are aware of an issue affecting AppLovin reporting. Some customers may see duplicate campaigns and duplicated spend in Northbeam due to upstream issues with AppLovin’s Reporting API . The issue appears to have started around August 16, 2026 at 03:00 UTC. We are working with AppLovin and will provide another update when more information is available.
The upstream issue with Applovin Reporting API has been resolved and Northbeam is now re-processing Applovin data for the last few days. We anticipate the issue to be fixed for all impacted customers in the next 3-4 hours.
Pixel data collection is disrupted due to networking infrastructure failures with our hosting providers. We are actively working on mitigation.
We are actively investigating mitigation steps for the pixel data collection disruption caused by networking infrastructure failures with our hosting providers. We will share another update as soon as we have more information.
We continue to actively investigate mitigation steps for the pixel data collection disruption caused by networking infrastructure failures with our hosting providers. We will share another update as soon as we have more information.
Pixel data collection is recovered from disruption caused by networking infrastructure failures with our hosting providers. We are continuing to monitor the health of the system closely.
We experienced a partial pixel data collection outage between 7:00pm PT on July 4 to 4:40 PT on July 5. Pixel data collection recovered around 4:40pm PT on July 5. For the impacted window, affected customers may see missing order and revenue in channel-level attribution reporting. However, total order and revenue was still captured in the Orders page, and top-line store-level performance remains properly represented. We are continuing to monitor the situation and assess the impact for affected accounts.
Pixel data is operating normally as of July 05, 16:35 pacific time. We continue to monitor the situation.
We are addressing delays in pixel data processing that began around 7:45a PT. During this time, some customers may see delays in data reporting for attributed metrics. We have isolated the issue to a processing backlog in part of our ingestion pipeline, and our engineering team is actively working to restore normal throughput. We will continue to share updates as progress is made.
Northbeam pixel data is delayed by approximately two hours.
We are aware of an upstream issue affecting the Vibe Ads integration that is causing gaps in Vibe Ads data in Northbeam. The upstream impact started on Thursday, Jun 25th 2026. As a result, customers with a Vibe integration may see delayed or inaccurate ad spend and performance metrics in their dashboards. Our engineering team is actively monitoring the issue. We will share another update as soon as we have more information or a recovery path.
We have started to see signs of recovery upstream. We will continue to monitor the issue until the data pipelines are caught up.
A network outage at a legacy infrastructure provider caused a disruption in pixel data collection from 7:25pm to 11:04pm PDT. Data collection has resumed. This incident affected customers still on our legacy infrastructure. During the disruption window, those customers experienced a loss of visit and event data. Because pixel events are sent from the visitor’s browser in real time, events that failed to deliver during this period cannot be recovered. Affected customers will see a gap in visits, pageviews, and attributed revenue for this window. The legacy third-party provider has recovered, and we are actively monitoring the situation. Migration off this legacy infrastructure has been underway for existing customers, and we will continue working directly with the remaining customers to complete that migration. We will also reach out to affected customers directly.
We are observing degraded performance and intermittent failures on Meta's side when attempting to fetch data from the Meta Ads API. We started observing these issues around 2026-06-10 5:45 PM ET. As a result, you may experience delays or inaccuracies in Facebook Ads performance metrics. Our engineering team is actively monitoring Meta’s API status. We will provide updates as soon as we have more information or a resolution path.
We are aware of an issue affecting multiple customers that may result in missing visits in dashboards starting Tuesday, May 19 at around 21:00 UTC. Impacted customers will also see revenue reported as unattributed since that time. Our team is actively working to identify the root cause and restore normal reporting. We will share another update as soon as we have more information.
We have reverted the change that caused this regression and believe the issue is resolved for customers as of May 20th, 15:04 UTC(11:04 ET). We are still working to determine the impact during the time the issue was present, including effect on visits and revenue attribution. Thank you for your patience while we are working through this.
We are continuing to assess the impact of the regression. We will update when we have more information.
Our team is actively working to restore the affected data for all impacted customers for the incident duration, from approximately May 19 at 21:00 UTC (5:00 PM ET) through May 20 at 15:00 UTC (11:00 AM ET). We will share another update once the restore and data processing are complete. No data has been lost.
Our team is continuing to restore affected data for impacted customers. Recovery is now over halfway complete. We expect the remaining backfill to continue through the day and complete by end of day today, May 21 (ET). We will share another update as progress continues. We can confirm that no data has been lost.
We are aware of an upstream issue affecting the Snap Ads integration that is causing gaps in Snap Ads data in Northbeam. The upstream impact appears to have started about 8:00 p.m on Monday, May 18, 2026 UTC. As a result, customers with a Snap integration may see delayed or inaccurate ad spend and performance metrics in their dashboards. Our engineering team is actively monitoring the issue. We will share another update as soon as we have more information or a recovery path.
We have started to see signs of recovery upstream. We will continue to monitor the issue until the data pipelines are caught up.
We’re currently experiencing a delay in processing order data for customers sending data to our Orders API. At the moment, affected data processing is running about 18 hours behind expected timing. Our team is actively investigating the issue and working to restore normal processing as quickly as possible. We’ll share another update as soon as we have more information or meaningful progress to report.
We’re currently experiencing a delay in processing order data for customers sending data to our Orders API. At the moment, affected data processing is running about 18 hours behind expected timing. Our team is actively investigating the issue and working to restore normal processing as quickly as possible. We’ll share another update as soon as we have more information or meaningful progress to report.
We are aware of an upstream issue affecting the X Ads integration that is causing gaps in X/Twitter Ads data in Northbeam. The upstream impact with X's API appears to have started on or around March 27th, 2026. As a result, customers with an X integration may see delayed or inaccurate X Ads spend and performance metrics in their dashboards. Our engineering team is actively monitoring the issue. We will share another update as soon as we have more information or a recovery path.