Previous incidents

Identity provider recovered.

Identity provider recovered.

Log collection recovered.

Log collection recovered.

Log collection recovered.

Log platform recovered.

Metrics storage recovered.

Identity provider recovered.

Log platform recovered.

Metrics storage recovered.

Identity provider recovered.

Log retrieval recovered.

Log retrieval recovered.

Log retrieval recovered.

Log retrieval recovered.

Metrics storage recovered.

The monitor for paas-health.magnolia-platform.com/metrics went down due to receiving status 502 and 503 errors, indicating service unavailability, which was temporarily unavailable through different regions. The issue was resolved automatically within a few minutes without further escalation.

The monitor for paas-health.magnolia-platform.com/metrics was down due to a 502 Bad Gateway error, transitioning to a 503 Service Temporarily Unavailable error shortly after. The issue was detected across multiple continents, and the monitor recovered automatically within a few minutes. The incident was resolved without further escalation.

The incident was caused by a 502 status error at paas-health.magnolia-platform.com/metrics, with the service becoming temporarily unavailable. The monitors across all regions detected the errors, but the system auto-resolved the incident shortly after, postponing escalations.

The monitor for paas-health.magnolia-platform.com/metrics was down due to a Status 503 error, causing temporary unavailability. The issue was resolved automatically within a few minutes as monitors recovered across different regions, leading to the incident being marked for auto-resolution.

The incident was caused by a 503 Service Temporarily Unavailable error at paas-health.magnolia-platform.com/metrics. The monitor recovered across all regions within a few minutes, and the issue was resolved automatically after a 5-minute wait, postponing any further escalations.

The incident involved the paas-health.magnolia-platform.com/metrics endpoint going down with a status 503 error, indicating the service was temporarily unavailable. This error was detected from multiple locations. The issue resolved automatically shortly after, with monitors in North America, Australia, and Europe recovering, leading to the postponement of further actions and confirming service stability.

The incident was caused by a temporary issue that resulted in the monitor id.magnolia-platform.com being down with a status 503 error. The problem, identified as "Service Temporarily Unavailable" and followed by a "502 Bad Gateway" error, resolved automatically within minutes, with monitors in North America, Europe, and Australia recovering shortly afterward.

The incident was caused by a monitor down at paas-health.magnolia-platform.com/metrics, receiving status codes 502 and 503. After a brief downtime, the monitor recovered across all regions, and the incident was automatically resolved.

The monitor for paas-health.magnolia-platform.com/metrics went down, showing a 503 Service Temporarily Unavailable error. This affected regions in Asia, Europe, and North America. The monitor recovered automatically across all regions within a few minutes, and the incident was set to auto-resolve after verifying stability.

The monitor for paas-health.magnolia-platform.com/metrics went down due to a 503 Service Temporarily Unavailable error across different regions. The issue resolved itself within minutes as monitors in Europe, North America, and Asia recovered automatically. The incident was set to auto-resolve after a brief wait.

The incident was caused by the paas-health.magnolia-platform.com/metrics monitor returning a "503 Service Temporarily Unavailable" status due to a temporary issue across different regions. The service automatically recovered shortly after, resolving the incident without further intervention.

The monitor for paas-health.magnolia-platform.com/metrics went down due to a temporary 503 Service Unavailable error, detected across multiple regions. The issue was resolved automatically, with the monitor recovering shortly after the errors were detected.

The paas-health.magnolia-platform.com/metrics monitor went down with a status 503 error, showing "Service Temporarily Unavailable." The issue was detected across multiple regions, including Australia, Europe, and North America. The monitor recovered automatically shortly after, and the incident was resolved after a brief monitoring period.

The incident was triggered by a 502 status error on paas-health.magnolia-platform.com/metrics, which later switched to a 503 status indicating service was temporarily unavailable. This issue affected users across North America, Europe, and Asia. The monitors recovered automatically shortly after, and the incident was resolved without any manual intervention needed.

The monitor for paas-health.magnolia-platform.com/metrics was down, returning a status 503 Service Temporarily Unavailable across Europe, North America, and Asia. The issue was resolved automatically after a brief period, once the monitor recovered in all locations.

