Northbeam Outage History

Northbeam is up right now

Northbeam had 7 outages in the last 2 years totaling 562h 5m of downtime — averaging 0.3 incidents per month.

There were 7 Northbeam outages since April 15, 2026 totaling 562h 5m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://northbeam.status.io

Minor June 14, 2026

Pixel Data Collection Disruption - Legacy Infrastructure Outage

Detected by Pingoru
Jun 14, 2026, 07:22 AM UTC
Resolved
Jun 14, 2026, 06:46 PM UTC
Duration
11h 23m
Affected: Data collectionData collection (Primary Data Center)
Timeline · 1 update
  1. monitoring Jun 14, 2026, 07:22 AM UTC

    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.

Read the full incident report →

Major June 10, 2026

Meta Ads API Disruption

Detected by Pingoru
Jun 10, 2026, 10:30 PM UTC
Resolved
Jun 11, 2026, 01:37 PM UTC
Duration
15h 6m
Affected: DashboardData processingData collectionData collection (Primary Data Center)TikTokMetaPinterestGoogleMicrosoftShopifyAmazonOrders APIOrders API (API)MNTNX (Twitter)SnapSnap (External data integrations)
Timeline · 1 update
  1. identified Jun 10, 2026, 10:30 PM UTC

    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.

Read the full incident report →

Minor May 20, 2026

Issue with tracking visits

Detected by Pingoru
May 20, 2026, 03:17 PM UTC
Resolved
May 22, 2026, 03:46 AM UTC
Duration
1d 12h
Affected: Data collectionData collection (Primary Data Center)
Timeline · 5 updates
  1. identified May 20, 2026, 03:17 PM UTC

    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.

  2. identified May 20, 2026, 04:02 PM UTC

    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.

  3. identified May 20, 2026, 08:43 PM UTC

    We are continuing to assess the impact of the regression. We will update when we have more information.

  4. identified May 20, 2026, 11:08 PM UTC

    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.

  5. identified May 21, 2026, 06:03 PM UTC

    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.

Read the full incident report →

Minor May 18, 2026

Snap Ads Reporting Delay

Detected by Pingoru
May 18, 2026, 11:13 PM UTC
Resolved
May 20, 2026, 03:25 PM UTC
Duration
1d 16h
Affected: SnapSnap (External data integrations)
Timeline · 2 updates
  1. investigating May 18, 2026, 11:13 PM UTC

    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.

  2. monitoring May 18, 2026, 11:21 PM UTC

    We have started to see signs of recovery upstream. We will continue to monitor the issue until the data pipelines are caught up.

Read the full incident report →

Minor May 12, 2026

Delays in Orders API data processing

Detected by Pingoru
May 12, 2026, 03:24 PM UTC
Resolved
May 18, 2026, 10:51 PM UTC
Duration
6d 7h
Affected: Orders APIOrders API (API)
Timeline · 2 updates
  1. investigating May 12, 2026, 03:23 PM UTC

    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.

  2. investigating May 12, 2026, 03:24 PM UTC

    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.

Read the full incident report →

Minor April 15, 2026

X Ads Reporting Issues

Detected by Pingoru
Apr 15, 2026, 05:40 PM UTC
Resolved
Apr 28, 2026, 01:09 PM UTC
Duration
12d 19h
Affected: X (Twitter)X (Twitter) (External data integrations)
Timeline · 1 update
  1. identified Apr 15, 2026, 05:40 PM UTC

    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.

Read the full incident report →