Real-time status check for Burp Suite. See if it's just you or everyone experiencing issues.
Burp Suite by PortSwigger is the industry-standard web application security testing platform used by penetration testers worldwide.
Category: Security Tools | Website: portswigger.net
ipconfig /flushdns or sudo systemd-resolve --flush-caches.Burp Suite by PortSwigger is the industry-standard web application security testing platform. The free Community Edition is widely used for learning; the paid Professional and Enterprise editions are standard tools for professional pentesters and bug bounty hunters. Burp's interception proxy, Repeater, Intruder, and BApp Store extensions form the daily toolkit for web app security testing.
When PortSwigger's services are down, multiple things can be affected: portswigger.net (main site, account, license verification), BApp Store (extensions repository), Web Security Academy (learning platform with labs), Burp Collaborator (out-of-band testing infrastructure), and license activation servers. Burp itself runs locally on your machine, so the application keeps working during many PortSwigger outages — but features that depend on PortSwigger backend (Collaborator, BApp updates, license checks for Professional users) may fail.
For status verification, status.portswigger.net shows component-level status. The @PortSwigger Twitter account posts updates. For Professional users specifically, license activation issues during outages are a known frustration — PortSwigger generally extends grace periods automatically during their outages.
During pentest engagements, Burp is critical-path tooling. Burp itself runs locally so most functionality continues during PortSwigger outages, but Collaborator-dependent testing (blind XSS, OOB SQLi, SSRF detection) needs alternatives. Have Interactsh or self-hosted Collaborator configured before engagements start.
Bug bounty hunters use Burp Pro extensively. Outages affecting BApp Store updates or Collaborator can interrupt active hunting sessions. Have backup OOB testing tools ready; rely on already-installed extensions during BApp Store outages.
The Academy hosts free hands-on labs for web security learning. When the Academy is down, structured learning is interrupted. Have downloaded labs (DVWA, OWASP Juice Shop) for offline practice during Academy outages.
Burp Pro license activation depends on PortSwigger backend. New activations during outages may fail. Existing installations continue working (license caches locally). For teams: install on machines with verified license activation before depending on it for time-bounded engagements.
Burp Enterprise (the CI/CD version) integrates with build pipelines. Outages affecting the Enterprise infrastructure can halt scheduled scans. Have monitoring on scan completion; alert if scans do not run as expected.
Hosted Collaborator is convenient but creates dependency on PortSwigger infrastructure. For serious work, self-hosted Collaborator (Pro feature) or Interactsh as backup is the right pattern.
Burp updates can introduce regressions or compatibility issues. During time-bounded engagements, stick with the version you started with. Update between engagements after testing the new version on your usual workflows.
BApp extensions sometimes have complex configurations. Export your configurations periodically so re-installation (after outage, hardware change, version update) restores your full setup quickly.
Burp project files contain extensive engagement data. Storing only on cloud-synced folders creates dependency on the sync service being available. Keep local copies; sync as backup, not primary storage.
Before reporting issues to PortSwigger support, check status.portswigger.net and Twitter — if the issue is widespread, it is already known. Report only when your issue appears unique to your installation.
For Professional users, having Community Edition installed on a separate machine (or VM) provides a backup workflow during license activation issues. Most basic functionality works in Community.