---
title: "Infra log · Frazer"
description: "Plain-language write-ups of incidents and operations work on Frazer’s own platform, linked from the email owners get when an incident affected them."
url: https://frazer.ai/infra-log
index: https://frazer.ai/llms.txt
tokens: 379
---

> For agents: every page on frazer.ai is indexed at https://frazer.ai/llms.txt.

# Infra log · Frazer

**Infra log**  frazer.ai

# Our own incidents,  
written up candidly.

Plain-language write-ups of incidents and operations work on Frazer’s own platform. If an incident affected your organization, owners and security contacts get an email that links the write-up.

[Status page](https://frazerstatus.com) [Changelog](https://frazer.ai/changelog)

01 · How it works Fig. 1

## From an incident to a write-up.  
Live on the status page, then here.

The status page shows an incident while it happens. Within 24 hours of mitigation, a preliminary report appears here, and the full postmortem within 7 days; organizations it affected get an email that links it.

**Fig. 1** One incident, from the first alert to the write-up status page off our platform

02 · Where to look

## Where each answer lives.

Is something down right now?

The [status page](https://frazerstatus.com), per region and service. It runs off our platform and on outside DNS, so it stays up when frazer.ai does not.

Did it affect us?

Owners and security contacts get a required email that links the write-up here.

What are you changing?

Each write-up says what happened, without blame, and what we are changing.

What changed in the product?

The [changelog](https://frazer.ai/changelog), with RSS and JSON feeds.

Was there a vulnerability?

[Security notices](https://frazer.ai/security/notices), by email and RSS.

03 · Write-ups

## No write-ups yet.

A write-up appears here when an incident’s postmortem is done.