Your campaign is ready. 50,000 messages queued up. You hit "Send" – and nothing happens. The Meta dashboard shows "Operational." Your heart rate spikes.
Before you panic-call support: in 90% of cases, the problem isn't Meta. Since 2026, three things have been throwing WhatsApp marketers off track: pacing mechanisms, invisible quality restrictions, and new AI policies. Plus a fourth issue that's barely on anyone's radar: the switch to BSUIDs.
This guide shows you how to tell real outages from self-inflicted problems – and what you can actually do when your messages get stuck.
First Step: Check Official Status Sources
When messages aren't getting through, your first stop is the official Meta Business Status Dashboard. Here you can see if the WhatsApp Business Platform is currently having issues.
But be careful: the dashboard is often delayed. Meta sometimes updates the status 15–30 minutes after an outage begins. A green "Operational" doesn't automatically mean your account is working.
What most people don't know: Meta isn't always to blame. On February 4, 2026, Cloudflare outages took down large parts of internet infrastructure – including Meta services. The official dashboard still showed "Operational" while messages were already stuck. External monitoring tools like Downdetector often show you these backbone problems faster than Meta's own page.
If both sources show green, the problem is most likely on your end. And that's where it gets interesting.
Why the API Seems "Down" – But Isn't
The most frustrating scenario: everything shows green, but your messages are stuck. Welcome to 2026.
Latency Differences: Marketing Is Slower Than Service
Here's a fact most people don't know: Meta doesn't treat all messages equally. While service messages (OTPs, shipping confirmations) are processed with a P99 latency under 2.5 seconds, marketing messages often see latency above 7 seconds – and even higher during peak times.
This isn't a bug. It's intentional. Meta prioritizes transactional messages to handle traffic spikes. Your newsletter is "stuck" while your competitor's one-time passwords fly through.
What this means for you: if your marketing campaign feels sluggish, it's usually not a technical outage. It's prioritization. Plan accordingly and don't send time-sensitive campaigns during peak hours (e.g., not Monday at 9 AM).
Template Pacing vs. Portfolio Pacing: The Difference Matters
Pacing isn't a bug – it's a feature. But there are two variants you need to distinguish:
Portfolio Pacing affects your entire account. It kicks in for new accounts (under 500,000 messages per year) or when Meta detects red flags – like a sudden volume spike. Your entire sending gets throttled, regardless of the template.
Template Pacing affects individual message templates. Meta sends a portion of your campaign (e.g., 10%) and waits for feedback. If an above-average share of recipients block your message, that specific template gets throttled or stopped – other templates can keep running.
Both lead to error code 132015 or delays without an explicit error message.
The difference between Pacing and Pausing: Pacing slows sending to collect feedback. Pausing stops it completely when negative signals (blocks, reports) during pacing were too high. Pacing is a test. Pausing is the verdict.
The solution: Ramp up new campaigns slowly. Start with 1,000–5,000 messages, wait 24 hours, analyze reactions. Only then scale. This is called "warm-up" – and it's mandatory in 2026.
More on optimizing your sending quality in our WhatsApp Business API Guide.
Ghost Restrictions: Limited Without Warning
Sometimes Meta's fraud detection gets too aggressive. Your account gets restricted, but the "Account Quality" dashboard shows nothing. No warning, no message, no explanation.
This happens especially often with accounts that scale quickly or show unusual sending patterns.
What you can do:
Check your Quality Rating in Meta Business Manager.
Reduce sending volume for 48–72 hours.
Analyze whether specific templates are getting blocked disproportionately.
When in doubt: work with a BSP like Chatarmin, which often has faster access to Meta resources than standard support.
How to build your trust level with Meta is explained in our post WhatsApp Green Tick.
AI Policy Violations: The New Pitfall
Since January 15, 2026, Meta has tightened the rules for AI chatbots. General AI assistants – bots that answer everything like a ChatGPT clone – are banned.
Only bots with clear business context are allowed: customer support, product advice, appointment booking. If your bot acts too "general," Meta can block it. For you, this looks like an API outage, but it's actually a policy block.
Check:
Is your bot limited to a specific use case?
Are there clear boundaries on what the bot won't answer?
Have you considered the new AI guidelines in your bot setup?
If you're unsure whether your WhatsApp Automation is compliant: let us take a look.
The ID Problem: BSUID Instead of Phone Number
This is the technical topic causing confusion in 2026 – and hardly anyone is talking about it.
With the rollout of WhatsApp Usernames (starting June 2026), Meta is switching to the Business-Scoped User ID (BSUID). The BSUID is a unique identifier for each user that will gradually replace the phone number as the primary identifier.
Why this causes problems: Many CRMs and custom integrations expect a phone number in the webhook. But Meta is increasingly delivering a BSUID. The result: the message gets delivered, but your CRM doesn't recognize the customer. It looks like an API error – but it's a mapping problem on your end.
What you need to do:
Check if your CRM or integration can process BSUIDs.
Adjust your webhook logic to match both formats (number and BSUID).
Plan for username support: starting summer 2026, users can be reachable without a phone number.
At Chatarmin, we've already updated this mapping. If your messages arrive but don't show up in your CRM, this is often the reason – not the API.
Error Codes: What They Mean and How to Fix Them
If you're lucky, the API at least gives you an error code. Here are the most important ones for 2026:
| Error Code | Meaning | Solution |
|---|---|---|
| 132015 | Template paused (pacing or poor feedback) | Stop campaign, check quality rating, apply warm-up strategy |
| 1005 | Number still registered on On-Premises | Migrate to Cloud API – On-Premises was shut down October 23, 2025 |
| 131030 | Recipient not on WhatsApp | Build in number validation before sending |
| 131031 | Template not approved or expired | Check template status in Business Manager |
| 131047 | Re-engagement required (24h window expired) | Use only approved templates, no free text |
| 131051 | Too many messages to this number | Respect rate limit, reduce sending frequency |
| 400 (generic) | Malformed request | Check payload structure and JSON syntax |
| 401 | Authentication failed | Renew bearer token, check API access in Business Manager |
Important: Not every error comes from the API. Often delivery fails on your own server – e.g., due to faulty webhook signature validation, timeouts, or the BSUID issue (see above).
Cloud API vs. On-Premises: There's Only One Path Now
If you still have documentation for "On-Premises API" lying around: delete it.
Support for On-Premises ended on October 23, 2025. Meta has concentrated all resources on the Cloud API. If you're seeing error 1005, you missed that date and need to migrate urgently.
The good news: the Cloud API is easier to manage, doesn't require your own server infrastructure, and gets new features first. The bad news: if you haven't migrated yet, your setup has been on borrowed time for months.
Set Up Monitoring: Webhooks Instead of Hoping
Manual testing is not a monitoring strategy. For real oversight, you need webhooks.
Webhooks notify you in real-time about your message status: sent, delivered, read – or failed. Instead of waiting for errors, you get notified immediately.
What you should track:
messages: Incoming messages and replies
message_status: Delivery confirmations and errors
message_template_status_update: Changes to your templates
For technical implementation, you need an endpoint on your server that receives and processes webhooks. Meta sends a signature with it (X-Hub-Signature) that you should validate.
Sounds complex? It is. At Chatarmin, we handle this monitoring for you. You get plain-language notifications like "Template XY has been paused" instead of cryptic error codes. Just like Luxusbetten24, who run high sending volumes without constantly staring at error codes.
What to Do During Real Outages
Sometimes Meta actually goes down. It's rare, but it happens – as the Cloudflare-related outage on February 4, 2026 showed. Here's your playbook:
Stay calm. Panic emails to support accomplish nothing.
Check status pages: metastatus.com + Downdetector
Don't resend. Duplicate messages annoy customers and hurt your quality rating.
Use queuing. Professional systems hold messages in a queue and send automatically once the API is back.
Communicate. For longer outages: inform your team so customer support knows what's happening.
Farbenlöwe uses exactly this setup: support-heavy communication with consistent quality rating – even when things get stuck.
Conclusion: Usually You're the Problem (And That's Good News)
Sounds harsh, but it's actually good news: if the problem is on your end, you can fix it. Real Meta outages are rare. Pacing, latency prioritization, BSUID mapping, and policy violations are common – and you can avoid all four with the right setup.
The short version:
Always check official status pages first (but don't trust them blindly).
Understand the difference between pacing and pausing.
Expect higher latency for marketing messages (>7s vs. <2.5s).
Update your webhooks for BSUID – username support is coming.
Keep your bots compliant (no general AI assistants since January 15, 2026).
Don't feel like googling error codes and configuring webhooks? Chatarmin handles technical stability so you can focus on marketing.
Book your individual consultation now →
Frequently Asked Questions About WhatsApp API Status
Is WhatsApp Business currently down?
First check the official Meta Business Status Dashboard and external sites like Downdetector. Meta often shows "Operational" even when local disruptions or pacing measures are active.
What does WhatsApp error code 132015 mean?
This code means your template sending has been paused (pacing). Meta is currently checking user reactions because the template is new or has received negative feedback.
Why are my WhatsApp marketing messages delayed?
Marketing messages often have higher latency (P99 >7 seconds) than service messages (<2.5 seconds) because Meta deprioritizes them during peak times. This isn't a technical outage – it's intentional prioritization.
What is the Business-Scoped User ID (BSUID)?
The BSUID is a unique identifier for users that supplements and will gradually replace the phone number as the primary identifier in the API starting 2026. It's necessary to correctly process usernames and privacy settings.
Why am I getting error code 1005?
Error 1005 signals that a number is still registered on the deprecated On-Premises API. This was shut down on October 23, 2025 – you need to migrate to the Cloud API.
Are AI chatbots banned on WhatsApp?
Since January 15, 2026, general-purpose AI assistants are banned. Only bots for specific business purposes like support, bookings, or product advice are allowed.
What's the difference between template pacing and pausing?
Pacing slows sending to collect feedback – your campaign runs, just slower. Pausing stops sending completely when negative signals during pacing were too high.
How many messages can I send as a new business?
Unverified businesses start with a limit of 250 messages per 24 hours. After business verification in Meta Business Manager, the limit increases to 1,000 – verified accounts with good history often jump directly to 100,000 in 2026.
Why aren't messages reaching my CRM?
This is often due to webhook errors: either your CRM still expects phone numbers while the API is already delivering BSUIDs, or webhook signature validation is failing. Check both.
Are utility templates sent for free?
Utility templates (e.g., shipping updates, booking confirmations) are free within the 24-hour service window. Outside this window, standard Meta fees apply.
