The Things Industries Outage History

The Things Industries is up right now

The Things Industries had 14 outages in the last 2 years totaling 147h 15m of downtime — averaging 0.6 incidents per month.

There were 14 The Things Industries outages since June 3, 2024 totaling 147h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.thethings.industries

Minor May 6, 2026

Issue with AWS-IOT integration in The Things Stack Cloud NAM1 Cluster

Detected by Pingoru
May 06, 2026, 10:43 AM UTC
Resolved
May 06, 2026, 05:30 PM UTC
Duration
6h 46m
Affected: North America 1 (nam1)
Timeline · 3 updates
  1. identified May 06, 2026, 10:43 AM UTC

    We have identified an issue causing increased failure rates in AWS IoT application package messages in The Things Stack Cloud NAM1 Cluster. Our engineering team is actively working on a resolution. Impact: Users may experience intermittent disruptions with AWS IoT integration during this time. We apologise for the inconvenience and will post updates here as we make progress.

  2. monitoring May 06, 2026, 04:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 06, 2026, 05:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 9, 2026

The Things Gateway Controller down for emergency maintenance

Detected by Pingoru
Jan 09, 2026, 03:16 PM UTC
Resolved
Jan 09, 2026, 04:13 PM UTC
Duration
56m
Timeline · 3 updates
  1. identified Jan 09, 2026, 03:16 PM UTC

    We're conducting emergency maintenance on the infrastructure running The Things Gateway Controller. This causes connectivity issues with The Things Indoor Gateway Pro.

  2. monitoring Jan 09, 2026, 04:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 09, 2026, 04:13 PM UTC

    The incident has been resolved. The Things Indoor Gateway Pro gateways are reconnecting. This may take some additional time due to reconnect backoffs.

Read the full incident report →

Minor December 19, 2025

Webhook failures in TTSC eu1 cluster

Detected by Pingoru
Dec 19, 2025, 04:53 PM UTC
Resolved
Dec 19, 2025, 04:53 PM UTC
Duration
—
Affected: Europe 1 (eu1)
Timeline · 3 updates
  1. investigating Dec 19, 2025, 02:50 PM UTC

    We are investigating reports about webhook failures in our eu1 cluster.

  2. monitoring Dec 19, 2025, 03:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 19, 2025, 04:53 PM UTC

    A significant increase in downlink queue operations within a short time window and this caused internal database connections to accumulate as each request waited for exclusive access to device resources. This connection buildup exhausted the available connection pool, resulting in degraded performance for other operations across the Application Server. Unrelated requests experienced increased latency and timeouts as they competed for the limited available connections. Measures were taken so that this incident do not happen again.

Read the full incident report →

Minor October 8, 2025

Webhooks failures in the TTSC eu1 cluster

Detected by Pingoru
Oct 08, 2025, 10:12 AM UTC
Resolved
Oct 09, 2025, 02:21 AM UTC
Duration
16h 9m
Affected: Europe 1 (eu1)
Timeline · 4 updates
  1. investigating Oct 08, 2025, 10:12 AM UTC

    We are investigating reports about webhook failures in the TTSC eu1 cluster.

  2. monitoring Oct 08, 2025, 10:57 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 09, 2025, 02:21 AM UTC

    This incident has been resolved.

  4. postmortem Oct 13, 2025, 01:57 PM UTC

    On October 7-8, 2025, the webhook ingestion service in our eu1 cluster experienced a degradation that led to an increase in processing errors. This resulted in delayed data delivery due to processing retries and, in a small number of cases, data loss after too many retries occurred. ‌ The issue was caused by a lock that, under certain conditions, could be held indefinitely because it was configured without an automatic expiration. This created a chain reaction where subsequent processes would wait for the lock while holding their Redis connections open. The accumulation of these waiting processes likely caused a rapid increase in Redis connections, which in turn impacted the performance of dependent services. ‌ Service was restored after deploying an update that adjusted the locking logic. To enhance future reliability, our follow-up actions include a review of similar code patterns and performing more heavy load tests on the webhook related services.

Read the full incident report →

Minor October 7, 2025

Webhooks failures in eu1

Detected by Pingoru
Oct 07, 2025, 05:51 PM UTC
Resolved
Oct 07, 2025, 07:12 PM UTC
Duration
1h 21m
Affected: Europe 1 (eu1)
Timeline · 3 updates
  1. investigating Oct 07, 2025, 05:51 PM UTC

    We are investigating reports about webhook failures in our eu1 cluster.

  2. monitoring Oct 07, 2025, 06:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 07, 2025, 07:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 19, 2025

Issue accessing entity pages in The Things Stack Console (nam1 cluster)

