Read the quickstart

System status

Live status of every Gatepost component, with 90 days of history. Incidents are posted here within 10 minutes of being confirmed.

All systems operationalUpdated 13 September 2026, 12:40 UTC
Ingest: Europe collectorsFrankfurt, Amsterdam, Helsinki, Warsaw
99.97%90-day uptime
Ingest: Russia and CIS collectorsMoscow, Saint Petersburg, Almaty
99.99%90-day uptime
Ingest: Middle East collectorsDubai, Tel Aviv
100%90-day uptime
Ingest: Asia-Pacific collectorsSingapore, Tokyo, Sydney
99.98%90-day uptime
Ingest: Americas collectorsVirginia, Oregon, São Paulo
100%90-day uptime
ConsoleDashboards, session traces, alerts configuration
99.94%90-day uptime
Alerts and webhooksEmail, Slack, Telegram, HTTP webhooks
99.91%90-day uptime
Read APIMetrics export and integrations
100%90-day uptime
SDK distributionPackage repositories and CLI downloads
100%90-day uptime
16 June 2026Today

Incident history

Times are UTC. Post-incident reviews are sent to affected customers by email.

Delayed alert notifications

4 September 2026, 09:12 to 10:03 UTC. Alerts and webhooks. Resolved.

  1. Monitoring detected alert evaluation lagging behind ingest by more than 5 minutes.
  2. Cause identified: a queue consumer restarted in a loop after a configuration deploy. Deploy rolled back.
  3. Backlog processing. Alerts that fired during the delay were delivered late but not lost.
  4. Alert latency back under 30 seconds. Incident closed. Ingest and the console were not affected.

Elevated ingest latency at Europe collectors

27 August 2026, 16:48 to 17:29 UTC. Europe collectors. Resolved.

  1. Acknowledgement latency at two European collectors rose from under 100 ms to 2 to 4 seconds. Batches were still accepted; no data was lost.
  2. Traffic from the affected collectors shifted to neighbouring European collectors.
  3. Cause identified: an upstream network provider maintenance introduced packet loss on one transit path.
  4. Path restored, latency normal, traffic returned. SDK retries covered the window for devices that saw timeouts.

Console slow to load session traces

14 July 2026, 11:05 to 12:50 UTC. Console. Resolved.

  1. Session trace pages took 10 to 20 seconds to load for projects with more than 50 million sessions a month.
  2. Cause identified: a query planner regression after a database upgrade chose a poor index for large projects.
  3. Query hint deployed as a workaround. Load times back under 2 seconds.
  4. Verified for all affected projects. A permanent fix shipped on 16 July.

Scheduled maintenance: TLS certificate rotation, Asia-Pacific collectors

22 June 2026, 02:00 to 02:35 UTC. Asia-Pacific collectors. Completed.

  1. Collectors were rotated out of service one at a time for certificate renewal. Devices retried against the remaining collectors in the region.
  2. All collectors back in service with the new certificates. No customer action was required.

Older incidents

Before the 90-day window.

  1. Read API returned 500 for metrics export requests with more than 10,000 rows, 38 minutes.
  2. SDK distribution: package repository unavailable for 22 minutes during a storage migration.
  3. Console sign-in delayed by identity provider outage, 1 hour 14 minutes. Ingest unaffected.