News
hidden-dummy
⚠️ 10.16.2026 Current status of the GREEN-API service
🟢 10.15.2026 Telegram instance operations restored
⚠️ 10.14.2026 Technical issues with MAX and WhatsApp instances
10.14.2026 Current status of the GREEN-API service
10.13.2026 MAX instance operations restored
10.13.2026 WhatsApp instance operations restored in the Russian Federation
10.13.2026 Massive outage of Yandex.Cloud servers
10.13.2026 WhatsApp instance creation option restored
10.08.26 Technical issues
10.08.2026  Important Changes to WABA Operations (webinar)

🟢 10.15.2026 Telegram instance operations restored

Good news! We have restored all Telegram instances.

Instances of the 41ХХ and 45ХХ types are now operational again. Scan the QR code to start using them.

Service has been restored for instances of the following types:
– 41ХХXXXXXXXX,
– 45ХХXXXXXXXX

Update on the current status of the GREEN-API service:

✅ green-api.com website — operational
✅ Console — operational. We have restored the display of payments and instance renewals
✅ Chats — operational
✅ CheckAccount method for verifying MAX accounts — operational
✅ WhatsApp 1ХХХ, 5ХХХ, 7ХХХ — operational
✅ MAX 31XX, 35XX — operational
✅ Telegram 41XX, 45XX — operational. QR code re-scanning required
✅ GREEN-API mobile app — operational
✅ WhatsApp Proxy — operational
✅ Service status — operational

Currently known issues:

⚠️ The following issues are being observed on WhatsApp instances (7201, 1101, 1103, 1105, 55XX):
– Unstable performance
– Instances may return 404 or 504 errors
– Messages may arrive with a delay
– GetWaSettings method could occasionally display outdated information
– QR codes fail to generate on some instances
– Issues with the message-sending queue have been noted on some instances
– Notifications (webhooks) for incoming messages may be duplicated

⚠️ The following issues are being observed on MAX instances (31XX, 35XX):
– Incoming messages arrive with a delay
– Webhooks may fail to send
– The host 3XXX.kz.api.green-api.com is inaccessible from the Russian Federation; we recommend using api.green-api.com instead
– When using direct hosts, timeouts may occur with sending methods (sendMessage, sendFileByUrl) and receiveNotification
– Increased API response latency may occur when accessing from the Russian Federation
– MAX instances may fail to load in the console or appear as unauthorized; please use the GetStateInstance method

⚠️ Other issues:
– The media host media.green-api.com is temporarily unavailable. We recommend using the direct host for your specific instance or media.greenapi.com.

🛠 We are continuing to address the aftermath of a global outage caused by technical issues at the cloud provider Yandex.Cloud.

You can monitor the current operational status of the GREEN-API service at https://status.green-api.com. We will provide further updates as functionality is restored.

We apologize for any inconvenience! 🙏
Thank you for being with us!

GREEN-API Team💚

Scroll to Top