outages.live
Live
EntireIncident ·

Delayed repository metadata and activity updates in India region

ResolvedOfficial update

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

The latest update from Entire.

State

Resolved

Started

Lasted

28 min

Worst impact

Degraded

Timeline

2 updates
23:3923:4623:5300:0000:07
DegradedUpdate postedTimes in UTC

Investigating

28 min 100%

Updates

Times in UTC

As posted by Entire

Resolved

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

Investigating

Investigating — Elevated processing delays in one region We identified an issue causing delays in background data processing in one of our regions. A fix has been merged and is being rolled out. Impact: Core product functionality is unaffected. Repository metadata updates are delayed for a subset of repositories and will catch up automatically once the fix is live. A small number of users may see gaps in their activity history from earlier today; we are preparing a backfill to restore this data. Next update: once the fix is deployed and we've confirmed recovery.

Entire in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

4

Median duration

28 min

This incident

About the median

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

2 h 14 min
median 28 min
90 days agoToday

Other Entire incidents

All incidents

Entire·Accidental "Entire Gates" checks on GitHub repositories

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.

Resolved

Entire·Errors loading repositories and trails

This issue has been resolved and service is operating normally.

Resolved

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane