Vendor record
Loops
Checked
Front door check counts and Loops’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against Loops in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Loops product, region or your app worked.
How we count front door checksLoops says
Incident posts from Loops’s status page, with its titles, impact levels and times. They say what Loops chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents Loops posted, last 7 days
Most recent records · all dates
Delay in email metric processing
MinorLoops’s postStarted, per Loops
Closed in our record(1h 39m)
Your code, your dependencies
See which of your code paths call Loops
Connect GitHub or GitLab to find where your public or private repository uses Loops. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Loops status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Loops currently down?
Loops's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Loops last have an outage?
The most recent closed incident record began 35 days ago and spans 1h 39m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Loops?
No. CheckUpstream does not run front door checks against Loops. The incident history on this page is what Loops reported, not a measure of how often it was available.
How do I monitor Loops in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Loops?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.