Live

Status page migration to a new provider

MaintenanceOfficial update

We will be undergoing scheduled maintenance during this time.

The latest update from Loops.

State

Scheduled

Starts

in 91 d

2027-02-01 00:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Loops

Scheduled2026-11-01 17:18 UTC

We will be undergoing scheduled maintenance during this time.

Affected components

1
Status page

Loops in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

1 h 34 min

This incident

Not comparable

Other Loops incidents

All incidents

Follow Loops

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane