WOCOM Status Page
Services
1 service runs in Atlanta
Third-party platforms
Providers WOCOM builds on. Their components, incidents and update timelines are collected here every five minutes and shown in full — there is nothing to read on somebody else's site.
- investigating · 15 Nov, 07:38 [RESOLVED] Increased Connectivity issues in US-EAST-1
- investigating · 21 Sep, 18:26 [RESOLVED] Increased Error Rates
Collected from Amazon Web Services's public status feed every five minutes, last check 5 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.
-
resolved · 16 Nov, 16:40
Between 16:40 UTC and 18:22 UTC, our Engineering team observed an increase in 4xx error rates with App Platform operations via the Cloud Control Panel. During this time, users may have experienced errors while attempting to view or update their apps on the Cloud Panel. This was a UI-only issue and apps continued to run throughout the duration of the incident.
Our Engineering team has resolved this issue. As of 18:22 UTC, users should no longer be experiencing this issue and all services should now be functioning normally.
We apologize for any inconvenience, and if you are still experiencing any problems or have additional questions, please open a Support ticket within your account.
- in progress · 13 Nov, 15:17 Scheduled maintenance is currently in progress. We will provide updates as necessary.
-
scheduled · 13 Nov, 15:16
This is a continuation of the scheduled Storage Network Maintenance in TOR1 originally planned for Nov 13, 2026, 15:30-19:00 UTC The work did not finish within the initial maintenance window, so our Engineering team is continuing the upgrades to the storage system's network switches in the TOR1 region.
Expected impact:
The upgrades continue to be performed in a rolling fashion with automatic failover to ensure service continuity. We do not expect any customer impact. If an unexpected issue arises during the upgrade, there could be a temporary inability to create new Droplets, Backups may retry, and Snapshots may fail, in the TOR1 region. We will work to resolve any such situation promptly.
We will post an update when the maintenance is complete.
If you have any questions related to this issue, please send us a ticket from your cloud support page:
- in progress · 13 Nov, 10:30 Scheduled maintenance is currently in progress. We will provide updates as necessary.
- scheduled · 13 Nov, 09:30 Maintenance will begin as scheduled in 60 minutes.
-
scheduled · 13 Nov, 00:39
Start: Nov 13, 2026, 15:30 UTC
End: Nov 13, 2026, 19:00 UTC
During the above window, our Storage Systems team will be performing upgrades to the storage system’s network switches in the TOR1 region to enhance infrastructure performance and stability.
Expected impact:
These upgrades are performed in a rolling fashion with automatic failover to ensure service continuity. We do not expect any customer impact during this maintenance window. If an unexpected issue arises during the upgrade, there could be a temporary inability to create new Droplets, Backups may retry, and Snapshots may fail, in the TOR1 region. We will work to resolve any such situation promptly.
If you have any questions related to this issue, please send us a ticket from your cloud support page:
-
postmortem · 15 Sep, 13:44
1. What happened
Between 16:56 UTC and 23:09 UTC on August 24, 2026, customers using DigitalOcean’s Cloud Control Panel, Public API, and dependent product management systems experienced elevated request error rates, peaking at 25%, in two distinct windows totaling 3.5 hours of active degradation within a 6-hour span. Running Droplets, network routing, and block storage \(Volumes\) remained fully functional and unaffected throughout the event. No customer data loss occurred.
The event was initiated during a planned infrastructure migration of the database layer supporting identity, authentication, and authorization services. The migration introduced increased execution latency for a critical authorization query. In response to the elevated query latency, multiple upstream services initiated automated hedged retries. This secondary request amplification led to queue buildup in excess of… -
resolved · 25 Aug, 14:04
Our Engineering team has confirmed all services remain stable and we will now resolve this incident. Further details on root cause and mitigation will be provided in a postmortem via this status page for users interested in learning more.
Thank you for your patience throughout this incident. If you continue to experience any issues, please reach out to Support from within your account - monitoring · 25 Aug, 11:30 Our Engineering team has continued to monitor the health of all services and has observed no recurrence of impact over the past 12+ hours. We will continue to monitor services for a short period to confirm stability before we mark this incident resolved. We understand the impact this incident had for DigitalOcean users and we will publish a postmortem on the status page to provide further details on root cause and mitigation.
-
monitoring · 24 Aug, 19:54
Our Engineering team has implemented mitigation measures to address the issue impacting the DigitalOcean public API and Cloud Control Panel. We are seeing improvements, and users should now be able to access the Cloud Control Panel and use the public API normally.
We are continuing to monitor the service to ensure it remains stable and will provide further updates as more information becomes available. We appreciate your patience and understanding.
Collected from DigitalOcean's public status feed every five minutes, last check 5 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.
- resolved · 14 Nov, 00:27 All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
- monitoring · 13 Nov, 23:11 We are monitoring recovery from errors affecting ChatGPT billing, including checkout, and Ads invoice retrieval.
- resolved · 15 Nov, 19:17 All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
- monitoring · 14 Nov, 00:31 We are monitoring the affected services to confirm recovery. Delays in cost data are still expected.
- monitoring · 13 Nov, 13:56 We’ve applied a mitigation and are monitoring the affected services to confirm recovery. Delays in cost data are still expected.
- identified · 13 Nov, 11:10 We have identified an issue causing delays in publishing Organization cost data through the Costs API. API and ChatGPT usage are not affected. We are working to restore normal data freshness.
- resolved · 13 Nov, 00:55 All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
-
identified · 12 Nov, 22:59
We have identified that users are experiencing elevated errors for the impacted services.
We are working on implementing a mitigation.
- resolved · 13 Nov, 19:18 All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience.
- monitoring · 13 Nov, 11:20 We’re seeing signs of recovery for the Microsoft 365 connector and are continuing to monitor the affected services to confirm recovery.
- investigating · 12 Nov, 13:29 We’re investigating an issue with Microsoft connectors where new connections may be broken and tools are not working as expected. We’ll share an update when we know more.
Collected from OpenAI's public status feed every five minutes, last check 5 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.
- maintenance in progress · 17 Oct, 21:00 Maintenance has started
- maintenance scheduled · 16 Oct, 11:22 The GroqCloud console will be undergoing scheduled maintenance affecting console functionality from 04:00 to 06:00 UTC. API requests and inference are not affected. During the window, the console usage, activity and logs pages may show errors for up to 30 minutes, and new usage data may be up to 1 hour late. No usage or billing data will be lost.
- resolved · 12 Oct, 13:36 The issues affecting minimaxai/minimax-m2.7 have been resolved. The model is operating normally. Root cause: hardware connectivity issues. We apologize for the disruption and thank you for your patience.
- identified · 12 Oct, 13:17 We have identified the problem affecting the minimaxai/minimax-m2.7 service. The issue was traced to hardware connectivity issues. A fix is in progress. Users may still see API failures until the fix completes.
- resolved · 11 Oct, 23:00 The Groqcloud console issue has been resolved. All services are operating normally. We apologize for the disruption and appreciate your patience.
- monitoring · 11 Oct, 22:47 We've mitigated the errors on the GroqCloud console and functionality has been restored. Inference API requests are not affected, and we will provide additional updates here.
- investigating · 11 Oct, 22:37 We are currently investigating increased error rates on our GroqCloud console (including metrics, /models API endpoints, and API key creation). Users may receive 500 errors when making requests to console.groq.com. Our engineers are isolating the issue.
- resolved · 10 Oct, 11:14 The issues affecting minimaxai/minimax-m2.7 have been resolved. The model is operating normally. Root cause: Data center hardware issues. We apologize for the disruption and thank you for your patience.
- identified · 10 Oct, 05:09 We have identified the problem affecting the enterprise-only minimaxai/minimax-m2.7 model. The issue was traced to hardware issues in our data center. A fix is in progress. Users may still see failed requests until the fix completes.
Collected from Groq's public status feed every five minutes, last check 5 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.
Status is maintained by the WOCOM operations team. Something not right? Tell us or call the fault line on 876-906-7240.