← Back to Twilio History
minor✓ Resolved

New Accounts Are Being Incorrectly Identified as Legacy Whatsapp Account

Twilio•Wed, Apr 29, 2026, 05:40 PM
Status
resolved
Duration
23h 59m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Apr 30, 2026, 05:40 PM
This incident has been resolved.
identifiedThu, Apr 30, 2026, 10:31 AM
Our engineers have identified an issue where new accounts are being incorrectly identified as legacy WhatsApp accounts and are working to deploy a fix. We expect to provide another update in 16 hrs or as soon as more information becomes available.
identifiedThu, Apr 30, 2026, 02:33 AM
Our engineers have identified an issue where new accounts are being incorrectly identified as legacy WhatsApp accounts and are working to deploy a fix. We expect to provide another update in 8hrs or as soon as more information becomes available.
identifiedWed, Apr 29, 2026, 09:33 PM
Our engineers have identified an issue where new accounts are being incorrectly identified as legacy WhatsApp accounts and are working to deploy a fix. We expect to provide another update in 4h or as soon as more information becomes available.
identifiedWed, Apr 29, 2026, 07:27 PM
Our engineers have identified an issue where new accounts are being incorrectly identified as legacy WhatsApp accounts and are working to deploy a fix. We expect to provide another update in 2h or as soon as more information becomes available.
identifiedWed, Apr 29, 2026, 06:24 PM
Our engineers have identified an issue where new accounts are being incorrectly identified as legacy Whatsapp accounts and are working to deploy a fix. We expect to provide another update in 1h or as soon as more information becomes available.
investigatingWed, Apr 29, 2026, 05:40 PM
Our monitoring systems have detected a potential issue with New Accounts Are Being Incorrectly Tagged With Legacy Whatsapp Account Flags. Our engineers have been alerted and are investigating. We will provide an update when we have more details.

📊 TECHNICAL DETAILS

Internal ID
0d14b073-3567-4e76-b52e-ccbf7bd043f0
External ID
441kvr95r8xj
🕐 Started
Wed, Apr 29, 2026, 05:40 PM
🔄 Last Updated
Thu, Apr 30, 2026, 05:40 PM
✓ Resolved
Thu, Apr 30, 2026, 05:40 PM
MINOR
Impact Level
23h 59m
Total Duration
6
Status Updates
Affected Components
Messaging Channels
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed