Bugcrowd status history

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

1incidents, last 30 days

1incidents, last 90 days

3incidents on record

Incidents per week, last 12 weeks:

Get Bugcrowd alerts in your Slack — free template RSS for Bugcrowd

How long do Bugcrowd incidents last?

36 minmedian incident duration3 measured

3.9 h90th percentile1 in 10 ran longer

30 minmedian, major/critical only2 incidents

From 3 incidents with a vendor-posted start and resolve time. Longest on record: Asynchronous job processing delayed — 3.9 h (2026-09-15 06:07 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)

Started	Incident	Status	Impact	Duration
2026-09-15 06:07 UTC	Asynchronous job processing delayed	resolved	minor	3 h 52 min
2026-02-26 05:08 UTC	Temporary login issues for Hackers	resolved	major	24 min
2025-10-22 00:14 UTC	Tracker portal is experiencing issues	resolved	major	36 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 Bugcrowd with the template

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

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