glitchmap

HashiCorp

Operational

All checks pass. Checks: 3 · Vendor incidents: 2

Is HashiCorp down? — short answer →

Holding for 1d

Subscribe in Telegram

100.00%
Uptime · 24 hours
100.00%
Uptime · 7 days
100.00%
Uptime · 30 days
392ms
Latency
2026-08-25 — —2026-08-26 — —2026-08-27 — —2026-08-28 — —2026-08-29 — —2026-08-30 — —2026-08-31 — —2026-09-01 — —2026-09-02 — —2026-09-03 — —2026-09-04 — —2026-09-05 — —2026-09-06 — —2026-09-07 — —2026-09-08 — —2026-09-09 — —2026-09-10 — —2026-09-11 — —2026-09-12 — —2026-09-13 — —2026-09-14 — —2026-09-15 — —2026-09-16 — —2026-09-17 — —2026-09-18 — —2026-09-19 — —2026-09-20 — —2026-09-21 — —2026-09-22 — —2026-09-23 — —2026-09-24 — —2026-09-25 — —2026-09-26 — —2026-09-27 — 100.00%2026-09-28 — 100.00%2026-09-29 — 100.00%2026-09-30 — 100.00%2026-10-01 — 100.00%2026-10-02 — 100.00%2026-10-03 — 100.00%2026-10-04 — 100.00%2026-10-05 — 100.00%2026-10-06 — 100.00%2026-10-07 — 100.00%2026-10-08 — 100.00%2026-10-09 — 100.00%2026-10-10 — 100.00%2026-10-11 — 100.00%2026-10-12 — 100.00%2026-10-13 — 100.00%2026-10-14 — 100.00%2026-10-15 — 100.00%2026-10-16 — 100.00%2026-10-17 — 100.00%2026-10-18 — 100.00%2026-10-19 — 100.00%2026-10-20 — 100.00%2026-10-21 — 100.00%2026-10-22 — 100.00%2026-10-23 — 100.00%2026-10-24 — 100.00%2026-10-25 — 100.00%2026-10-26 — 100.00%2026-10-27 — 100.00%2026-10-28 — 100.00%2026-10-29 — 100.00%2026-10-30 — 100.00%2026-10-31 — 100.00%2026-11-01 — 100.00%2026-11-02 — 100.00%2026-11-03 — 100.00%2026-11-04 — 100.00%2026-11-05 — 100.00%2026-11-06 — 100.00%2026-11-07 — 100.00%2026-11-08 — 100.00%2026-11-09 — 100.00%2026-11-10 — 100.00%2026-11-11 — 100.00%2026-11-12 — 100.00%2026-11-13 — 100.00%2026-11-14 — 100.00%2026-11-15 — 100.00%2026-11-16 — 100.00%2026-11-17 — 100.00%2026-11-18 — 100.00%2026-11-19 — 100.00%2026-11-20 — 100.00%2026-11-21 — 100.00%2026-11-22 — 100.00%
Last 90 days today
100%
Availability and latency. Hover for exact values.

Checks

3
dns DNS Passing
tls TLS certificate Passing
web Website / API Passing

Not working for you?

Tell us what exactly is broken. Reports are counted separately from our own checks and do not change the status on this page.

Incident history

10
Partial outage Status raised from the vendor's official page 20.11 16:10 · 6h 54m Degraded Status raised from the vendor's official page 17.11 10:56 · 1h 59m Degraded Status raised from the vendor's official page 15.11 19:13 · 2h 15m Degraded Status raised from the vendor's official page 15.11 05:28 · 6h 5m Partial outage Status raised from the vendor's official page 14.11 04:18 · 19m Partial outage Status raised from the vendor's official page 14.11 03:28 · 34m Partial outage Status raised from the vendor's official page 06.11 15:11 · 5m Degraded Status raised from the vendor's official page 05.11 08:16 · 1h 50m Partial outage Status raised from the vendor's official page 22.10 17:16 · 2h 50m Partial outage Status raised from the vendor's official page 13.10 16:06 · 20m

Measurements and sources

glitchmap checks public service endpoints and uses official status reports when available. A passing check confirms that endpoint only; it does not test every feature or your connection.

How we check

Official status page

Operational

Official status data source

New email and password account creation is no longer supported monitoring 20.11 19:31
Temporary limitations for users on Free Subscription monitoring 20.11 22:58

Incident titles come from the vendor and are shown as published