All Systems Operational

Uptime over the past 90 days. View historical uptime.
App Servers Operational
90 days ago
99.87 % uptime
Today
Europe 1 (Germany) Operational
90 days ago
99.87 % uptime
Today
Europe 2 (Finland) Operational
90 days ago
99.87 % uptime
Today
United States 1 (St. Louis, MO) Operational
90 days ago
99.87 % uptime
Today
United States 2 (N. Virginia) Operational
90 days ago
99.87 % uptime
Today
United States 3 (St. Louis, MO) Operational
90 days ago
99.87 % uptime
Today
Brazil 1 (Sao Paulo) Operational
90 days ago
99.87 % uptime
Today
United States 5 (Manassas, Virginia) Operational
90 days ago
99.84 % uptime
Today
DB Servers Operational
90 days ago
99.99 % uptime
Today
Europe 1 (Germany) Operational
90 days ago
100.0 % uptime
Today
Europe 2 (Finland) Operational
90 days ago
100.0 % uptime
Today
United States 1 (St. Louis, MO) Operational
90 days ago
100.0 % uptime
Today
United States 2 (N. Virginia) Operational
90 days ago
100.0 % uptime
Today
United States 3 (St. Louis, MO) Operational
90 days ago
100.0 % uptime
Today
Brazil 1 (Sao Paulo) Operational
90 days ago
100.0 % uptime
Today
United States 5 (Manassas, Virginia) Operational
90 days ago
99.96 % uptime
Today
Infrastructure Operational
90 days ago
99.99 % uptime
Today
Logs ? Operational
90 days ago
100.0 % uptime
Today
Build System ? Operational
90 days ago
99.98 % uptime
Today
Metrics ? Operational
90 days ago
100.0 % uptime
Today
Web App Operational
90 days ago
100.0 % uptime
Today
App (app.zcloud.ws) Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

May 20, 2025

No incidents reported today.

May 19, 2025

No incidents reported.

May 18, 2025

No incidents reported.

May 17, 2025

No incidents reported.

May 16, 2025

No incidents reported.

May 15, 2025
Scheduled Maintenance for Metrics Service
Completed - The scheduled maintenance has been completed.
May 15, 05:00 UTC
Verifying - Verification is currently underway for the maintenance items.
May 15, 04:16 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 15, 03:00 UTC
Scheduled - We are performing updates to enhance service performance and reliability.
May 15, 02:50 UTC
May 14, 2025
DNS not resolving
Resolved - Everything should be working fine.
May 14, 02:17 UTC
Monitoring - All apps should now be resolving DNS correctly. We've completed the migration of all DNS configurations to a new AWS account using Route53.

If you still encounter any issues, please let us know. Contact us via WhatsApp to avoid delays related to email DNS resolution problems.

Here's a summary of what happened with our AWS account, based on what we know so far:

---

**Thu May 8, 2025**
12:29:59 GMT-0400 (Amazon Standard Time)

AWS contacted us requesting we complete these steps:
1. Change our AWS root account password
2. Enable multi-factor authentication (MFA) on the AWS root user for additional account protection
3. Check AWS CloudTrail logs for suspicious activity
4. Review for any unauthorized AWS usage
5. Respond to the existing support case or create a new one confirming completion of steps 1-4

Completing these steps would restore account access, prevent suspension, and allow us to apply for a billing adjustment if applicable. Any billing adjustment for unexpected charges would be considered after securing the account.

---

**Thu May 8, 2025**
23:21:42 GMT-0400 (Amazon Standard Time)

We replied addressing all four required topics:
1. Root Account Password Change
2. Multi-Factor Authentication (MFA) Review
3. CloudTrail Log Review
4. Usage Review

We wrote a methodical response since one of our clients previously had their account suspended and we had to rescue them from a difficult situation.

---

**Mon May 12, 2025**
23:27:53 GMT-0400 (Amazon Standard Time)

After receiving no response from AWS, we contacted them to confirm everything was okay.

---

**Tue May 13, 2025**
13:06:40 GMT-0400 (Amazon Standard Time)

They suspended our account and we asked why.

---

**Tue May 13, 2025**
13:40:33 GMT-0400 (Amazon Standard Time)

They replied: "This case has been resolved. Please contact us again if you need further assistance."

However, the issue was not resolved—our account remained suspended.

---

We haven't heard anything further from AWS. We've tried reaching multiple contacts within AWS, but they seem to have limited ability to help with the actions we need.

We still don't know if we'll recover our account.

In the coming days, we'll monitor the situation and likely decide to migrate our Route53 integrations elsewhere.

We sincerely apologize for the DNS resolution outage. We'll work hard to prevent this single point of failure with DNS in the future. While we use multiple providers for various services, we didn't expect AWS to fail us on this critical service.
May 13, 23:51 UTC
Update - We have thousands of domains, all managed through our Route 53 AWS account.

We've recreated all records in our database for a new account.

Most, if not all, apps should be working again. If you encounter any issues, please contact us via WhatsApp at +55 67 992449937, as our emails may be affected by a DNS issue.
May 13, 22:26 UTC
Update - Some DNSs are already recreated.

We are proceeding with recreating all of them.
May 13, 21:18 UTC
Identified - We are recreating our DNS records in another AWS account.

We will keep updating here.
May 13, 20:55 UTC
Investigating - AWS blocked our account, and our domains are managed by Route 53.

We are working on a fix ASAP.
May 13, 20:16 UTC
Building process issues
Resolved - Everything is back to normal.

As we changed our storage, the rebuild action will fail on old builds since the source code zip is in the old storage.

This action is rarely used, so it should be fine for our clients.
May 14, 00:18 UTC
Monitoring - The build should be working fine again.
May 13, 18:51 UTC
Update - We've tested our change to send the zip file with code to OCI; now, we will modify our build process to consume from OCI.
May 13, 18:30 UTC
Update - The issue is that AWS blocked our account. We don't have many components running there, but the S3 bucket for storing uploaded source code is hosted on AWS.

We are working with AWS to restore our account, which was blocked without any apparent reason. In parallel, we're moving the build process to use a bucket on OCI.

We will keep posting updates here.
May 13, 17:50 UTC
Identified - We have identified an issue in our build process and are working to resolve it.
May 13, 17:33 UTC
May 13, 2025
May 12, 2025

No incidents reported.

May 11, 2025

No incidents reported.

May 10, 2025

No incidents reported.

May 9, 2025

No incidents reported.

May 8, 2025

No incidents reported.

May 7, 2025

No incidents reported.

May 6, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage