March 2026 Ad Platform
Reliability Report
12 incidents across Meta, Google Ads, and Microsoft Advertising - with a 6-hour Google Ad Manager outage as the month's biggest disruption.
The Numbers
Source: AdStatus monitoring data for March 1-31, 2026
Key Findings
Google Ad Manager had its worst outage in months
A 6-hour disruption on March 24-25 affected a significant subset of users with error messages, high latency, and unexpected behavior. Google Ads typically maintains 99.9%+ uptime, making this a rare and notable event.
Microsoft Advertising dominated incident counts - but only data delays
All 7 Microsoft incidents were data freshness issues (Share of Voice, Offline Conversions, Reporting). No service outages. This pattern suggests infrastructure strain on reporting pipelines rather than core ad-serving problems.
Meta had 2 disruptions - one short, one still ongoing at month-end
A 1-hour ads delivery outage on March 17 and a medium disruption affecting Ads Creation and Editing that started March 31 and carried into April. Much better than Q4 2025's pattern of multi-day disruptions.
Complete March 2026 Incident Timeline
Share of Voice data delayed
Data freshness impacted between Mar 10 9:15 PM and Mar 11 9:30 PM UTC.
Offline Conversions data delayed
Attribution and optimization impact for advertisers using offline conversion tracking.
Reporting and shopping data delayed
Broader reporting pipeline issue affecting multiple data surfaces.
Ads Delivery outage
Short but severe - ad delivery was fully impacted across the platform before services were restored.
Share of Voice data delayed (again)
Second SOV delay in a week - indicates a recurring reporting pipeline issue.
Offline Conversions data delayed
Second offline conversions delay in March.
Share of Voice data delayed (third time)
Third SOV incident in nine days - clearly a persistent issue with this pipeline.
AdMob data access issue
Users could access AdMob but could not see the most recent data. Precursor to the larger Ad Manager incident.
The month's biggest incident: Google Ad Manager 6-hour outage
A significant subset of users experienced error messages, high latency, and intermittent access. This is a rare event for Google infrastructure and affected publisher revenue during peak US/EU advertising hours.
Offline Conversions data delayed
Third offline conversions incident this month.
Medium disruption: Ads Creation and Editing
Started less than an hour before month-end and carried into April - advertisers reported trouble creating or editing ads in Ads Manager.
Patterns & Takeaways
Microsoft's reporting pipeline needs attention
Three separate Share of Voice delays in nine days (Mar 10, Mar 18, Mar 19), plus multiple offline conversions delays. Data freshness matters for bid optimization and attribution. If you rely on Microsoft reporting, build in a 24-hour buffer for March data.
Google proves nothing is immune
Google is the gold standard for ad platform reliability, but March showed even Google's infrastructure can fail for 6+ hours. Teams relying exclusively on Google should have a monitoring plan - outages are rare but they do happen, and when they happen nobody is expecting them.
Meta continues its improved Q1 trajectory
Only 2 Meta incidents in March, versus the multi-day Q4 2025 disruptions. The Mar 17 delivery outage was resolved in under 90 minutes - a big contrast with 2025 patterns. Meta's reliability is notably better this quarter.
What Advertisers Should Do
- Audit your March Microsoft Advertising reporting data - expect gaps in SOV, offline conversions, and shopping data.
- Verify your March 24 Google Ad Manager revenue - publishers may have experienced reduced fill rates during the 6-hour window.
- If you run Meta ads, check for any spend anomalies around the March 17 ads delivery outage.
- Set up automated monitoring so you hear about the next incident in 5 minutes instead of hours later from a confused client.
Methodology
All data in this report comes from AdStatus monitoring of official status pages for Meta (metastatus.com), Google Ads (ads.google.com/status), and Microsoft Advertising (status.ads.microsoft.com). Each incident is logged with its canonical ID, detection timestamp, resolution timestamp, and severity classification.
Incidents counted: only new incidents created in March 2026 (first_detected_at between 2026-03-01 and 2026-03-31). Resolution times are calculated from detection to platform-confirmed resolution. Some incidents listed as "active" are Microsoft data delays that do not receive explicit resolution updates on the status page.
Get the Next Incident in Your Slack
Stop checking status pages. AdStatus monitors Meta, Google, Microsoft, Pinterest, and Amazon every 5 minutes and sends Slack alerts the moment something breaks. $10/month per workspace, 7-day free trial.
Add to Slack - Free for 7 Days