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 2 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 a moment 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 100% across 2 days watched Today

What the provider reported

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.

Network Connectivity from India to NYC Resolved

24 Jul 2026, 05:36 · 2h 6m · NYC1

resolved · 24 Jul, 07:42 Between 07:46 UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP.

Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources.

We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.
monitoring · 24 Jul, 06:45 We are observing improvements in network connectivity for users in India accessing resources in our NYC region. Our team is monitoring the situation to ensure that the service has returned to normal operation and remain stable. We appreciate your patience and will provide an update once the issue is fully confirmed as resolved.
identified · 24 Jul, 05:36 We have noticed network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.

Reserved IP routing in TOR1 Resolved

16 Jul 2026, 08:39 · 3h 45m · Reserved IP, TOR1

resolved · 16 Jul, 12:24 Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally.

If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.
monitoring · 16 Jul, 12:01 Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results.

Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team.

We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.
identified · 16 Jul, 10:30 Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.

Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1.

Our engineering team is now working on implementing a fix. We will provide updates as more information becomes available.
investigating · 16 Jul, 08:39 Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.

In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1.

Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.

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

Components we depend on

Responses

Audio

Files

Fine-tuning

Realtime

Batch

Embeddings

90 days, as WOCOM observed it

90 days ago 100% across 2 days watched Today

What the provider reported

Elevated errors in ChatGPT conversations for Free users Resolved

13 Aug 2026, 10:19 · 8h 39m

resolved · 13 Aug, 18:58 All impacted services have now fully recovered.
monitoring · 13 Aug, 17:07 We’ve applied a mitigation and are monitoring recovery following an issue with a downstream provider.
monitoring · 13 Aug, 11:54 We have applied the mitigation and are monitoring the recovery.
identified · 13 Aug, 10:48 We are still implementing the mitigation.

Error while creating custom RBAC roles for Enterprise users Resolved

13 Aug 2026, 09:03 · 8h 23m

resolved · 13 Aug, 17:26 All impacted services have now fully recovered.
monitoring · 13 Aug, 16:25 We have applied the mitigation and are monitoring the recovery.
identified · 13 Aug, 13:48 We are continuing to implement the mitigation
identified · 13 Aug, 10:44 We are still implementing the mitigation.

Increase in errors on API, Codex and Work Mode Resolved

11 Aug 2026, 16:35 · 1h 7m

resolved · 11 Aug, 17:42 All impacted services have now fully recovered.
monitoring · 11 Aug, 17:16 We have applied the mitigation and are monitoring the recovery.
identified · 11 Aug, 16:39 We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation.
identified · 11 Aug, 16:37 We have identified that users are experiencing elevated errors for the impacted services.

We are working on implementing a mitigation.

Users unable to login to ads manager Resolved

11 Aug 2026, 12:25 · 3m

resolved · 11 Aug, 12:28 All impacted services have now fully recovered.
identified · 11 Aug, 12:25 We have identified that users are are unable to login to ads manager.

We are working on implementing a mitigation.

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

openai/gpt-oss-120b Performance Issue Resolved

19 Mar 2026, 07:51 · 59m

resolved · 19 Mar, 08:50 The issues affecting openai/gpt-oss-120b have been resolved. The model is operating normally. Actions were taken to cancel billing plans and restrict verification status of organizations engaged in coordinated abuse. We apologize for the disruption and thank you for your patience.
monitoring · 19 Mar, 08:23 We have implemented a fix for openai/gpt-oss-120b and performance is improving. We’re now monitoring the model to ensure stability persists. If all remains normal, we will resolve the incident in the next update.
identified · 19 Mar, 07:51 We have identified the problem affecting the openai/gpt-oss-120b model. The issue has been traced to malicious traffic patterns. A fix is in progress, we are working to block the source of these requests. Users may still see degraded performance from requests made to openai/gpt-oss-120b as we identify and block the orgs from which this traffic is originating.

Planned Maintenance: meta-llama/llama-4-maverick-17b-128e-instruct (me-central-1) Resolved

24 Oct 2025, 13:25

maintenance scheduled · 24 Oct, 13:25 When: Monday, Nov 3, 2025

• 00:00 to 03:00 UTC (Sunday, Nov 2, 16:00 to 19:00 PT)

What

• We’re performing planned maintenance on the me-central-1 deployment of meta-llama/llama-4-maverick-17b-128e-instruct to keep systems current. Other regions remain available.

Impact

• No customer action required.

• Requests that explicitly target the me-central-1 endpoint for this model will be unavailable for approximately 2 hours within the window, possibly longer if troubleshooting is required.

• Requests not pinned to me-central-1 will continue to be served by other regions.

Updates

• We will post at start, after the change completes, and when monitoring finishes.

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