Damn, is it down?

All services / Cloud & developer

gitguardian.com · Cloud & developer

Is GitGuardian down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

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 → gitguardian.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.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 80 ms · 1 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10146 ms16:1522:1504:1510:0016:00
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
04:1500.065 ms0
04:3000.069 ms0
04:4500.0138 ms0
05:0000.049 ms0
05:1500.057 ms0
05:3000.038 ms0
05:4500.0146 ms0
06:0000.063 ms0
06:1500.047 ms0
06:3000.044 ms0
06:4500.071 ms0
07:0000.057 ms0
07:1500.098 ms0
07:3000.0103 ms0
07:4500.036 ms0
08:0000.044 ms0
08:1500.050 ms0
08:3000.055 ms0
08:4500.061 ms0
09:0000.081 ms0
09:1500.042 ms0
09:3000.046 ms0
09:4500.046 ms0
10:0000.070 ms0
10:1500.042 ms0
10:3000.062 ms0
10:4500.041 ms0
11:0000.067 ms0
11:1500.083 ms0
11:3000.055 ms0
11:4500.065 ms0
12:0000.096 ms0
12:1500.050 ms0
12:3000.065 ms0
12:4500.081 ms0
13:0000.052 ms0
13:1500.0130 ms0
13:3000.0104 ms0
13:4500.058 ms0
14:0000.069 ms0
14:1500.075 ms0
14:3000.052 ms0
14:4500.0143 ms0
15:0000.075 ms0
15:1500.0140 ms0
15:3000.062 ms0
15:4500.081 ms0
16:0000.080 ms0

Reliability

Score 100/100 · grade A

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.

GitGuardian status badge Embed a live GitGuardian status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

GitGuardian status and 30-day uptime badge

Past outages

No outages on record for GitGuardian yet. Outages of 10 minutes or more get their own page here.

All GitGuardian outages · Every recent outage

Having trouble with GitGuardian?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is GitGuardian down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

GitGuardian not working for me but the status is fine. What now?

If GitGuardian 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 GitGuardian's side.

How does Damn is it down decide GitGuardian'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 GitGuardian checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.