The monitor for paas-health.magnolia-platform.com/metrics was down due to connectivity issues, leading to a "couldn't connect to server" error. After briefly experiencing these errors across multiple regions, the system automatically recovered within a few minutes, resolving the incident.

The incident was caused by the monitor for paas-health.magnolia-platform.com/metrics being down, showing a 502 error. This triggered multiple 503 errors across Asia, North America, and Europe. The monitor automatically recovered soon after, resolving the incident without further escalation.

The incident was caused by the domain cockpit.mplatform.magnolia-platform.com not being recognized, leading to a series of Fastly errors with status 500 across multiple regions. After several attempts, the domain issue was identified and resolved, leading to the recovery of the monitor without further action required.

The monitor for id.magnolia-platform.com experienced a temporary outage with a 503 Service Unavailable status across multiple regions. The issue was automatically resolved after monitors recovered in Europe, North America, and Australia, and no manual interventions were required.

The incident was caused by issues with the SSL peer certificate or SSH remote key on thanos.magnolia-platform.com, resulting in intermittent unavailability and several status 503 errors. The monitors detected multiple errors across different regions, but the system managed to recover automatically after several fluctuations in service availability.

The monitor for id.magnolia-platform.com went down due to timeouts and service being temporarily unavailable, resulting in repeated 503 errors and SSL connection issues across multiple regions. The service intermittently recovered on its own, and the incident was eventually resolved automatically after the system remained consistently stable for a sufficient period.

The incident was caused by a monitor for thanos.magnolia-platform.com going down with a "503 Service Temporarily Unavailable" error across multiple regions. The issue repeatedly occurred and resolved itself automatically several times, with the system set to wait before confirming a complete resolution.

The incident was caused by multiple occurrences of a 503 Service Unavailable error affecting the id.magnolia-platform.com site. The site went down intermittently across different global regions. Each time the monitor recovered, the status temporarily returned to normal before recurring. Ultimately, the issue was resolved after several cycles of recovery and reappearance, with the monitors stabilizing over time.

The monitor for id.magnolia-platform.com experienced a temporary outage with a 503 status error, making it unavailable across various regions. After initial recovery, the issue reoccurred but was eventually resolved, with systems automatically holding off on further actions to ensure stability.

The incident was caused by the monitor id.magnolia-platform.com being down, resulting in a 503 Service Temporarily Unavailable error across different regions. The situation was resolved automatically within a few minutes as the monitor recovered in Europe, North America, and Asia, after which the incident was marked for auto-resolution.

The incident was caused by the monitor for thanos.magnolia-platform.com being down with a "Status 503 Service Temporarily Unavailable." The issue resolved itself automatically following a temporary recovery across different regions, but briefly reappeared before completely resolving, with a wait time before final auto-resolution and postponed escalations.

The incident was caused by a timeout while receiving data at thanos.magnolia-platform.com, leading to service disruptions and multiple errors including 503 Service Unavailable and SSL certificate issues. Despite several temporary recoveries, the problem repeatedly reappeared. The incident was eventually managed by waiting for systems to stabilize and automatically resolved without further escalations.

The incident at id.magnolia-platform.com occurred due to timeouts where no headers were received, leading to repeated errors across regions. The system intermittently showed 404 and 503 errors, SSL certificate issues, and eventual 403 Forbidden responses. Despite initial recoveries, the issue reappeared multiple times across different locations. Eventually, the site recovered automatically, and the monitor stabilized without requiring manual intervention.

The monitor for paas-health.magnolia-platform.com/metrics experienced downtime with a 502 Bad Gateway error and shifted to a 503 Service Unavailable status across different regions. The issue was swiftly resolved within a few minutes as the monitor recovered automatically in Asia, North America, and Europe.

The monitor for paas-health.magnolia-platform.com/metrics was down, showing a 502 Bad Gateway status that caused a temporary outage detected in North America, Europe, and Asia, with subsequent 503 errors. The problem resolved automatically a few minutes later, restoring normal service without needing further escalation.