outages.live
Live
ReplitIncident · 2026-09-24 16:05 UTC

GitHub connector may not be working for users

ResolvedOfficial update

We've identified an issue with GitHub connectors starting Tuesday 1PM PT that prevented users from being able to connect their project source code to GitHub. This issue is recovering and we'll keep you updated here.

The latest update from Replit.

State

Resolved

Started

38 d ago

2026-09-24 16:05 UTC

Lasted

13 days

until 2026-10-07 14:52 UTC

Worst impact

Partial outage

Timeline

1 update
Sep 24Sep 27Oct 1Oct 4Oct 7
NoticeUpdate postedDates in UTC

Resolved

13 days 100%

Updates

Times in UTC

As posted by Replit

Resolved2026-10-07 14:52 UTC

We've identified an issue with GitHub connectors starting Tuesday 1PM PT that prevented users from being able to connect their project source code to GitHub. This issue is recovering and we'll keep you updated here.

Replit in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

34

Days with an incident

46

Median duration

2 h 3 min

This incident

151× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

13 days
median 2 h 3 min
90 days agoToday

Other Replit incidents

All incidents

Replit·Agent and Workspace Issues

Replit reports a major outage that affects Agent and Workspace interactions. Replit is now monitoring the fix. Replit states that agent interactions should work again and asks users to update the browser tab.

Partial outageupdated 6 h ago

Replit·Investigating an issue related to the agent's ability to process images

We have resolved some of the earlier issues where connections to replit was disrupted.

Resolvedresolved 2 d ago

Replit·Investigating issues related to platform access

Access to Replit services has recovered.

Resolvedresolved 2 d ago

Replit·Users can't access privately deployed apps

Users are able to access their private apps again.

Resolvedresolved 9 d ago

Replit·Hubspot Connectors is not working

HubSpot connectors that use Replit’s default configuration are not working. We’ve identified the root cause and are currently working on a fix.

Resolvedresolved 9 d ago

Follow Replit

Your coding agent knows when Replit is down, and tells you when a failure is theirs, not yours. You can also get Replit incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "replit" and tell me if Replit has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=replit
Slack
/feed subscribe https://outages.cc/feed.xml?providers=replit

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane