Vendor Status Watch

← all vendors

Doit status history

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

2incidents, last 30 days
4incidents, last 90 days
21incidents on record
Incidents per week, last 12 weeks:

How long do Doit incidents last?

46.8 hmedian incident duration21 measured
11.2 days90th percentile1 in 10 ran longer
7.5 hmedian, major/critical only1 incident

From 21 incidents with a vendor-posted start and resolve time. Longest on record: Investigating incorrect April AWS cost data for some CloudHealth-managed customers — 40.8 days (2026-05-18 13:05 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 (21)

StartedIncidentStatusImpactDuration
2026-09-11 11:19 UTCCost anomalies showing stale excess cost and statusresolvedminor2 d 9 h
2026-09-01 16:07 UTCGoogle Cloud issue [ONGOING]: Multiple Google Cloud servicesresolvednone25 h 15 min
2026-07-17 10:13 UTCAWS billing data issue causing inaccurate cost signals in DoiT Cloud Intelligenceresolvedminor46 h 48 min
2026-06-26 23:12 UTCGeneral issue with opening GCP Expert Inquiry tickets from the DCI Consoleresolvedminor37 h 50 min
2026-05-18 13:05 UTCInvestigating incorrect April AWS cost data for some CloudHealth-managed customersresolvedminor40 d 20 h
2026-05-08 11:49 UTCAWS missing dataresolvednone5 d 5 h
2026-04-06 13:39 UTCAWS missing dataresolvedminor4 d 0 h
2026-03-27 12:02 UTCIntermittent AWS ingestion issue affecting subset of DCI customersresolvedminor4 d 4 h
2026-03-26 09:58 UTCAWS missing dataresolvednone58 min
2026-03-06 16:26 UTCGCP Data Delivery Delays for billing exports to BigQueryresolvedminor2 d 15 h
2026-02-16 19:43 UTCInaccurate AWS Cost Dataresolvedminor11 d 5 h
2026-02-16 08:31 UTCDelayed GCP data delivery of cost and usage since February 11, 2026resolvedminor2 d 22 h
2026-01-13 12:26 UTCDelayed GCP cost and usage data updates since January 10, 2026resolvedminor7 d 1 h
2026-01-03 00:02 UTCSubset of public APIs are unavailableresolvedmajor7 h 32 min
2025-12-11 12:23 UTCSign-in via Magic Link Unavailableresolvednone4 h 16 min
2025-12-08 14:15 UTCBilling profiles unavailable in DoiT Consoleresolvedminor44 h 33 min
2025-12-02 09:40 UTCOkta SSO sign-in issue impacting access to the DoiT consoleresolvedminor19 h 48 min
2025-11-18 12:51 UTCDoiT Console: Degraded availability due to third‑party CDNresolvedminor19 h 32 min
2025-10-23 08:58 UTCBigQuery Lens: Incorrect Storage Metricsresolvedminor20 d 6 h
2025-10-23 05:06 UTCinvestigating an increased level of 500 errors for customersresolvednone7 h 05 min
2025-08-31 10:10 UTCEmail Delivery Disruptionresolvedminor4 h 55 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 Doit with the template

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

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