We started checking Loops on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Loops reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Loops's own status page declared. Below it, any public chatter we saw about Loops and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Loops's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Loops in the last 24 hours, which is not evidence that nothing is wrong.
Loops's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Loops's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Loops next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
Bluesky posts1 in the last hour (prior day averaged 0.1/hour)
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
431
US-West
99.70%
332
Europe
100.00%
303
Asia-Pacific
100.00%
186
Their declared record
Loops's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delay in email metric processingMinor incident
Sep 11, 2026, 1:16 PM UTC to Sep 11, 2026, 2:49 PM UTC (1h 34m)resolved
their latest update (Sep 11, 2026, 2:49 PM UTC): The metrics processing pipeline has caught up. No metrics were lost, this was only a delay in processing.
increased rate of 500 level responsesPartial outage
Mar 2, 2026, 10:58 PM UTC to Mar 2, 2026, 11:44 PM UTC (46 min)resolved
their latest update (Mar 2, 2026, 11:44 PM UTC): This incident has been resolved.
Webhook Delivery DelayedMinor incident
Feb 10, 2026, 11:05 AM UTC to Feb 10, 2026, 6:36 PM UTC (7h 31m)resolved
their latest update (Feb 10, 2026, 6:36 PM UTC): This incident has been resolved.
Elevated error rates for app.loops.soMinor incident
Jan 24, 2026, 7:49 AM UTC to Jan 24, 2026, 9:07 AM UTC (1h 18m)resolved
their latest update (Jan 24, 2026, 9:07 AM UTC): This incident has been resolved.
Elevated error rates for app.loops.soMinor incident
Nov 18, 2025, 12:15 PM UTC to Nov 18, 2025, 3:37 PM UTC (3h 23m)resolved
their latest update (Nov 18, 2025, 3:37 PM UTC): This incident has been resolved.
Oct 20, 2025, 8:30 AM UTC to Oct 20, 2025, 10:47 AM UTC (2h 17m)postmortem published
their latest update (Oct 21, 2025, 5:22 PM UTC): On October 20 2025, Loops was impacted by AWS’s outage in the US-EAST-1 region. We observed a variety of misbehaviors during that time, some more serious than others. Overall, the impact to Loops fell within the wider window provided by AWS \(06:49 UTC to 22:53 UTC\). During the …
Outbound WebhooksMinor incident
Oct 14, 2025, 1:57 PM UTC to Oct 14, 2025, 2:43 PM UTC (46 min)postmortem published
their latest update (Oct 14, 2025, 2:44 PM UTC): Between approximately 13:42 and 14:18 UTC attempted webhook deliveries failed while our webhooks database was unavailable due to an unplanned outage. Webhooks messages during that period were lost and will not be delivered.
We’ve prioritized work to make webhooks more resilient …
Increased 500 errorsPartial outage
Sep 3, 2025, 8:14 AM UTC to Sep 3, 2025, 8:44 AM UTC (30 min)postmortem published
their latest update (Sep 4, 2025, 2:00 PM UTC): Between Sept 3 03:40 UTC and Sept 3 08:30 UTC Loops experienced a period of elevated error rates where API requests intermittently returned 500’s due to high CPU use on our primary database. We resolved the issue and additionally made monitoring and process changes to speed respo…
increased rate of 500 level responsesMinor incident
Aug 20, 2025, 5:30 PM UTC to Aug 20, 2025, 6:51 PM UTC (1h 21m)resolved
their latest update (Aug 20, 2025, 6:51 PM UTC): This incident has been resolved.
Increased 500 status codesPartial outage
Apr 22, 2025, 6:13 PM UTC to Apr 22, 2025, 7:31 PM UTC (1h 17m)resolved
their latest update (Apr 22, 2025, 7:31 PM UTC): This incident has been resolved.
Showing the 10 most recent of 15 incidents Loops has declared in the history we hold.
These entries are Loops's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Loops's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.