outages.live
Live
EntireIncident ·

Accidental "Entire Gates" checks on GitHub repositories

ResolvedOfficial update

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.

The latest update from Entire.

State

Resolved

Started

Lasted

2 h 14 min

Worst impact

Notice

Timeline

2 updates
19:4320:1720:5021:2421:57
NoticeUpdate postedTimes in UTC

Monitoring

2 h 14 min 100%

Updates

Times in UTC

As posted by Entire

Resolved

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.

Monitoring

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 and are monitoring. We apologize for the mistake.

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

4.8× 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·Errors loading repositories and trails

This issue has been resolved and service is operating normally.

Resolved

Entire·Delayed repository metadata and activity updates in India region

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

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