Real-time status check for HackerOne. See if it's just you or everyone experiencing issues.
HackerOne is the leading bug bounty platform connecting ethical hackers with organizations to find and fix security vulnerabilities for rewards.
Category: Bug Bounty | Website: www.hackerone.com
ipconfig /flushdns or sudo systemd-resolve --flush-caches.HackerOne is the largest bug bounty and vulnerability disclosure platform — connects ethical hackers with organisations running bug bounty or vulnerability disclosure programs. Used by major companies (Google, GitHub, Microsoft, Department of Defense, many more) for managed vulnerability intake. Bug bounty hunters use HackerOne to find programs, submit vulnerabilities, and receive bounties.
When HackerOne is down, the impact splits between hunters and program owners: hunters cannot submit reports (in-progress findings stuck in browser), cannot access program scope or credentials, cannot receive bounty notifications. Program owners cannot triage incoming reports, cannot communicate with hunters, may miss time-bounded disclosures. Both sides have time-sensitivity considerations during outages.
For status verification: HackerOne does not publish a comprehensive public status page comparable to AWS or GitHub. Status updates typically come via the @hacker0x01 Twitter account, in-app notifications when accessible, and direct hunter/triager community channels. The lack of a comprehensive status page means using this checker plus Twitter is often the best status verification approach.
Hunters use HackerOne for program research, scope checking, report submission. Outages disrupt active hunting. Have multiple platforms in your routine (HackerOne + Bugcrowd + Intigriti) so platform outages do not stop hunting entirely.
Time-bounded disclosure (90-day deadlines from CERT/CC, scheduled coordinated disclosure with vendors) requires reliable platform access. Outages near disclosure deadlines need backup paths — direct vendor contact, public disclosure if necessary.
Security teams running bug bounty programs use HackerOne for incoming report triage. Outages delay triage and hunter communication. Have direct contact paths (security@ email) as backup for time-sensitive vulnerabilities.
Hunters check program scope before testing. During outages, scope cannot be verified — testing without confirmed scope risks out-of-scope activity. Document scope before sessions to enable testing during outages.
HackerOne handles bounty payments. Outages affect payment processing visibility. Payments queued during outages are typically processed when service resumes; documented bounty award amounts can be verified when access returns.
Browser drafts can be lost during outages, browser crashes, or session timeouts. Draft reports in local markdown files, copy to HackerOne for submission. Local drafts also enable better formatting, version control, and review.
HackerOne is one of several bug bounty platforms (Bugcrowd, Intigriti, Synack, Open Bug Bounty, YesWeHack). Hunters depending entirely on HackerOne miss programs on other platforms and lose access during HackerOne outages. Maintain accounts on multiple platforms.
Last-minute submissions fail when platforms have issues. For time-bounded disclosures (CERT 90-day deadlines, coordinated disclosure dates), submit with buffer time. The few-day buffer absorbs platform issues.
During HackerOne outages, scope cannot be verified live. Testing without confirmed current scope risks out-of-scope activity (legal and ethical issues). Document scope before each testing session; refer to local notes during platform outages.
Frustration during outages sometimes leads hunters to publicly disclose findings out of impatience. This violates responsible disclosure norms and harms hunter reputation. Wait for platform recovery; use direct vendor contact if needed for genuinely time-critical issues.
Hunter portfolio (resolved reports, bounties, reputation) is hosted on HackerOne. Periodic exports preserve your work history independent of platform availability. Useful for resume material and platform-portability.
domain/.well-known/security.txt with direct contact info.domain/.well-known/security.txt specifying how to report security vulnerabilities. Typically includes contact email, PGP key for encrypted communication, policy URL, and acknowledgment policy. Useful as direct disclosure path when platform-based disclosure is unavailable.