Minor Service Outage

About This Site

Welcome to Cary Group AB - Statuspage. A status page is a website used to provide information about the operational status of IT systems, including ongoing incidents, planned maintenance, and system performance in real time.

Uptime over the past 90 days. View historical uptime.
Ryds Bilglas - Booking System (SE) Operational
90 days ago
100.0 % uptime
Today
Ryds Bilglas - Website Operational
Cary Group - Website Operational
Cary Group - Intranet Operational
90 days ago
100.0 % uptime
Today
Cabas (extern) Operational
90 days ago
100.0 % uptime
Today
Cary Group - Integration platform Operational
90 days ago
100.0 % uptime
Today
Cary Group - Gains integration Operational
90 days ago
100.0 % uptime
Today
Cary Group - Calibration Reports integration Operational
90 days ago
100.0 % uptime
Today
Navision (extern) Operational
90 days ago
100.0 % uptime
Today
Cary Group - Data Platform Partial Outage
90 days ago
87.34 % uptime
Today
Cary Group - Glass Mate (Autovalid) Operational
90 days ago
100.0 % uptime
Today
Jira Create and edit Operational
Cary Group - PIM Lite Operational
90 days ago
100.0 % uptime
Today
Cary Group - Price Engine Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Mar 26, 2026

No incidents reported today.

Mar 25, 2026
Service disruption in Price Engine
Postmortem - Read details
Mar 25, 12:45 CET
Resolved - On March 25th, 2026 between 10:04 and 10:11 UTC, the price engine API returned 500 Internal Server Error for all request.

The root cause was a breaking change in how a package handles certain aspects of configuration. This was not caught during the automated tests since the test environments does not have the kind of configuration we have in production that triggered the problem.

Timeline:

09:57 A new version of the software is deployed to production.
10:04 The new version fails to correctly handle the configuration in production and starts returning 500 Internal Server Error.
10:05 The team monitors the logs in production during rollout and notice the problem and starts rolling back the new version.
10:07 Automated alarms are triggered in production due to the errors.
10:11 The previous version is fully rolled out and we are back to normal operations.
Mar 25, 11:59 CET
Mar 24, 2026

No incidents reported.

Mar 23, 2026

No incidents reported.

Mar 22, 2026

No incidents reported.

Mar 21, 2026

No incidents reported.

Mar 20, 2026

No incidents reported.

Mar 19, 2026

No incidents reported.

Mar 18, 2026

No incidents reported.

Mar 17, 2026

No incidents reported.

Mar 16, 2026

No incidents reported.

Mar 15, 2026

No incidents reported.

Mar 14, 2026
All sales orders from Spain not sent to Gains
Postmortem - Read details
Mar 14, 13:51 CET
Resolved - On 2026-03-13, 461 sales orders from Spain were not sent to Gains. These have been resent and will be available in Gains 2026-03-15 (start of office hours.)

No other markets or data were affected.
Mar 14, 13:48 CET
Mar 13, 2026

No incidents reported.

Mar 12, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage