Tight Outage History

Tight is up right now

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

Source: status.tight.com

6incidents recorded
6last 12 months
0last 90 days
31 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
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 744 (0%)
November 202600 of 235 (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 →

Major 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 →

Major May 19, 2026 Tight API (Production) Partial Outage 9m

Started May 19, 2026, 06:23 PM UTC· resolved May 19, 2026, 06:32 PM UTC

  1. investigating May 19, 2026, 06:19 PM UTC

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

  2. resolved May 19, 2026, 06:32 PM UTC

    This outage was automatically restored.

Read the full incident report →

Minor March 16, 2026 Tight API DNS Issues 2h 20m

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

  1. investigating Mar 16, 2026, 06:25 PM UTC

    A DNS resolution failure at GoDaddy is causing a geographic-based partial outage affecting Tight users.

  2. resolved Mar 16, 2026, 08:45 PM UTC

    Tight is seeing restored behavior resolving the API's DNS.

Read the full incident report →

Major February 27, 2026 Tight Embeddable UI (Production) Partial Outage 10m

Started Feb 27, 2026, 04:08 PM UTC· resolved Feb 27, 2026, 04:18 PM UTC

  1. investigating Feb 28, 2026, 04:08 AM UTC

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

  2. resolved Feb 28, 2026, 04:18 AM UTC

    This outage was automatically restored.

Read the full incident report →

Major December 18, 2025 Tight API DNS Issues 1m

Started Dec 18, 2025, 02:35 PM UTC· resolved Dec 18, 2025, 02:37 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →