Live  /  Providers  /  Replit

Replit

replit.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Replit. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

AI · SquidGrid tracks Replit’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 Replit is reporting

Current & recent incidents

Resolved

Chat is failing on mobile

2026-11-09 17:57 UTC · source

Resolved

Replit chats are inaccessible

2026-11-02 22:49 UTC · source

Resolved

Some Replit workspaces are inaccessible

2026-11-02 22:13 UTC · source

Resolved

Agent and Workspace Issues

2026-11-02 05:08 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 66 incidents from Replit’s own status page since 2026-05-11: 31 in the last 90 days, against 33 in the 90 days before.

Recent incidents in the archive

Computed by SquidGrid from the incidents Replit published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Replit 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.

Replit 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 Replit is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Replit.