Vendor Status Watch

← all vendors

PriceHubble status history

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

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

How long do PriceHubble incidents last?

2 minmedian incident duration5 measured
66 min90th percentile1 in 10 ran longer
6 minmedian, major/critical only4 incidents

From 5 incidents with a vendor-posted start and resolve time. Longest on record: Database capacity incident affecting Service Availability — 66 min (2026-05-30 13:20 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-08 08:00 UTCTemplates and Share link API degradationresolvedmajor11 min
2026-08-31 12:55 UTCIntermittent failures on Comparablesresolvedmajor2 min
2026-06-19 10:00 UTCOffers search API degradedresolvednone0 min
2026-05-30 13:20 UTCDatabase capacity incident affecting Service Availabilityresolvedcritical1 h 06 min
2026-05-13 08:30 UTCValuation API Outageresolvedmajor0 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 PriceHubble with the template

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

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