Live / Providers / Writer
Writer
writer.comNo open incidents
AI · SquidGrid tracks Writer’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.
Public — what Writer is reporting
Current & recent incidents
ResolvedUS API Down
2026-05-04 16:50 UTC · source
Resolvedwriteragent-down
2026-03-31 21:33 UTC · source
ResolvedRepeated Connector Configuration Prompts
2026-03-18 14:01 UTC · source
ResolvedWriter Agent SEV1 Outage (DB Lock Contention During Migration)
2026-03-10 15:17 UTC · source
ResolvedWriter Down
2026-03-09 19:35 UTC · source
ResolvedPalmyra Vision down through public api requests
2026-03-03 15:45 UTC · source
ResolvedTemplateHighP95Latency
2026-02-27 22:11 UTC · source
ResolvedBaseten embedding models down
2026-02-27 18:16 UTC · source
Track record
SquidGrid has archived 8 incidents from Writer’s own status page since 2026-02-27: 0 in the last 90 days, against 0 in the 90 days before.
- Most recent incident: 195 days ago
- Status page last checked 2026-11-16 01:27 UTC
With SquidGrid — where the route changes
Independent path health
A status page tells you what Writer has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.
Writer runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Writer is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.
🔒 Sign in to see
Incident track record: 90-day trend, median and worst time to fix
What tends to break, from their own incident write-ups
Recent public reports of problems with this service
Included with any paid plan.
See the full report →