Delay in email metric processing
The metrics processing pipeline has caught up. No metrics were lost, this was only a delay in processing.
The latest update from Loops.
State
Resolved
Started
52 d ago
2026-09-11 13:16 UTC
Lasted
1 h 34 min
until 2026-09-11 14:49 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 24 min 90%
Identified
9 min 10%
Updates
Times in UTCAs posted by Loops
The metrics processing pipeline has caught up. No metrics were lost, this was only a delay in processing.
We're continuing to make progress processing a backlog of email metrics.
Email metrics may be slow to appear or not appear on refresh. We are currently investigating the issue.
Affected components
1Loops in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
1
Median duration
1 h 34 min
This incident
About the median
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.
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.live/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.
https://outages.live/feed.xml?providers=loops/feed subscribe https://outages.live/feed.xml?providers=loopsFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane