Tight Outage History

Tight is up right now

Pingoru has recorded 8 incidents for Tight: 8 in the last 12 months and 0 in the last 90 days.

Source: status.tight.com

8incidents recorded
8last 12 months
0last 90 days
24 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Tight in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202610 of 744 (0%)
June 202620 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 550 (0%)

Incidents, newest first

Minor June 30, 2026 Tight API (Production) Degraded Performance 16m

Started Jun 30, 2026, 07:55 PM UTC· resolved Jun 30, 2026, 08:11 PM UTC

  1. investigating Jun 30, 2026, 07:55 PM UTC

    Tight API Integrations in the Production environment are experiencing degraded performance. We are dedicated to maintaining the highest possible uptime and are urgently investigating the issue.

  2. resolved Jun 30, 2026, 08:11 PM UTC

    The performance degradation was automatically resolved.

Read the full incident report →

Minor June 2, 2026 Tight API (Production) Partial Outage 8m

Started Jun 02, 2026, 11:38 PM UTC· resolved Jun 02, 2026, 11:46 PM UTC

  1. investigating Jun 02, 2026, 11:38 PM UTC

    Some Tight APIs are experiencing a partial outage in the Production environment . We are dedicated to maintaining the highest possible uptime and are urgently investigating the issue.

  2. resolved Jun 02, 2026, 11:46 PM UTC

    This outage was automatically restored.

Read the full incident report →

Minor March 16, 2026 Tight API DNS Issues –

Started Mar 16, 2026, 08:45 PM UTC· resolved Mar 16, 2026, 08:45 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major February 28, 2026 Tight Embeddable UI (Production) Partial Outage –

Started Feb 28, 2026, 04:18 AM UTC· resolved Feb 28, 2026, 04:18 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →