SMS Magic Status
Real-time updates of SMS Magic issues and outages
SMS Magic status is Operational
Message Delivery Service
SMS Magic REST API
Salesforce API
Zoho API
Message Delivery Service
DLR Sync with Salesforce
Incoming Message Sync with Salesforce
You're checking on SMS Magic - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Start Time : Mar 23, 2026 - 00:35 PDT
There is a carrier-partner incident currently impacting 10DLC SMS and MMS services for international numbers.
Customers may experience intermittent latency impacting inbound (MO) and outbound (MT) SMS and MMS via 10DLC .
The cause of this issue is under investigation at this time.
SMS Magic Outage Survival Guide
SMS Magic Components
SMS Magic US Data Center
SMS Magic REST API
Salesforce API
Zoho API
Message Delivery Service
Start Time : Mar 23, 2026 - 00:35 PDT
There is a carrier-partner incident currently impacting 10DLC SMS and MMS services for international numbers.
Customers may experience intermittent latency impacting inbound (MO) and outbound (MT) SMS and MMS via 10DLC .
The cause of this issue is under investigation at this time.
DLR Sync with Salesforce
Incoming Message Sync with Salesforce
DLR sync with Zoho
DLR sync with Open API
Incoming sync with Zoho
Incoming sync with Open API
Converse Desk on SaaS Portal
Incoming MMS messages processing
SMS Magic Buy Portal
Analytics Dashboard
SMS Magic Customer Portal
Incoming messages
Email Service
Billing & provisioning service
URL Shortening & Tracking
SMS Magic Website
SMS Magic Australia Data Center
SMS Magic REST API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Salesforce API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Zoho API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Message Delivery Service
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
DLR Sync with Salesforce
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming Message Sync with Salesforce
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
DLR sync with Zoho
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
DLR sync with Open API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming sync with Zoho
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming sync with Open API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Converse Desk on SaaS Portal
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming MMS messages processing
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
SMS Magic Customer Portal
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Analytics Dashboard
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
SMS Magic Buy Portal
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming messages
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Email Service
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Billing & provisioning service
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
URL Shortening & Tracking
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
SMS Magic Europe Data Center
SMS Magic REST API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Salesforce API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Zoho API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Message Delivery Service
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
DLR Sync with Salesforce
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming Message Sync with Salesforce
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
DLR sync with Zoho
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
DLR sync with Open API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming sync with Zoho
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming sync with Open API
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Converse Desk on SaaS Portal
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming MMS messages processing
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
SMS Magic Customer Portal
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Analytics Dashboard
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
SMS Magic Buy Portal
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Incoming messages
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Email Service
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
Billing & provisioning service
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.
URL Shortening & Tracking
SUMMARY We identified an issue where incorrect monthly usage emails were sent to a majority of payee customers in the USA environment. The February usage report sent on March 7 contained incorrect credit counts due to a system glitch in the report generation process.
IMPACT Customers who received the February usage email may have seen incorrect credit usage totals in their report. This issue affected email reports only and did not impact actual billing, account balances, or platform usage data.
CURRENT STATUS We are currently regenerating the February usage reports with corrected data. Customers are advised to disregard the previous February usage email received earlier and refer to the corrected report once received.