Rewindex

ChangesCriblMultiple organizations did not upgrade during 4.9.1 cloud release

Cribl: Major incident: Multiple organizations did not upgrade during 4.9.1 cloud release

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Cribl removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Multiple organizations did not upgrade during 4.9.1 cloud release
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2024-11-06 14:49 UTC
AddedResolved time#5
Before: not present
After: 2024-11-06 17:13 UTC
AddedUpdateinvestigating#6
Before: not present
After: We are currently investigating this issue.
AddedUpdateinvestigating#7
Before: not present
After: We have identified some Cribl Cloud Organizations have not yet upgraded to version 4.9.1 and are investigating the root cause further. Some users may see version 4.9.0 still active, and may also experience some UI refreshes as we work to resolve the version upgrade. Please contact 'support@cribl.io' if you have any questions or concerns.
AddedUpdateinvestigating#8
Before: not present
After: Cribl Cloud Engineering are diligently working to upgrade the remaining Cloud Organizations to version 4.9.1. We will continue to provide updates here, but please feel free to contact 'support@cribl.io' if you have any immediate questions or concerns.
AddedUpdateinvestigating#9
Before: not present
After: We have identified the issue affecting some Cribl Cloud Organizations from upgrading to version 4.9.1. We are now addressing the last few Organizations and will post a progress update shortly.
AddedUpdateinvestigating#10
Before: not present
After: Cribl Engineering have successfully upgraded the affected Organizations to version 4.9.1.
AddedUpdateresolved#11
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Wednesday, November 6, 2024

1 incident change

All Cribl changesCribl profileMarkdownJSON