WATI
WATI - Status page
Analytics(live.wati.io), Team Inbox(live.wati.io), Broadcast(live.wati.io), Contacts(live.wati.io), Automations(live.wati.io), Billing(live.wati.io), Login(live.wati.io), Onboarding(live.wati.io), Webhook(live.wati.io), Wati API(live.wati.io)
There have been no more reported incidents or failures so far. We have concluded that every component is now operational and working as expected.
Cloudfare just updated us that a fix has been released. We are going to continue monitoring the situation.
Upon confirming our servers' services are running optimally without any faults, we have found that Cloudfare services are currently facing disruptions that are affecting our services.
We will continue to monitor this situation.
Cloudfare status page: https://www.cloudflarestatus.com/
Our team is currently investigating a major instability in multiple modules across our servers.
We already have our engineering team actively seeking for the root-cause and will keep you posted.
Apologies for the inconvenience and count on us on prioritizing the solution!
Billing(eu.wati.io), Billing(live.wati.io), Billing(enterprise.wati.io)
The issue affecting Billing Service has been fully resolved, and all systems are now operating normally.
Summary of the Event:
Between 07:00 AM and 09:27 AM UTC, we experienced increased error and latency with our Billing Service due to AWS outage, specifically related to DNS resolution issue impacting DynamoDB.
Our team is conducting a full post-mortem analysis to prevent this from happening again. We sincerely apologize for the impact this had on you and your business.
We have seen the Billing Services start recovering, and some clients can create a new account or make credit purchases from their account.
We will continue to monitor the situation and will post another update once we have confirmed full recovery.
Starting around 3 PM HKT, we noticed there are multiple errors with our Billing Services. The issue originated from a service disruption, most likely related to a global outage of AWS services
What is the impact?
Most actions that are related to our Billing Services, including but not limited to: new subscription purchase, credit top-up, subscription upgrade/downgrade, add-on purchase/removal, accessing plan details in the account, are all affected.
The service responsible for message charging is still working as usual and has no issues.
What's next?
We will provide another update as soon as we have more information. We apologize for the disruption and appreciate your patience.
Billing(eu.wati.io), Billing(live.wati.io), Billing(enterprise.wati.io)
The issue affecting Billing Service has been fully resolved, and all systems are now operating normally.
Summary of the Event:
Between 07:00 AM and 09:27 AM UTC, we experienced increased error and latency with our Billing Service due to AWS outage, specifically related to DNS resolution issue impacting DynamoDB.
Our team is conducting a full post-mortem analysis to prevent this from happening again. We sincerely apologize for the impact this had on you and your business.
We have seen the Billing Services start recovering, and some clients can create a new account or make credit purchases from their account.
We will continue to monitor the situation and will post another update once we have confirmed full recovery.
Starting around 3 PM HKT, we noticed there are multiple errors with our Billing Services. The issue originated from a service disruption, most likely related to a global outage of AWS services
What is the impact?
Most actions that are related to our Billing Services, including but not limited to: new subscription purchase, credit top-up, subscription upgrade/downgrade, add-on purchase/removal, accessing plan details in the account, are all affected.
The service responsible for message charging is still working as usual and has no issues.
What's next?
We will provide another update as soon as we have more information. We apologize for the disruption and appreciate your patience.