WOCOM Status Page

Services

10 of 10 operational · filter by location to see what each region carries

SIP Trunk

Inbound and outbound calling

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

WOCOM Hub Platform

Portal, extensions, routing, call control

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

AI Receptionist

Answering, transfers, message capture

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

AI Transcription

Call transcripts and sentiment analysis

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

Messaging Services

SMS and WhatsApp notifications

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

WOCOM Meet

Video meetings, recording and screen share

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

Hosted Services

Cloud PBX and hosted infrastructure

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

Customer Portal

Billing, usage and account management

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

WOCOM API

Programmable voice and platform API

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

Ticketing System

Support tickets and escalations

Operational

Jamaica Miami Atlanta New York Texas San Francisco Canada

90 days ago 100% uptime Today

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.

Components we depend on

Regions · N. Virginia

Regions · Ohio

Regions · Canada

90 days, as WOCOM observed it

90 days ago 100% across 35 days watched Today

What the provider reported

Nothing affecting the components above in the records we hold.

Collected from Amazon Web Services's public status feed every five minutes, last check 2 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.

Components we depend on

API

Cloud Control Panel

Droplets · ATL1

Networking · ATL1

DNS

Droplets · NYC1

Networking · NYC1

Managed Databases · NYC3

Droplets · NYC3

Load Balancers · NYC3

Networking · NYC3

Networking · SFO3

Droplets · TOR1

Networking · TOR1

90 days, as WOCOM observed it

90 days ago 94.29% across 35 days watched Today

What the provider reported

Cloud Control Panel and API Resolved

24 Aug 2026, 12:14 · 1d 1h · API, Cloud Control Panel

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.

Managed Databases Creation Resolved

23 Aug 2026, 00:11 · 9h 22m · NYC1, NYC3

resolved · 23 Aug, 09:33 Our Engineering team has resolved the issue preventing cluster creation on Managed Databases in the NYC3 and NYC1 regions. Customers can now create new Managed Databases Clusters normally.

Our Engineering team has monitored the environment to ensure stability. We sincerely apologize for any inconvenience this disruption may have caused to your operations. If you continue to experience issues, please open a ticket with our Support team:
monitoring · 23 Aug, 06:30 Our Engineering team has implemented the necessary fixes affecting Managed Database cluster creation in the NYC3 and NYC1 regions. Users should now be able to create new Managed Database clusters.

We are currently monitoring the situation to ensure that the service has returned to normal operation and remains stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
investigating · 23 Aug, 02:06 We continue to investigate an issue affecting DigitalOcean Managed Databases cluster creation across multiple regions.

During this time, users may experience errors when creating Managed Database clusters via the Cloud Control Panel or API.

Our engineering team is implementing a mitigation and working to restore normal provisioning. We will provide another update as soon as more information is available.
investigating · 23 Aug, 00:11 Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests.

We apologize for the inconvenience and will share an update once we have more information.

Multiple Services Availability Resolved

6 Aug 2026, 11:33 · 1m · Global, Cloud Firewall, DNS

resolved · 6 Aug, 11:33 Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing.

Customers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications.

The services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing.

We apolo…

Cloud Control Panel Access Resolved

3 Aug 2026, 08:58 · 4h 2m · Cloud Control Panel

resolved · 3 Aug, 12:59 Between 09:36 and 13:30 UTC on August 3, some customers experienced intermittent errors while accessing the DigitalOcean Cloud Control Panel. We renewed the affected internal certificates and restored access. The issue is resolved, and the Cloud Control Panel is operating normally. We apologize for the disruption.
monitoring · 3 Aug, 11:39 We have implemented mitigation for the issue causing some customers to experience intermittent errors when accessing the DigitalOcean Cloud Control Panel. We are seeing recovery and are monitoring the service closely. We will provide another update once we have confirmed the issue is fully resolved
investigating · 3 Aug, 08:58 Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an "mTLS verification failed" message. Our engineering team is actively investigating.

We apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available.

If you have any questions related to this issue, please send us a ticket from your cloud support page.

Collected from DigitalOcean's public status feed every five minutes, last check 2 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.

Components we depend on

Files

Fine-tuning

Realtime

Embeddings

90 days, as WOCOM observed it

90 days ago 88.57% across 35 days watched Today

What the provider reported

SSO sign-in and SCIM provisioning issues Resolved

18 Sep 2026, 18:00 · 19m

resolved · 18 Sep, 18:18 All impacted services have now fully recovered.
monitoring · 18 Sep, 18:06 We have applied the mitigation and are monitoring the recovery.
identified · 18 Sep, 17:40 Some users are unable to sign in with single sign-on (SSO). User and group provisioning through SCIM is also affected.

We are working on implementing a mitigation.

Overbilling for OpenAI-hosted containers in the Agent API Resolved

18 Sep 2026, 17:29 · 9h 23m

resolved · 19 Sep, 02:52 All impacted services have now fully recovered.
monitoring · 19 Sep, 00:00 We have applied the mitigation, and any new sessions would not run into this issue. We are monitoring the recovery.
identified · 18 Sep, 20:08 We are still implementing the mitigation.
investigating · 18 Sep, 18:22 We’re continuing to work on a fix for the container overbilling issue.

We’re also reviewing affected usage to identify impacted customers and calculate refunds.

Delayed support responses Resolved

18 Sep 2026, 16:36 · 3h 34m

resolved · 18 Sep, 20:10 All impacted services have now fully recovered.
monitoring · 18 Sep, 16:59 We have applied the mitigation and are monitoring the recovery.

Some support responses by email and chat may still be delayed while we work through affected cases.
identified · 18 Sep, 16:36 Some users are experiencing delayed responses from OpenAI Support by email and chat.

We’re investigating and will share updates as we learn more.

We are seeing elevated error rates across API models Resolved

17 Sep 2026, 16:29 · 21m

resolved · 17 Sep, 16:50 All impacted services have now fully recovered.
monitoring · 17 Sep, 16:20 We have applied the mitigation and are monitoring the recovery.
identified · 17 Sep, 15:20 We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation.

Collected from OpenAI's public status feed every five minutes, last check 2 minutes ago. Times are Jamaica time. A provider's state is reported here, never counted towards WOCOM's own.

Components we depend on

Website

API

whisper-large-v3

whisper-large-v3-turbo

openai/gpt-oss-120b

llama-3.3-70b-versatile

90 days, as WOCOM observed it

90 days ago 100% across 35 days watched Today

What the provider reported

Data Center Failure Impacting Capacity Resolved

1 Jul 2026, 18:01 · 1h 34m

resolved · 1 Jul, 19:35 The capacity issue has been resolved. All services are operating at normal capacity. The incident was caused by a power loss issue that led to a cooling system failure at one of our US Central data centers. We apologize for any disruption and appreciate your patience.
monitoring · 1 Jul, 18:48 We have redistributed and allocated more capacity to production models in the US Central region. Users should see performance return to normal. We’re now monitoring the infrastructure to ensure stability.
identified · 1 Jul, 18:27 A power loss issue at approximately 22:20pm UTC led to a subsequent cooling system failure at one of our US Central data centers that is causing reduced capacity, primarily for the `openai/gpt-oss-20b` model. The team is working on restoring capacity.
identified · 1 Jul, 18:11 We have identified a cooling system failure at one of our US Central data centers that is causing reduced capacity. The team is working on restoring capacity. Users continue to see elevated latencies for specific models.

Collected from Groq's public status feed every five minutes, last check 2 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.

WOCOM Status Page

Services

Third-party platforms

WOCOM Sales

Start a conversation

Connecting you with an agent...