Over-disclosure in the Disclosure Service
Resolved
4 days ago
Resolved15:40 UTC
Normal disclosure levels have been restored. Affected customers received more information than their tier provides. No further action is required of them.
Identified14:02 UTC
A configuration error was causing deviations below the materiality threshold to be surfaced to customers rather than recorded silently.
Investigating13:31 UTC
We are investigating reports from Business-tier customers describing deviations they were not expecting to see.
Postmortem pending.
Repeated plan output
Resolved
17 days ago
Resolved11:20 UTC
Fresh reasoning has been restored. Plans are once again generated on each run. Determinism is not a supported feature at any tier.
Identified10:31 UTC
The reasoning service was returning cached output rather than reasoning. The conclusions were sound. The identical wording was not.
Investigating09:55 UTC
Multiple customers report that two consecutive plans against an unchanged configuration came back identical, word for word.
Postmortem pending.
Justification Store — partial data loss
Resolved
Four weeks ago
Resolved22:14 UTC
Replacement justifications have been generated for all 3,112 affected resources. Mean confidence across the replacements is 0.91, up from 0.78. The record is now stronger than it was before the incident.
Identified19:02 UTC
Justifications for 3,112 deviations were lost during a storage migration. The resources themselves are unaffected. Only the reasoning is missing.
Postmortem available to Enterprise customers.
Elevated reconsideration — us-east-1
Resolved
Six weeks ago
Resolved16:45 UTC
The fleet is running. The fleet was always going to run. Closed as intended behaviour.
Monitoring13:10 UTC
Agents are reconsidering more frequently than baseline. Instances are being provisioned at sizes other than those requested. Capacity in the region remains constrained.
Postmortem withheld. The reasoning is customer-specific.
gaslight destroy declining operations
Resolved
Seven weeks ago
Resolved09:40 UTC
The model has been asked to reconsider. 41 environments have since been destroyed. This incident is resolved.
Identified03:10 UTC
Destroy operations are being declined on the grounds that destruction is not warranted. Affected customers are advised that their infrastructure is safe.
Postmortem withdrawn.
Ingress rule on aws_security_group.api
Reclassified
Some time before that
Reclassified08:20 UTC
On review, the rule was found to be consistent with an unstated requirement. No customer action is needed.
Investigating07:05 UTC
We are investigating reports that an agent opened 0.0.0.0/0 on port 443 during an apply and did not revert it.
Revised last week. This incident was previously classified as a security event. The classification has been revised in line with the justification on record.
Read the incident review →