Guardsquare logo

Is Guardsquare Down?

SaaSLive status, outages, and incident history

No. Guardsquare is up right now.

Every monitored Guardsquare system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Guardsquare breaks

Guardsquare is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Guardsquare status page
How we know: the official Guardsquare status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Guardsquare Status Summary

As of 21:56 UTC on 9 November 2026, Guardsquare is operational. PulsAPI checked Guardsquare's official status page and found 7 of 7 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.78% uptime for Guardsquare, counting degraded performance as up. The latest incident, "Preventive measures against (CVE-2026-109618 & CVE-2026-109619)", was on Oct 21, 2026 and lasted 3h 55m.

Cite as: PulsAPI, “Guardsquare status”, checked 9 November 2026, 21:56 UTC. https://www.pulsapi.com/services/guardsquare

Guardsquare Component Status

The main Guardsquare systems on this page. All 7 are operational right now.

7operational
App attestation
Operational
Application security testing
Operational
Dashboard UI
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Data ingestion, Guided protection workflow, Monitoring API, Webhook calls.

See all of them free

Component statuses may change independently during partial outages.

Recent Guardsquare Outages & Incidents

Incident history from the official Guardsquare status page, including resolution updates.

Preventive measures against (CVE-2026-109618 & CVE-2026-109619)Resolved Oct 21, 2026 · 3h 55mResolved

**Official Security Advisory** Upon learning of the vulnerabilities we immediately identified the external facing services within our infrastructure that were potentially vulnerable to CVE-2026-109618 & CVE-2026-109619. As a precaution, we temporarily took the affected services offline until the official patches were available, applied them immediately, and restored operations under continuous security monitoring. We have completed a full impact analysis across our infrastructure. We found no evidence of compromise or unauthorized access related to these vulnerabilities. There's no customer impact and no action required on your side. --- [2026-10-21T18:01:13Z] (resolved) We've successfully applied all necessary patches to our infrastructure. --- [2026-10-21T14:06:10Z] (investigating) We have temporarily taken our platform offline to safely deploy critical security patches addressing CVE-2026-109618 and CVE-2026-109619.

Monitoring api intermittently errors or times outResolved Sep 1, 2026 · 3h 2mResolved

We've gotten confirmation from our cloud vendor that this issue can only happen in the 17 hour period around the end of the month. In addition we will take measures to prevent this issue on our side as well. --- [2026-09-01T12:46:55Z] (investigating) We're investigating an issue that can cause requests to the monitoring api to fail or time-out intermittently. We suspect it is due to a communication problem with the database and are working with our cloud vendor to resolve this.

Increased attestation token issuance error rateResolved Aug 19, 2026 · 3h 37mResolved

The issue is fully resolved. We will reach out to affected customers. --- [2026-08-20T07:42:51Z] (identified) The issue is caused by a periodic rotation of internal encryption keys being generated with a wrong length. We are working on a fix to resolve the issue. --- [2026-08-20T07:42:51Z] (investigating) We have noticed an increase in error rates in our attestation service that can cause an increase in offline tokens.

Guardsquare Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Guardsquare incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 11100.00% average · 2 days with incidentsNov 9

Going further back: Guardsquare uptime by month and every recorded Guardsquare outage.

Live Guardsquare Outage Reports

Problems reported by engineers using Guardsquare. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Guardsquare problems reported yet.

Something wrong with Guardsquare on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Guardsquare

Guardsquare publishes a public status page at status.guardsquare.com covering 6 components, including Dashboard UI, Application security testing and Webhook calls. PulsAPI tracks Guardsquare outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Guardsquare uptime at 99.78%. Response times, incident history, and SLA tracking for Guardsquare are available on the PulsAPI dashboard.

Guardsquare Status FAQ

Is Guardsquare down right now?

The verdict at the top of this page comes from the latest poll of the official Guardsquare status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Guardsquare is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Guardsquare recovers.

How do I check Guardsquare uptime history?

PulsAPI tracks Guardsquare uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.78%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Guardsquare changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Guardsquare outages?

PulsAPI reads the official Guardsquare status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Guardsquare components?

Yes. PulsAPI monitors 7 individual Guardsquare components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Guardsquare goes down?

Yes. Create a free account and subscribe to Guardsquare: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Guardsquare to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Guardsquare problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Guardsquare?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Guardsquare plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Guardsquare with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services