Bluefin status history
Current state: degraded — “Minor Service Outage” per https://status.bluefin.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Bluefin incidents last?
From 23 incidents with a vendor-posted start and resolve time. Longest on record: Customer Funding Advisory – Processor — 43.5 h (2026-01-26 17:09 UTC). Excluded, never estimated: 1 still open / no resolve time. 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 (24)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 09:40 UTC | Intermittent Interruption | investigating | major | open |
| 2026-09-02 15:49 UTC | Intermittent Interruption | resolved | none | 3 h 17 min |
| 2026-08-25 14:51 UTC | Processing issue | resolved | major | 1 h 08 min |
| 2026-08-25 14:06 UTC | Processing issue | resolved | major | 28 min |
| 2026-08-07 17:00 UTC | Outage update - investigating | resolved | minor | 55 min |
| 2026-07-28 13:31 UTC | P2PEManager Issue | resolved | minor | 43 min |
| 2026-07-09 14:24 UTC | Service Issue | resolved | none | 31 min |
| 2026-05-28 18:23 UTC | Intermittent processing issue on PCX - Issue with 3rd party service provider | resolved | major | 17 h 52 min |
| 2026-03-16 16:38 UTC | Service Issue ShieldConex Tulsa Transaction | resolved | none | 1 h 45 min |
| 2026-03-03 15:28 UTC | Customer Funding Advisory – Federal Reserve | resolved | none | 4 h 30 min |
| 2026-02-08 08:18 UTC | Service Issue | resolved | minor | 1 h 20 min |
| 2026-02-02 22:33 UTC | 3rd Party Incident | resolved | none | 11 h 43 min |
| 2026-01-26 17:09 UTC | Customer Funding Advisory – Processor | resolved | none | 43 h 30 min |
| 2026-01-21 17:59 UTC | Intermittent Interruption | resolved | major | 1 h 05 min |
| 2025-12-29 17:25 UTC | 3rd Party Incident | resolved | major | 12 h 10 min |
| 2025-12-12 18:17 UTC | Investigating reports of decryption failures | resolved | minor | 5 h 18 min |
| 2025-11-01 03:23 UTC | ShieldConex Partial Outage | resolved | minor | 7 h 43 min |
| 2025-10-20 14:14 UTC | Phone System Outage | resolved | minor | 8 h 15 min |
| 2025-10-19 11:33 UTC | Processing issue | resolved | none | 0 min |
| 2025-10-15 17:10 UTC | Phone System | resolved | major | 5 h 47 min |
| 2025-09-12 14:16 UTC | Payconex Processing issue | resolved | minor | 6 h 21 min |
| 2025-09-05 15:45 UTC | Delayed Batch Settlement Notifications from PayConex | resolved | none | 3 h 35 min |
| 2025-08-25 12:48 UTC | Processing issue | resolved | none | 13 min |
| 2025-08-21 11:07 UTC | 3rd Party Incident | resolved | major | 32 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 Bluefin with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"bluefin"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}