Live / Corrigo / Incident
Corrigo: JLLT OneServiceCenter has been alerted to potential service issues with Enterprise Back Office in the AM Region
Corrigo · corrigo.comMajor incidentResolved2026-10-01 13:27 UTC
Public — what happened
Summary
Corrigo reported a major problem with Enterprise Back Office in its AM region beginning at 16:59 UTC on September 30, 2026, saying some users could get a 502 error and be unable to reach Back Office. The company opened a master support case, 01050374, and asked customers who thought they were affected to cite it when contacting Support. About an hour later, at 18:00 UTC, Corrigo said it had put a fix in place and was watching the results. It did not give a cause, and the incident was marked resolved on October 1 at 13:27.
Timeline
- Started — 2026-09-30 16:59 UTC
- Investigating — 2026-09-30 16:59 UTC
- Monitoring — 2026-09-30 18:00 UTC
- Resolved — 2026-10-01 13:27 UTC · 20h 28m 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 41, 2026, our weekly internet health report.