Vendor reports: degradedResolved · vendor status “resolved”Official status API

Unable to create new integration authentications

Reported by HackerOne · Identity & Security · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Jan 29, 2025, 10:55 UTC
Vendor's clock
Resolved
Feb 1, 2025, 00:21 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 d 13 h
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • HackerOne reports degraded: "Unable to create new integration authentications".[E1, E2]
  • The vendor marked it resolved at 2025-02-01 00:21 UTC.[E3, E7]

Affected products and regions

  • Components: HackerOne Integrations.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-02-01 00:21 UTC · summary s1, evidence ca5d2bd5dc4955d1

Evidence (7)
  1. E1HackerOne reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Unable to create new integration authentications". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-01-29 10:55 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: HackerOne Integrations. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-02-01 00:21 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: HackerOne Integrations

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

HackerOne is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jan 29, 2025, 10:55 UTCVendor-reported startVendor time
  2. Feb 1, 2025, 00:21 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.