Xplor status history
Current state: operational — “All Systems Operational” per https://status.spotpos.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Xplor incidents last?
From 7 incidents with a vendor-posted start and resolve time. Longest on record: SPOT Corporate - Phone System Service — 37.0 h (2026-02-19 01:11 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 (7)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-08 21:05 UTC | SPOT Hosted - Database Service Degradation | resolved | minor | 3 h 56 min |
| 2026-07-07 16:37 UTC | SPOT Hosted - Service Degradation | resolved | major | 23 h 11 min |
| 2026-05-18 23:26 UTC | Temporary Interruption to SPOT Cloud Services | resolved | major | 1 h 30 min |
| 2026-03-06 16:13 UTC | SPOT Hosted - Network Service Degradation | resolved | minor | 4 h 34 min |
| 2026-02-19 01:11 UTC | SPOT Corporate - Phone System Service | resolved | major | 36 h 57 min |
| 2025-11-06 11:30 UTC | SPOT Hosted - Database Service Degradation | resolved | major | 6 h 16 min |
| 2025-10-03 22:45 UTC | SPOT Corporate - Corporate Services Degraded | resolved | major | 5 h 29 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 Xplor with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"xplor"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}