Live  /  CorityOne  /  Incident

CorityOne: Trubox APP02 Monitoring

CorityOne · cority.comMinor incidentResolved2026-10-23 17:00 UTC
Public — what happened

Summary

CorityOne said it was watching for a possible performance problem affecting its Trubox service on a server called APP02, starting at 15:10 UTC on 2026-10-23. Shortly afterward it announced a planned emergency restart of some services at 12:00 PM Eastern, which would have briefly blocked all users from reaching Trubox. By 15:55 UTC the company said it had put a fix in place, that the restart was no longer thought necessary, and that it was continuing to monitor the application. The incident was marked resolved at 17:00 UTC, and CorityOne rated it as minor.

Affected

TruBox-APP02

As listed on CorityOne’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach CorityOne against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for CorityOne: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the CorityOne report →

More from CorityOne

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the CorityOne status & history page.

Related: CorityOne status & history. SquidGrid is not affiliated with CorityOne.