Gemfury status history
Current state: operational — “All Systems Operational” per https://status.fury.co (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Gemfury incidents last?
From 10 incidents with a vendor-posted start and resolve time. Longest on record: AWS outage effects — 12.7 h (2025-10-20 15:59 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 (10)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-09 13:38 UTC | Elevated error rates for badge service | resolved | major | 2 h 08 min |
| 2026-05-20 13:20 UTC | Investigating elevated repo errors | resolved | minor | 2 h 35 min |
| 2026-03-25 07:44 UTC | Elevated errors for uploads and asynchronous work | resolved | minor | 46 min |
| 2026-03-24 16:34 UTC | Job processing delays & errors | resolved | minor | 2 h 05 min |
| 2026-03-16 15:41 UTC | Elevated errors | resolved | minor | 1 h 41 min |
| 2026-02-22 04:59 UTC | Elevated errors | resolved | minor | 1 h 51 min |
| 2026-02-09 11:21 UTC | Elevated errors & timeouts | resolved | minor | 4 h 59 min |
| 2025-10-20 15:59 UTC | AWS outage effects | postmortem | minor | 12 h 40 min |
| 2025-10-20 10:15 UTC | AWS outage effects | resolved | none | 26 min |
| 2025-09-18 15:37 UTC | Elevated error rates | resolved | minor | 1 h 51 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 Gemfury with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"gemfury"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}