Detected by Pingoru
Jul 19, 2025, 05:36 AM UTC
Resolved
Jul 21, 2025, 06:58 AM UTC
Duration
2d 1h
Affected: North America 1 (nam1)
Timeline · 6 updates
  1. investigating Jul 19, 2025, 05:36 AM UTC

    We are currently investigating this issue.

  2. identified Jul 19, 2025, 06:46 AM UTC

    We are deploying a fix.

  3. monitoring Jul 19, 2025, 10:43 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. investigating Jul 19, 2025, 02:12 PM UTC

    We have increased the resources for the Proxy services to accommodate the spike in traffic. However, the issue still persists. Our team is continuing to investigate the root cause.

  5. monitoring Jul 20, 2025, 01:25 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Jul 21, 2025, 06:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 19, 2025

Issue accessing entity pages in The Things Stack Console

Detected by Pingoru
Jun 19, 2025, 12:23 PM UTC
Resolved
Jun 20, 2025, 12:57 PM UTC
Duration
1d
Affected: Europe 1 (eu1)Europe 2 (eu2)North America 1 (nam1)Australia 1 (au1)Asia 1 (as1)
Timeline · 4 updates
  1. investigating Jun 19, 2025, 12:23 PM UTC

    We are currently investigating this issue.

  2. identified Jun 20, 2025, 10:52 AM UTC

    We are deploying a fix.

  3. monitoring Jun 20, 2025, 11:22 AM UTC

    We have deployed a fix and we are monitoring.

  4. resolved Jun 20, 2025, 12:57 PM UTC

    We've received confirmation that the problem has been fixed. If issues persist, please reach out to [email protected]

Read the full incident report →

Minor May 14, 2025

Login Issues in the Console

Detected by Pingoru
May 14, 2025, 09:05 AM UTC
Resolved
May 14, 2025, 01:17 PM UTC
Duration
4h 12m
Affected: Europe 1 (eu1)Europe 2 (eu2)North America 1 (nam1)Australia 1 (au1)Asia 1 (as1)
Timeline · 4 updates
  1. investigating May 14, 2025, 09:05 AM UTC

    We are currently investigating an issue affecting a subset of customers who are seeing a blank page when attempting to log in to the Console. This appears to impact only certain clients. We will provide more information as we continue to investigate.

  2. identified May 14, 2025, 10:04 AM UTC

    We have identified the cause of the issue resulting in a blank screen during login for some users. A fix is being prepared and will be deployed shortly.

  3. monitoring May 14, 2025, 10:15 AM UTC

    A fix has been deployed to address the issue affecting the login screen. Affected users should now be able to access the Console normally. We are monitoring the situation to ensure full stability.

  4. resolved May 14, 2025, 01:17 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 24, 2025

Misleading license expiry notification

Detected by Pingoru
Apr 24, 2025, 11:00 AM UTC
Resolved
Apr 24, 2025, 11:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 24, 2025, 11:01 AM UTC

    We identified an issue where users were shown a notification stating that the license for The Things Stack Cloud was expiring soon. This message was incorrect and not related to any active subscriptions held by the users. The notification should not have been displayed and has since been resolved.

Read the full incident report →

Minor April 24, 2025

TTIG Pro cellular connectivity issues in United States and Canada

Detected by Pingoru
Apr 24, 2025, 08:37 AM UTC
Resolved
Apr 24, 2025, 08:53 AM UTC
Duration
16m
Affected: Cellular data for The Things Industries gateways
Timeline · 3 updates
  1. identified Apr 24, 2025, 08:37 AM UTC

    The Things Indoor Gateway Pros in United States and Canada that are (only) using the cellular backhaul may suffer from cellular connectivity issues. The underlying issue started at 05:47 UTC. The cause is an incident at our MVNO Soracom. See https://status.soracom.io/incidents/287968 for more up-to-date information.

  2. monitoring Apr 24, 2025, 08:52 AM UTC

    Most gateways are coming back online. We're monitoring closely. For avoid cellular connectivity issues, make sure to connect the gateway also via WiFi or ethernet. See https://www.thethingsindustries.com/docs/hardware/gateways/models/thethingsindoorgatewaypro/#connection-settings for more information.

  3. resolved Apr 24, 2025, 08:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2024

Issue with MQTT connections

Detected by Pingoru
Jun 03, 2024, 04:04 PM UTC
Resolved
Jun 03, 2024, 07:06 PM UTC
Duration
3h 1m
Affected: Europe 1 (eu1)Europe 2 (eu2)North America 1 (nam1)Australia 1 (au1)
Timeline · 3 updates
  1. investigating Jun 03, 2024, 04:04 PM UTC

    We are investigating a reported issue on MQTT connections.

  2. monitoring Jun 03, 2024, 06:10 PM UTC

    We have reverted a change and monitoring the results.

  3. resolved Jun 03, 2024, 07:06 PM UTC

    We reverted the change that caused the issue and it's now resolved.

Read the full incident report →