outages.live
Live

Entire

Entire is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Entire status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Entire since . The days before that show only what Entire published.

Incidents in 90 days

3

Days with an incident

4

Median duration

28 min

Longest incident

2 h 14 min

Components

11
entire.com website Operational
90 days agoNo incidentsToday
Control Plane Operational
90 days agoNo incidentsToday
GitHub mirroring Operational
90 days agoNo incidentsToday
Git Service Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Git Service Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Git Service Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
Git Service Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 20, 2026

Duration2 h 14 min to Accidental "Entire Gates" checks on GitHub repositoriesNotice

This issue has been resolved and service is operating normally. Due to a configuration error earlier today, Entire added a non-blocking check to pull requests on a subset of GitHub repositories mirrored to Entire and added a link in the pull request body that didn't have those enabled. We have reverted the configuration change. We apologize for the mistake.

Sep 25, 2026

Duration6 min to Errors loading repositories and trailsDegraded

This issue has been resolved and service is operating normally.

Aug 14, 2026

Duration28 min to Delayed repository metadata and activity updates in India regionDegraded

This issue has been resolved and service is operating normally. A post-incident review will be conducted.

Follow Entire

Your coding agent knows when Entire is down, and tells you when a failure is theirs, not yours. You can also get Entire 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 "entire" and tell me if Entire 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=entire
Slack
/feed subscribe https://outages.cc/feed.xml?providers=entire

Go from tracking outages to fixing production issues with Polylane.

Try Polylane