User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
pushsecurity.com · Cloud & developer
Is Push Security down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → pushsecurity.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 170 ms · 5 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 222 ms | 0 |
| 03:30 | 0 | 0.0 | 204 ms | 0 |
| 03:45 | 0 | 0.0 | 314 ms | 0 |
| 04:00 | 0 | 0.0 | 284 ms | 0 |
| 04:15 | 0 | 0.0 | 272 ms | 0 |
| 04:30 | 0 | 0.0 | 740 ms | 0 |
| 04:45 | 0 | 0.0 | 207 ms | 0 |
| 05:00 | 0 | 0.0 | 228 ms | 0 |
| 05:15 | 0 | 0.0 | 331 ms | 0 |
| 05:30 | 0 | 0.0 | 162 ms | 0 |
| 05:45 | 0 | 0.0 | 305 ms | 0 |
| 06:00 | 0 | 0.0 | 369 ms | 0 |
| 06:15 | 0 | 0.0 | 300 ms | 0 |
| 06:30 | 0 | 0.0 | 264 ms | 0 |
| 06:45 | 0 | 0.0 | 335 ms | 0 |
| 07:00 | 0 | 0.0 | 158 ms | 0 |
| 07:15 | 0 | 0.0 | 378 ms | 0 |
| 07:30 | 0 | 0.0 | 198 ms | 0 |
| 07:45 | 0 | 0.0 | 964 ms | 0 |
| 08:00 | 0 | 0.0 | 262 ms | 0 |
| 08:15 | 0 | 0.0 | 161 ms | 0 |
| 08:30 | 0 | 0.0 | 262 ms | 0 |
| 08:45 | 0 | 0.0 | 209 ms | 0 |
| 09:00 | 0 | 0.0 | 210 ms | 0 |
| 09:15 | 0 | 0.0 | 320 ms | 0 |
| 09:30 | 0 | 0.0 | 324 ms | 0 |
| 09:45 | 0 | 0.0 | 125 ms | 0 |
| 10:00 | 0 | 0.0 | 387 ms | 0 |
| 10:15 | 0 | 0.0 | 142 ms | 0 |
| 10:30 | 0 | 0.0 | 339 ms | 0 |
| 10:45 | 0 | 0.0 | 252 ms | 0 |
| 11:00 | 0 | 0.0 | 196 ms | 0 |
| 11:15 | 0 | 0.0 | 127 ms | 0 |
| 11:30 | 0 | 0.0 | 367 ms | 0 |
| 11:45 | 0 | 0.0 | 161 ms | 0 |
| 12:00 | 0 | 0.0 | 136 ms | 0 |
| 12:15 | 0 | 0.0 | 312 ms | 0 |
| 12:30 | 0 | 0.0 | 150 ms | 0 |
| 12:45 | 0 | 0.0 | 117 ms | 0 |
| 13:00 | 0 | 0.0 | 230 ms | 0 |
| 13:15 | 0 | 0.0 | 216 ms | 0 |
| 13:30 | 0 | 0.0 | 2861 ms | 0 |
| 13:45 | 0 | 0.0 | 817 ms | 0 |
| 14:00 | 0 | 0.0 | 1016 ms | 0 |
| 14:15 | 0 | 0.0 | 151 ms | 0 |
| 14:30 | 0 | 0.0 | 1469 ms | 0 |
| 14:45 | 0 | 0.0 | 345 ms | 0 |
| 15:00 | 0 | 0.0 | 170 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Push Security status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Push Security yet. Outages of 10 minutes or more get their own page here.
Having trouble with Push Security?
One report per service every 10 minutes from this network. No account.
Follow Push Security
Get an email when Push Security goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Push Security alerts to Slack, Discord or a webhook — free.
Questions
Is Push Security down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Push Security not working for me but the status is fine. What now?
If Push Security is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Push Security's side.
How does Damn is it down decide Push Security's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Push Security checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.