CorityOne logo

Is CorityOne Down?

SaaSLive status, outages, and incident history

No. CorityOne is up right now.

Every monitored CorityOne system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment CorityOne breaks

CorityOne is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official CorityOne status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

CorityOne Status Summary

As of 02:41 UTC on 14 November 2026, CorityOne is operational. PulsAPI checked CorityOne's official status page and found 75 of 75 components operational, with no active incidents. The latest incident, "Core to MyCority - Certificate Update", was on Nov 12, 2026 and lasted 32 min.

Cite as: PulsAPI, “CorityOne status”, checked 14 November 2026, 02:41 UTC. https://www.pulsapi.com/services/corityone

CorityOne Component Status

The main CorityOne systems on this page. All 75 are operational right now.

75operational
AU2-0 » API-AU2-0
Operational
AU2-0 » Features & Services-AU2-0
Operational
AU2-0 » GX2-AU2-0
Operational

72 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking AU2-0 » MyCority-AU2-0, CA1-0 » API-CA1-0, CA1-0 » Features & Services-CA1-0, CA1-0 » GX2-CA1-0, CA1-0 » MyCority-CA1-0, CA1-1 » API-CA1-1, CA1-1 » Features & Services-CA1-1, CA1-1 » GX2-CA1-1, CA1-1 » MyCority-CA1-1, CA1-2 » API-CA1-2, CA1-2 » Features & Services-CA1-2, CA1-2 » GX2-CA1-2, and 60 more.

See all of them free

Component statuses may change independently during partial outages.

Recent CorityOne Outages & Incidents

Incident history from the official CorityOne status page, including resolution updates.

Core to MyCority - Certificate UpdateResolved Nov 12, 2026 · 32 minResolved

The change to update the internal authentication certificate between Core and MyCority has been completed successfully. Normal service has been restored. Thank you for your patience and understanding. --- [2026-11-12T20:51:29.531Z] (identified) We will be performing maintenance to update the internal authentication certificate between Core and MyCority. During this maintenance, users may experience temporary interruptions when navigating from Core to MyCority. We expect the maintenance to be completed shortly and will provide an update once finished.

Web Service DisruptionResolved Nov 9, 2026 · 1h 23mResolved

Incident Summary A deployment on November 7, 2026, introduced two related issues affecting web service integrations and system performance. The changes were rolled back on the morning of November 9, 2026, restoring normal service operations. Customer Impact Web Service Integrations: Between November 7 and the rollback on November 9, integrations and scheduled imports relying on our web services may have experienced failures, potentially preventing some data from being exchanged as expected. System Performance: On November 9, beginning at approximately 5:00 AM EST, users across multiple regions experienced slower response times when saving or uploading records due to the changes deployed on November 7. Root Cause A change deployed on November 7 affected how the system collects diagnostic and monitoring information. Under certain conditions, this change interfered with web service connections and increased system resource utilization, resulting in integration failures and degraded application performance. Resolution and Next Steps The changes were rolled back on the morning of November 9, restoring normal system performance and web service functionality. Our Engineering team is preparing a corrective update to address the underlying issue. The update will undergo additional validation and testing before being deployed to production. --- [2026-11-09T16:46:49.780Z] (resolved) This incident has been resolved. --- [2026-11-09T15:28:15.145Z] (identified) The issue has been identified, and our team is working on remediation steps to restore normal service. We will continue to provide updates as progress is made. --- [2026-11-09T15:23:06.898Z] (investigating) The Web Service is currently experiencing issues. Our team is actively working to restore the service.

Core (GX2) - Degraded PerformanceResolved Nov 9, 2026 · 4h 53mResolved

Incident Summary A deployment on November 7, 2026, introduced two related issues affecting web service integrations and system performance. The changes were rolled back on the morning of November 9, 2026, restoring normal service operations. Customer Impact Web Service Integrations: Between November 7 and the rollback on November 9, integrations and scheduled imports relying on our web services may have experienced failures, potentially preventing some data from being exchanged as expected. System Performance: On November 9, beginning at approximately 5:00 AM EST, users across multiple regions experienced slower response times when saving or uploading records due to the changes deployed on November 7. Root Cause A change deployed on November 7 affected how the system collects diagnostic and monitoring information. Under certain conditions, this change interfered with web service connections and increased system resource utilization, resulting in integration failures and degraded application performance. Resolution and Next Steps The changes were rolled back on the morning of November 9, restoring normal system performance and web service functionality. Our Engineering team is preparing a corrective update to address the underlying issue. The update will undergo additional validation and testing before being deployed to production. --- [2026-11-09T15:40:31.458Z] (resolved) After a period of monitoring, the service has remained stable. This incident is now considered resolved. --- [2026-11-09T15:34:49.141Z] (monitoring) We are continuing to monitor for any further issues. --- [2026-11-09T15:13:02.001Z] (monitoring) Service performance has returned to expected levels. We are actively monitoring the environment to ensure continued stability and will take further action if necessary. --- [2026-11-09T14:51:12.864Z] (identified) The issue has been identified, and our team is working on remediation steps to restore normal service. We will continue to provide updates as progress is made. --- [2026-11-09T13:41:00.728Z] (investigating) We are continuing to investigate an issue affecting GX2 Core. The impact has now extended to all GX2 Core environments. Customers may experience slow performance, timeouts, or errors when using the application. --- [2026-11-09T13:21:56.696Z] (investigating) We are continuing to investigate this issue. --- [2026-11-09T10:46:48.236Z] (investigating) We are currently investigating an issue affecting the GX2 service in the EU1-0 cluster. Our team is actively working to identify the root cause and will provide further updates as soon as more information becomes available.

Upcoming maintenance

Announced by CorityOne. Planned work, not an outage.

Trubox - 2026.2.0 Development ReleaseScheduled for Nov 18, 2026 · 2h 0mScheduled

Cority is set to release Trubox v2026.2.0 to development sites. The maintenance window is scheduled to apply the latest release to all hosted customers’ development sites. Anticipated Impact: Users will not have access to Development Trubox sites during this change window. Release notes can be found at the following url: https://uc.cority.com/s/article/Cority-IQS-Trubox-v2026-2-0-Release-Notes

ReadySet Production Server Maintenance (2026.11.0)Scheduled for Nov 19, 2026 · 2h 0mScheduled

Cority is set to release ReadySet v2026.11.0. The maintenance window is scheduled to apply the latest release to hosted production sites. Readyset will not be accessible to end users during this time. Release notes can be accessed at the following page: https://userdocs.cority.com/articles/#!readyset-release-notes/readyset-release-november-18

CorityOne Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a CorityOne incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live CorityOne Outage Reports

Problems reported by engineers using CorityOne. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No CorityOne problems reported yet.

Something wrong with CorityOne on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About CorityOne

Is CorityOne down? Its official status page at status.cority.com reports on 75 components, including API-AU2-0, Features & Services-AU2-0 and GX2-AU2-0. PulsAPI checks it every few minutes and can alert you when CorityOne reports an incident.

CorityOne Status FAQ

Is CorityOne down right now?

The verdict at the top of this page comes from the latest poll of the official CorityOne status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if CorityOne is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until CorityOne recovers.

How do I check CorityOne uptime history?

PulsAPI tracks CorityOne uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever CorityOne changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect CorityOne outages?

PulsAPI reads the official CorityOne status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual CorityOne components?

Yes. PulsAPI monitors 75 individual CorityOne components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when CorityOne goes down?

Yes. Create a free account and subscribe to CorityOne: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with CorityOne to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot CorityOne problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor CorityOne?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so CorityOne plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track CorityOne with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services