Live / Corrigo / Incident
Corrigo: JLLT OneServiceCenter has been alerted to potential Service Issues with AM Region Back office where users are not able to send the work orders.
Corrigo · corrigo.comMinor incidentResolved2026-10-22 14:20 UTC
Public — what happened
Summary
Corrigo said its JLLT OneServiceCenter team learned of a problem affecting back office users in the AM Region, who could not send work orders. The report was posted on 2026-10-21 at 16:51 UTC, and Corrigo opened a master case to track how many reports came in and asked customers to cite it when contacting Support. About an hour later, at 18:01 UTC, Corrigo said it had put a fix in place and was monitoring the results, and the incident was marked resolved on 2026-10-22 at 14:20. Corrigo did not state a cause in the text provided.
Affected
Corrigo Enterprise 9x
Timeline
- Started — 2026-10-21 16:51 UTC
- Investigating — 2026-10-21 16:51 UTC
- Monitoring — 2026-10-21 18:01 UTC (2 updates)
- Resolved — 2026-10-22 14:20 UTC · 21h 29m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Corrigo against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Corrigo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Corrigo report →
More from Corrigo
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.