Vendor Status Watch

← all vendors

Blend status history

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

2incidents, last 30 days
10incidents, last 90 days
29incidents on record
Incidents per week, last 12 weeks:

How long do Blend incidents last?

5.4 hmedian incident duration29 measured
21.4 h90th percentile1 in 10 ran longer
9.8 hmedian, major/critical only9 incidents

From 29 incidents with a vendor-posted start and resolve time. Longest on record: Internal reporting data pipelines — 5.5 days (2025-11-26 04:14 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 (29)

StartedIncidentStatusImpactDuration
2026-09-07 16:59 UTCBlend External APIresolvedmajor3 h 01 min
2026-09-04 20:27 UTCConnectivity Disruption between TotalExpert and Blendresolvedminor15 h 14 min
2026-08-13 14:05 UTCClosings flowing from Encompass to Blend via EPC and PDDresolvedminor5 h 49 min
2026-08-10 20:28 UTCEncompass Disclosure Delivery Errorsresolvedminor18 h 21 min
2026-07-31 14:19 UTCIssues affecting closing packages and disclosures through docusignresolvedmajor5 h 26 min
2026-07-29 03:09 UTCBlend platform production availability is restoredresolvedcritical15 h 51 min
2026-07-23 16:47 UTCEPD Encompass Integration - Experiencing delaysresolvedminor5 h 15 min
2026-07-22 16:38 UTCCLOSING - Users may be experiencing troubles sending closing Packages to Blendresolvedminor4 h 30 min
2026-06-22 16:37 UTCTwilio outageresolvednone3 h 19 min
2026-06-22 15:00 UTCCloudflare Outageresolvednone3 h 51 min
2026-06-10 17:06 UTCOngoing Investigation into Platform Performance Degradationresolvedminor4 h 56 min
2026-06-05 19:11 UTCService Notice: Integration Connectivity Disruption between Encompass and Blendresolvedmajor2 d 18 h
2026-05-13 15:21 UTCPipeline View Search Functionalityresolvednone34 min
2026-04-24 16:21 UTCEncompass (ICE) Degraded Performanceresolvedminor21 h 27 min
2026-04-09 16:26 UTC502 Error When Accessing Blend Beta Environmentsresolvedmajor3 h 40 min
2026-04-08 16:54 UTCTicket Delivery Delaysresolvednone21 h 16 min
2026-03-05 22:00 UTCDocument Generationresolvedminor6 h 21 min
2026-03-02 19:48 UTCAPI Gateway – Monitoring Updateresolvedminor3 h 07 min
2026-02-11 15:50 UTCeClose - Hybrid Closing Packages (manually tagged only)resolvedminor1 h 14 min
2026-01-20 18:35 UTCAPI Availabilityresolvedminor6 h 23 min
2026-01-20 15:13 UTCAPI Failuresresolvedmajor9 h 46 min
2026-01-14 13:38 UTCBlend Platform - Operationalresolvedmajor2 d 10 h
2026-01-13 20:23 UTCBlend - Unable to Accessresolvedcritical1 h 28 min
2025-11-26 04:14 UTCInternal reporting data pipelinesresolvedminor5 d 12 h
2025-11-25 16:40 UTCApplication Export latency (stuck) incidentresolvedminor4 h 21 min
2025-11-19 15:44 UTCIssues identified with AUS/DU/LPA requests in Blendresolvednone1 h 15 min
2025-11-03 16:37 UTCBlend Signing Room/eClose Outageresolvedminor1 h 17 min
2025-10-20 09:27 UTCMajor Amazon Web Services (AWS) Outageresolvedcritical12 h 10 min
2025-08-21 18:35 UTCOneSpan Envelope Service Provider outageresolvednone19 h 52 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 Blend with the template

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

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