Vendor Status Watch

← all vendors

Loopup status history

Current state: operational — “All Systems Operational” per https://status.loopup.com (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.

1incidents, last 30 days
3incidents, last 90 days
14incidents on record
Incidents per week, last 12 weeks:

How long do Loopup incidents last?

15.3 hmedian incident duration14 measured
4.0 days90th percentile1 in 10 ran longer
16.1 hmedian, major/critical only3 incidents

From 14 incidents with a vendor-posted start and resolve time. Longest on record: Potential Service Impact in China — 33.8 days (2025-09-17 13:55 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (14)

StartedIncidentStatusImpactDuration
2026-09-19 08:30 UTCTaiwan - Outbound Callsresolvednone2 d 0 h
2026-08-25 08:17 UTCCall completion issues to Vivo network numbers in Brazilresolvednone0 min
2026-08-21 21:57 UTCCloud Telephony – Inbound Call Routing – Partial Service Degradationresolvednone14 h 28 min
2026-05-27 14:12 UTCCloud Telephony - Some Calls to UK Numbers Connecting Without Audioresolvednone19 h 19 min
2026-03-23 11:31 UTCCloud Telephony - South Korea - Service disruption impacting inbound callsresolvedminor22 h 22 min
2026-03-20 09:25 UTCPossible service disruption in South Korea and Israelresolvedminor3 h 03 min
2026-03-10 08:41 UTCSouth Africa - Network Issueresolvedminor2 h 03 min
2026-03-05 08:46 UTCCloud Telephony - Admin Portal - Reporting Dashboardresolvedminor3 d 23 h
2026-01-27 09:18 UTCCloud Telephony - APAC - Call failures impacting outbound calling in Chinaresolvedminor7 h 31 min
2025-11-20 10:38 UTCCloud Telephony - Intermittent load issues impacting the LoopUp Admin Portal (admin.loopup.com and one.loopup.com)resolvednone5 h 26 min
2025-11-18 14:36 UTCCloudflare Outage Impacting LoopUp Admin Portalresolvedcritical18 h 27 min
2025-10-29 16:15 UTCCloud Telephony - Intermittent load issues impacting the LoopUp Admin Portal (admin.loopup.com and one.loopup.com)resolvedmajor16 h 09 min
2025-10-09 08:41 UTCCloud Telephony - Intermittent load issues impacting the LoopUp Admin Portal (admin.loopup.com and one.loopup.com)resolvedmajor5 h 42 min
2025-09-17 13:55 UTCPotential Service Impact in Chinaresolvedminor33 d 19 h

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Loopup with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "loopup"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}