Vendor Status Watch

← all vendors

SolarWinds Loggly status history

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

1incidents, last 30 days
2incidents, last 90 days
5incidents on record
Incidents per week, last 12 weeks:
Get SolarWinds Loggly alerts in your Slack — free templateRSS for SolarWinds Loggly

How long do SolarWinds Loggly incidents last?

43 minmedian incident duration5 measured
4.2 h90th percentile1 in 10 ran longer
—median, major/critical onlynone posted

From 5 incidents with a vendor-posted start and resolve time. Longest on record: Front-end experiencing issues — 4.2 h (2025-11-18 12:07 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 (5)

StartedIncidentStatusImpactDuration
2026-09-03 22:52 UTCDelayed data ingestionresolvednone0 min
2026-08-07 20:54 UTCAlerting Delayresolvednone0 min
2026-05-11 21:06 UTCAlerts Issueresolvednone1 h 14 min
2026-01-21 15:44 UTCAlerts Issueresolvednone43 min
2025-11-18 12:07 UTCFront-end experiencing issuesresolvedminor4 h 12 min

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 SolarWinds Loggly with the template

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

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