Vendor Status Watch

← all vendors

Numerator status history

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

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

How long do Numerator incidents last?

34 minmedian incident duration3 measured
45 min90th percentile1 in 10 ran longer
39 minmedian, major/critical only2 incidents

From 3 incidents with a vendor-posted start and resolve time. Longest on record: Survey Response Errors — 45 min (2026-01-08 14:16 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 (3)

StartedIncidentStatusImpactDuration
2026-07-24 18:41 UTCDeployment Issueresolvednone14 min
2026-05-28 01:05 UTCService Outageresolvedcritical34 min
2026-01-08 14:16 UTCSurvey Response Errorsresolvedcritical45 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 Numerator with the template

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

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