Incidents reported on status page for Zapster API https://status.zapsterapi.com/ https://d1lppblt9t2x15.cloudfront.net/logos/4251012684a3cf461c279d89f41a2cfe.png https://status.zapsterapi.com/ en https://status.zapsterapi.com/incident/892048 Sun, 10 May 2026 02:40:00 -0000 https://status.zapsterapi.com/incident/892048#793dc9a35891f7314f1f7dd1ced4582b8886f6712a486a72f12152b53372d031 Maintenance completed https://status.zapsterapi.com/incident/892048 Sun, 10 May 2026 02:00:00 -0000 https://status.zapsterapi.com/incident/892048#e29bc29a3c8ad8f46ba645d9456547279ce935c154e865a8e15f34cddc75127e ## What's happening Emergency upgrade of the messaging broker that powers internal communication between Zapster API services. ## Why Our infrastructure provider identified a memory leak in the current cluster version. The fix requires an immediate version upgrade — we'd rather act now than wait for an unplanned outage. ## Impact While the maintenance is in progress, **message processing is paused**: - **Outbound messages**: API requests are still accepted, but messages are queued and won't reach WhatsApp until the maintenance ends. - **Incoming messages**: messages from your contacts are held for processing. - **Webhooks**: notifications to your webhook URL are paused and will be delivered retroactively once the service is back. **No messages are lost**: queues are persistent and processing resumes from where it stopped. ## ETA Estimated **over 1 hour**, with no firm window yet. We'll update this incident as soon as we have a tighter ETA or when the service is restored. ## Need help? The Support WhatsApp team is on standby throughout the maintenance window: +55 87 99907-9455 https://status.zapsterapi.com/incident/888468 Tue, 05 May 2026 20:41:16 -0000 https://status.zapsterapi.com/incident/888468#f0e4d0d503ce86bfa70f866dad9de8df5d7e8ac42d1d5e9c3597e3e1e344f0dd Documentation recovered. https://status.zapsterapi.com/incident/888468 Tue, 05 May 2026 20:36:20 -0000 https://status.zapsterapi.com/incident/888468#c8ba55168b9895167ac4351581c5a608cdd09267ffff5c63acb7beb95a54279f Documentation went down.