Status turngate.io

All systems operational

Checked every minute · updated 2026-09-27 21:11 UTC

Active notices

No active incidents or scheduled maintenance.

Components

Public website

turngate.io public website

Operational
90 days ago 100.00% uptime today

Turngate Application

Turngate application UI

Operational
90 days ago 99.99% uptime today
2026-07-24 Degraded performance
Down fromRestoredDurationDetail
2026-07-24 11:48 UTC2026-07-24 11:49 UTC1 min1 check with no response

API

Turngate REST API

Operational
90 days ago 99.94% uptime today
2026-08-14 Degraded performance
Down fromRestoredDurationDetail
2026-08-14 04:14 UTC2026-08-14 04:19 UTC5 minexpected status 200, got 500
2026-08-14 18:44 UTC2026-08-14 18:45 UTC1 minexpected status 200, got 500
2026-08-16 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-08-17 Degraded performance
Down fromRestoredDurationDetail
2026-08-17 08:46 UTC2026-08-17 08:47 UTC1 minexpected status 200, got 500
2026-08-18 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-08-19 Degraded performance
Down fromRestoredDurationDetail
2026-08-19 04:00 UTC2026-08-19 04:01 UTC1 minexpected status 200, got 500
2026-08-19 13:33 UTC2026-08-19 13:34 UTC1 minexpected status 200, got 500
2026-08-19 21:32 UTC2026-08-19 21:33 UTC1 minexpected status 200, got 500
2026-08-20 Partial outage
Down fromRestoredDurationDetail
2026-08-20 16:15 UTC2026-08-20 16:16 UTC1 minexpected status 200, got 500
2026-08-20 16:30 UTC2026-08-20 16:31 UTC1 minexpected status 200, got 500
2026-08-20 17:31 UTC2026-08-20 17:34 UTC3 minexpected status 200, got 500
2026-08-20 18:02 UTC2026-08-20 18:04 UTC2 minexpected status 200, got 500
2026-08-20 18:16 UTC2026-08-20 18:17 UTC1 minexpected status 200, got 500
2026-08-20 18:44 UTC2026-08-20 18:45 UTC1 minexpected status 200, got 500
2026-08-21 Degraded performance
Down fromRestoredDurationDetail
2026-08-21 17:01 UTC2026-08-21 17:02 UTC1 minexpected status 200, got 500
2026-08-21 17:58 UTC2026-08-21 17:59 UTC1 minexpected status 200, got 500
2026-08-21 18:32 UTC2026-08-21 18:33 UTC1 minexpected status 200, got 500
2026-08-21 21:46 UTC2026-08-21 21:47 UTC1 minexpected status 200, got 500
2026-08-24 Degraded performance
Down fromRestoredDurationDetail
2026-08-24 16:59 UTC2026-08-24 17:00 UTC1 minexpected status 200, got 500
2026-08-26 Degraded performance
Down fromRestoredDurationDetail
2026-08-26 18:18 UTC2026-08-26 18:19 UTC1 minexpected status 200, got 500
2026-08-27 Degraded performance
Down fromRestoredDurationDetail
2026-08-27 15:06 UTC2026-08-27 15:07 UTC1 minexpected status 200, got 500
2026-08-28 Degraded performance
Down fromRestoredDurationDetail
2026-08-28 16:32 UTC2026-08-28 16:33 UTC1 minexpected status 200, got 500
2026-08-31 Degraded performance
Down fromRestoredDurationDetail
2026-08-31 19:15 UTC2026-08-31 19:16 UTC1 minexpected status 200, got 500
2026-08-31 22:14 UTC2026-08-31 22:15 UTC1 minexpected status 200, got 500
2026-09-01 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-11 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-17 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-18 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-22 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-23 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-24 Degraded performance
Down fromRestoredDurationDetail
2026-09-24 18:17 UTC2026-09-24 18:18 UTC1 minexpected status 200, got 500
2026-09-27 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

Login / SSO

Authentication and single sign-on

Operational
90 days ago 99.99% uptime today
2026-07-14 Degraded performance
Down fromRestoredDurationDetail
2026-07-14 17:56 UTC2026-07-14 17:57 UTC1 min1 check with no response
2026-07-29 Partially degraded

A degradation was declared for this day, but no failed checks were recorded against this component.

YubiKey sign-in unavailable — full timeline →

2026-07-30 Partially degraded

A degradation was declared for this day, but no failed checks were recorded against this component.

YubiKey sign-in unavailable — full timeline →

2026-07-31 Partially degraded

A degradation was declared for this day, but no failed checks were recorded against this component.

YubiKey sign-in unavailable — full timeline →

2026-08-03 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-03 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-11 Partial outage

A degradation was declared for this day, but no failed checks were recorded against this component.

2026-09-13 Degraded performance

A degradation was declared for this day, but no failed checks were recorded against this component.

Alerting & notifications

Delivery of alerts, notifications and digests

Operational
90 days ago 100.00% uptime today
2026-07-22 Degraded

The service remained available and serving requests throughout, but was not behaving normally. A deployment or upgrade, a rate limit, or work running behind can all look like this.

FromUntilDurationDetail
2026-07-22 06:12 UTC2026-07-24 05:25 UTC47.2 hoursProcessing backlog above normal, reaching unprocessed data older than 24 hours at its worst

Alert and notification delivery delays — full timeline →

2026-07-23 Degraded

The service remained available and serving requests throughout, but was not behaving normally. A deployment or upgrade, a rate limit, or work running behind can all look like this.

FromUntilDurationDetail
2026-07-22 06:12 UTC2026-07-24 05:25 UTC47.2 hoursProcessing backlog above normal, reaching unprocessed data older than 24 hours at its worst

Alert and notification delivery delays — full timeline →

2026-07-24 Degraded

The service remained available and serving requests throughout, but was not behaving normally. A deployment or upgrade, a rate limit, or work running behind can all look like this.

FromUntilDurationDetail
2026-07-22 06:12 UTC2026-07-24 05:25 UTC47.2 hoursProcessing backlog above normal, reaching unprocessed data older than 24 hours at its worst

Data ingest

Collection and processing of integration data

Operational
90 days ago 100.00% uptime today