outages.live
Live

Loops

Loops is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

1

Median duration

1 h 34 min

Longest incident

1 h 34 min

Components

8

Email Sending

Loops Operational
90 days agoNo incidentsToday
Campaigns Operational
90 days agoNo incidentsToday
Transactional Operational
90 days agoNo incidentsToday
API Operational
90 days agoNo incidentsToday
App Operational
90 days ago1 day with an incidentToday
SMTP Relay Operational
90 days agoNo incidentsToday
Webhooks Operational
90 days agoNo incidentsToday
Status page Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Sep 11, 2026

Duration1 h 34 min13:16 to 14:49Delay in email metric processingDegraded

The metrics processing pipeline has caught up. No metrics were lost, this was only a delay in processing.

Maintenance

Status page migration to a new provider

We will be undergoing scheduled maintenance during this time.

Maintenancestarts in 91 d

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane