Logfire Down? Real-Time Status & Outage Tracker (2026)
Pydantic Logfire Down? Real-Time Status & Outage Checker (2026)
Pydantic Logfire is a modern observability platform built specifically for Python developers, created by the team behind Pydantic. Logfire provides OpenTelemetry-native logging, tracing, and metrics with deep integration for FastAPI, Django, SQLAlchemy, and popular Python frameworks. With first-class Python semantics and a clean dashboard for structured logs and traces, Logfire has rapidly gained adoption among Python/AI engineering teams. When Logfire goes down, structured logs and traces are dropped and Python application observability fails.
This page provides real-time Pydantic Logfire status monitoring, historical uptime data, and instant outage alerts.
Current Logfire Status
Check live Logfire status now: ezmon.com/status/pydantic-logfire
Our monitoring probes Logfire Cloud infrastructure every 60 seconds from multiple geographic regions:
- Logfire Dashboard — Web UI at logfire.pydantic.dev
- OTLP Ingestion Endpoint — OpenTelemetry span and log receiver
- Query API — Log search and trace retrieval
- Alert Engine — Threshold-based alerting
- SDK Connectivity — Python SDK authentication and data upload
Logfire Live Monitoring Dashboard
SERVICE STATUS UPTIME (30d) LAST CHECK
──────────────────────────────────────────────────────
Logfire Dashboard ✅ UP 99.8% 30s ago
OTLP Ingestion ✅ UP 99.7% 30s ago
Query API ✅ UP 99.7% 30s ago
Alert Engine ✅ UP 99.6% 30s ago
SDK Auth ✅ UP 99.8% 30s ago
──────────────────────────────────────────────────────
Multi-region checks: US-East, EU-West, AP-Southeast
Status updates every 60 seconds. Subscribe for instant alerts.
How to Check if Logfire Is Down
Quick Diagnosis Steps
- Check ezmon.com — Multi-region probes confirm ingestion vs. query failures
- Test SDK connectivity — Run a minimal Logfire Python snippet
- Check Logfire status —
status.pydantic.devfor official incidents - Check OTLP endpoint —
curl https://logfire-api.pydantic.dev/ - Pydantic Community Discord —
#logfirefor real-time reports
Logfire Python SDK Health Check
import logfire
import os
import httpx
def check_logfire_status():
"""Check Pydantic Logfire connectivity and ingestion."""
token = os.environ.get("LOGFIRE_TOKEN")
# Test OTLP ingestion endpoint reachability
try:
resp = httpx.get(
"https://logfire-api.pydantic.dev/",
timeout=10
)
print(f"Logfire API reachable: {resp.status_code}")
except httpx.ConnectError as e:
print(f"Cannot reach Logfire API: {e}")
return
# Configure Logfire
logfire.configure(token=token)
# Send a test span
try:
with logfire.span("health-check", source="ezmon-probe"):
logfire.info("Health check probe from ezmon.com", check_type="uptime")
print("Logfire span sent: OK")
except Exception as e:
print(f"Logfire span failed: {e}")
# Test FastAPI instrumentation (if applicable)
try:
import fastapi
from fastapi.testclient import TestClient
app = fastapi.FastAPI()
logfire.instrument_fastapi(app)
@app.get("/health")
async def health():
return {"status": "ok"}
client = TestClient(app)
resp = client.get("/health")
print(f"FastAPI instrumentation: OK ({resp.status_code})")
except ImportError:
print("FastAPI not installed (skipping instrumentation test)")
except Exception as e:
print(f"FastAPI instrumentation check failed: {e}")
print("Logfire: HEALTHY")
check_logfire_status()
Logfire with FastAPI/Django
import logfire
from fastapi import FastAPI
# Initialize Logfire for a FastAPI app
logfire.configure() # Uses LOGFIRE_TOKEN env var
app = FastAPI()
logfire.instrument_fastapi(app)
# Test that traces are flowing
@app.get("/health")
async def health_check():
with logfire.span("health.check"):
logfire.info("Health check requested")
return {"status": "ok", "logfire": "connected"}
# Django integration
# In settings.py:
# import logfire
# logfire.configure()
# logfire.instrument_django(capture_headers=True)
# SQLAlchemy integration
# from sqlalchemy import create_engine
# logfire.instrument_sqlalchemy(engine=engine)
Common Logfire Issues and Fixes
Spans Not Appearing in Dashboard
import logfire
# Check if Logfire is configured
logfire.configure(
token=os.environ["LOGFIRE_TOKEN"],
# Enable console output for local debugging
send_to_logfire="if-token-present",
console=logfire.ConsoleOptions(
min_log_level="debug",
verbose=True
)
)
# Force flush pending spans
import opentelemetry.sdk.trace.export as trace_export
# The SDK flushes on exit, but you can force it:
from opentelemetry import trace
provider = trace.get_tracer_provider()
if hasattr(provider, 'force_flush'):
provider.force_flush(timeout_millis=5000)
print("Spans flushed")
# Check OTLP export success
# Set OTEL_LOG_LEVEL=debug for verbose SDK logging
Token Authentication Issues
# Test token validity
curl -s "https://logfire-api.pydantic.dev/v1/info" \
-H "Authorization: Bearer $LOGFIRE_TOKEN" | jq .
# Re-authenticate via Logfire CLI
logfire auth
# List projects
logfire projects list
# Switch project
logfire use my-project
# Generate new write token
logfire projects tokens create --project my-project
High Volume / Rate Limiting
import logfire
# Configure sampling for high-volume services
logfire.configure(
token=os.environ["LOGFIRE_TOKEN"],
# Sample 10% of spans
trace_sample_rate=0.1
)
# Use span-level sampling for expensive operations
with logfire.span("expensive-operation", _sample_rate=0.01):
# This span sampled at 1%
do_expensive_work()
# Suppress noisy instrumentation
logfire.instrument_httpx(
capture_headers=False, # Don't capture request headers
capture_request_json_body=False
)
Logfire Architecture: What Can Go Down
| Component | Function | Impact if Down |
|---|---|---|
| OTLP Ingestion API | Receives OpenTelemetry spans and logs from SDKs | All application telemetry dropped |
| Query/Dashboard API | Log search, trace visualization, dashboard rendering | Cannot view or search telemetry data |
| Auth Service | Token validation and project access control | SDK auth fails; no data accepted |
| Alert Engine | Threshold-based alerting on log/metric patterns | Alerts not fired on error conditions |
| Storage Backend | ClickHouse-based columnar storage for telemetry | Ingestion queued; historical queries fail |
Logfire Uptime History
| Period | Uptime | Incidents | Longest Outage |
|---|---|---|---|
| Last 7 days | 99.9% | 0 | — |
| Last 30 days | 99.7% | 0 | — |
| Last 90 days | 99.5% | 1 | 1h 10m |
| Last 12 months | 99.3% | 4 | 2h 20m |
Historical data sourced from ezmon.com Logfire monitoring.
Get Instant Logfire Outage Alerts
Never miss a Logfire outage again. ezmon.com monitors Logfire 24/7 with multi-region probes and sends instant alerts via:
- Email (with escalation policies)
- Slack and Microsoft Teams webhooks
- PagerDuty and Opsgenie integration
- SMS and phone call alerts
- Webhook for custom notification pipelines
Set up Logfire monitoring in 30 seconds: ezmon.com/monitor/pydantic-logfire
This page is maintained by ezmon.com — independent uptime monitoring for developer infrastructure. Data is collected from our global probe network and updated in real time. We are not affiliated with Pydantic Services Inc.