Is Push Security down?
Last checked 8m agoNo incidents right now.
Push Security is operational right now. Last checked 8m ago; the most recent incident resolved 35d ago.
Real-time Push Security status, recent outages, and incident history — pulled directly from Push Security's official status page at https://status.pushsecurity.com every 5 minutes. Pingoru tracks 6 Push Security services and has captured 2 incidents in the last 90 days (98.52% uptime). Get email, Slack, Discord, or webhook alerts the moment Push Security reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Browser extension
Timeline · 3 updates
- identified · Jun 24, 2026, 07:15 PM UTC
Status: Identified We are investigating an issue affecting the App banners feature that results in banners failing to appear consistently in Edge. This issue occurs when Edge applies energy saving settings to tabs that haven’t been used recently, putting them to sleep. When this happens, the Push extension cannot consistently communicate with any Edge browser tabs, causing delayed or intermittent firing of controls. We are working to identify whether any other controls besides App banners are also impacted by this issue, and will update this page with more information. We have already identified a solution to this issue and sent v2.36.60 of the Push extension to the extension stores for release, pending the normal review process. Affected components Browser extension (Degraded performance)
- identified · Jun 25, 2026, 11:47 AM UTC
Status: Identified After further investigation, we have confirmed that the impact is not limited to App banners. When the Push extension goes into a degraded state where it has lost communication with tabs using Edge energy saver mode, the following Push capabilities could also work intermittently or be delayed in firing. Controls: • Phishing tool detection • Cloned login page detection • Password protection • Stolen credential detection • Strong password enforcement • MFA enforcement • Password logging prevention • Malicious copy and paste detection • App banners • File upload blocking • Clipboard blocking • Custom detections Telemetry: • Password login detection • FedCM login detection • MFA data collection • File uploads This issue was first introduced in v2.36.17 of the Push extension and has been fixed in the upcoming release v2.36.60. Note: This issue only impacts Edge browsers. Other browsers are not affected. Self-remediation option: We recommend you disable energy saving features in Edge to avoid tabs being put to sleep. This will serve as a workaround until the new version of the extension is available. Affected components Browser extension (Degraded performance)
- resolved · Jun 26, 2026, 01:18 AM UTC
Status: Resolved Version 2.36.60 of the Push extension became available at 1:18am UTC on the Chrome store, which contains the fix for this issue. A full writeup of the root cause will follow. Affected components Browser extension (Operational)
Latest: Status: Resolved Version 2.36.60 of the Push extension became available at 1:18am UTC on the Chrome store, which contains the fix for this issue. A full writeup of the root cause w…
-
- Data ingestionThird party componentsData deliveryAdmin consolePlatform
Timeline · 1 update
- resolved · May 26, 2026, 03:15 PM UTC
Status: Resolved The Push service experienced a 15-minute disruption. Security controls continued to work normally during this time. However, any new detection events and browser activity events that occurred during this 15-minute time period were lost and cannot be backfilled. We'll post a full postmortem soon. Affected components Third party components (Operational) Data delivery (Operational) Data ingestion (Operational) Admin console (Operational) Platform (Operational)
Latest: Status: Resolved The Push service experienced a 15-minute disruption. Security controls continued to work normally during this time. However, any new detection events and browser a…
-
- Started Jun 26, 2026, 01:18 AM UTC · Resolved Jun 26, 2026, 01:18 AM UTC · —
- Brief service disruption ResolvedStarted May 26, 2026, 03:15 PM UTC · Resolved May 26, 2026, 03:15 PM UTC · —