Notice history
View current statusAug 2025
Jul 2025
- Postmortem · UTC
Following the recent incident on 7/7/25, where propagation and notification tasks were delayed, our team has published a report that includes contributing factors, response efforts, and actions being taken to prevent similar issues in the future.
We apologize for the disruption this may have caused and appreciate your patience while our team worked to resolve this issue.
You can find the full report here: [LINK] - Resolved · UTC
After monitoring the implemented fix, we have confirmed this issue has been successfully resolved.
Thank you again for your patience as we worked to resolve this issue and we apologize for any inconvenience this issue may have caused.
- Monitoring · UTC
We implemented a fix and are currently monitoring the result.
We appreciate your continued patience while we work to resolve this issue.
- Identified · UTC
We have identified the issue and our team is actively working on a mitigation.
Thank you for your patience as we work to resolve this issue.
- Investigating · UTCWe are currently investigating this incident.
Jun 2025
- Resolved · UTCThis incident has been resolved.
- Investigating · UTC
Impact includes access grants and revocations. We are currently investigating this incident.
- Resolved · UTCThis incident has been resolved.
- Investigating · UTCWe are currently investigating this incident.
