All Systems Operational

Updated a few seconds ago

Web Apps

Operational

API

Operational

SMTP

Operational

Outbound Emails Delivery

Operational

Outbound SMS Delivery

Operational

Marketing email campaigns

Operational

Redirection Links

Operational

Inbound Events Tracking

Operational

Outbound Webhooks Processing

Operational

Account & Billing

Operational

Marketing automation

Operational

Landing pages

Operational

Inbox

Operational

CRM

Operational

Contact Import Service

Operational

WebEngage

Operational

Facebook Ads

Operational

Frontends

Operational

Integrations

Operational

WhatsApp Campaigns

Operational

Conversations

Operational

Meetings

Operational

History (Last 5 days)

Incident Status

Service Disruption


Components

Outbound Emails Delivery


Locations

Global




April 24, 2024 1:14AM UTC
[Resolved] All emails have been successfully processed, and all other services are functioning as expected. No emails were lost during this process, although there will be a latency of approximately 2 hours on emails. We apologize for any inconvenience this may have caused.

April 24, 2024 12:52AM UTC
[Monitoring] Email processing has resumed. We are continuing to monitor the email processing and other applications. End users may experience a delay of approximately 2 hours with their outbound emails and Webhooks. No emails have been lost during this process.

April 24, 2024 12:38AM UTC
[Identified] We've identified an issue with one of our providers that has caused the problem. We're already in communication with them to resolve the issue and minimize its impact. Further information will be provided in upcoming updates.

April 23, 2024 11:52PM UTC
[Investigating] Due to an issue, outbound email delivery has been completely disrupted—no emails are being sent. Some clients may encounter difficulties when accessing their accounts. This is also affecting outgoing Webhooks, and we're currently assessing other impacted applications. We've engaged the relevant teams to identify the issue and minimise its impact. Further information will be provided in forthcoming updates.

April 23, 2024 11:19PM UTC
[Investigating] We're aware of an on-going issue with our services. The impact and the scope are still under investigation. We apologize for the inconvenience.

Incident Status

Service Disruption


Components

API, SMTP, Outbound Emails Delivery, Marketing email campaigns


Locations

Global




April 22, 2024 10:15AM UTC
[Resolved] All emails have been successfully processed. For those that experienced delays, end users may observe a latency of up to 30 minutes. New emails are now being processed promptly, without any delay. We apologise for any inconvenience this may have caused.

April 22, 2024 10:07AM UTC
[Monitoring] We identified an issue with one of our infrastructure components that led to the delay. The component has been removed, and we are currently monitoring it. Further information will be provided in the subsequent updates.

April 22, 2024 10:00AM UTC
[Investigating] The incident has affected all clients. Outbound Email delivery is experiencing delays across all platforms, with an expected latency of 30 minutes. The relevant teams are actively investigating and working to minimize the impact.

Incident Status

Service Disruption


Components

Landing pages


Locations

Global




April 22, 2024 8:47AM UTC
[Resolved] We experienced a DNS misconfiguration on our end, resulting in inaccessible URLs. Users could create landing pages but couldn't access them. The misconfiguration has been rectified, and everything is functioning as expected now. We apologize for any inconvenience this may have caused.

April 22, 2024 8:40AM UTC
[Investigating] The issue is impacting all clients who is using Landing Pages. Users are encountering an "ERR_SSL_VERSION_OR_CIPHER_MISMATCH" error message when attempting to access the URLs generated after creating landing pages. It's important to clarify that while the creation of landing pages is still feasible, the issue lies specifically with accessing the URLs. We have currently engaged the relevant teams to thoroughly investigate and resolve this issue. Updates regarding progress will be shared in the next communication.