service · inferred from evidence
Axiom
A hosted log ingestion and analytics service that experienced an outage, causing network errors in client applications.
- First install & authentication can result in an `API Error 404: Not Found`
Install the latest Axiom CLI. The breakage came from a client-library/API compatibility mismatch, and the maintainer shipped a corrected release.
- brew cli client cannot auth
A practical guide for Axiom. [lukasmalkmus (collaborator)]: axiom auth login failing with API error 404 was a regression from the new API backend rollout. Fixed in CLI v0.13.1: upgrade and log in again.
- Internal errors in @axiomhq/pino cause server to crash
The SDK did not catch network errors from ingest, so any ingestion failure (outage, expired/invalid token) became an uncaught exception that took down the process. Maintainers released new versions of @axiomhq/js and @axiomhq/pino that catc
- Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (@axiomhq/nextjs)
Teaches the verified fix from a real axiom support thread: module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins (@axiomhq/nextjs)