Live / Corrigo / Incident
Corrigo: JLLT OneServiceCenter has been alerted to potential service issues with Corrigo Enterprise access issues.
Corrigo · corrigo.comMajor incidentResolved2026-11-09 14:44 UTC
Public — what happened
Summary
Corrigo said it learned of a problem on 2026-11-06 at 14:41 UTC in which people trying to open the Corrigo Enterprise back office were getting a 502 Bad Gateway error. About half an hour later it reported that a fix was in place and it was watching the results. At 16:34 UTC the company said the trouble had returned, with back office users possibly seeing a 500 or other generic error and slower response times, and that engineers were investigating the root cause. Corrigo reported a second fix at 19:55 UTC and the incident was marked resolved on 2026-11-09 at 14:44.
Affected
Corrigo Enterprise 9x
Timeline
- Started — 2026-11-06 14:41 UTC
- Investigating — 2026-11-06 14:41 UTC
- Monitoring — 2026-11-06 15:15 UTC
- Investigating — 2026-11-06 16:34 UTC
- Monitoring — 2026-11-06 19:55 UTC
- Resolved — 2026-11-09 14:44 UTC · 3 days 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 46, 2026, our weekly internet health report.