Datacake - Notice history

GraphQL API - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

Web Application - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

MQTT Server - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

White Label - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

Reports - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

Outgoing Webhooks - Operational

100.0% uptime
Sep 2026 · 100.0%Oct · 100.0%Nov · 100.0%
Sep 2026
Oct 2026
Nov 2026

Outbound Email Sending - Operational

Payments - Operational

Outbound SMS - Operational

Docs - Operational

Notice history

View current status

Nov 2026

Delayed email notifications
ResolvedPartial outage13 hours 46 minutes
  • ResolvedUTC

    We need to correct our previous update. Not all emails during this incident were delivered.

    Cause: at about 17:05 UTC on 14 Nov, our external email provider put a hold on all outgoing email from our account without notifying us. During the hold, their system kept accepting our emails as if they were being sent normally, but held them without delivering. We noticed the problem through our own monitoring and contacted the provider. They released the hold the same evening.

    What happened:

    - 14 Nov, 17:05 – 21:10 UTC: all platform emails were held by the provider. They were all delivered late, at about 23:30 UTC.

    - 14 Nov, 21:10 – 15 Nov, 06:39 UTC: while we worked around the hold, email notifications from rules were not sent. Device offline notifications, scheduled reports and other emails were delivered normally in this window. Rule email notifications from this window were not delivered and can't be resent.

    Since 06:39 UTC on 15 Nov, all emails, including rule notifications, are being delivered normally again.

    What wasn't affected: device monitoring, data collection and rule evaluation kept working the whole time. Rules still ran, and their other actions (webhooks, SMS, downlinks and so on) worked as usual. Only the email part of rule notifications was missing.

    What you can do: if you rely on rule email notifications, please check your devices' data and your rule history in the dashboard for the window from 21:10 UTC on 14 Nov to 06:39 UTC on 15 Nov.

    Next steps: a provider holding our email without notice isn't acceptable for notifications our customers rely on, so we're evaluating alternative email providers. We're also changing how rule notification emails are sent, so that switching providers can't affect them again.

    We're sorry, both for the outage and for the incorrect information in our previous update.

  • MonitoringUTC

    Email delivery is working again. Since 21:00 UTC, all platform emails are being sent normally again, including device offline notifications, scheduled report emails and rule-based email alerts.

    Between about 17:05 and 21:00 UTC, emails were not delivered. We're working with our email provider to find out whether emails from that window can still be delivered. If they can, you may receive some notifications late. If they can't, we'll send scheduled reports from that window again. We'll post an update once we know.

    Device monitoring, data collection, rules and all other notification channels worked normally the whole time.

    We're sorry for the trouble and will keep monitoring.

  • InvestigatingUTC

    Since about 17:05 UTC today, emails from the platform are not being delivered. This includes:

    - Device offline notifications

    - Scheduled report emails

    - Rule-based email alerts

    The problem is with our email delivery provider, and we're working with them to fix it. Everything else works normally: devices are monitored, data is collected and stored, rules run, and reports are generated. Webhooks, SMS and other non-email actions are not affected.

    Until this is fixed, please check device status and reports directly in the dashboard. Generated reports can be downloaded from the report page. We'll post an update as soon as email delivery is working again.

Git Sync causing missing page content
ResolvedPartial outage5 hours 13 minutes
  • ResolvedUTC

    This incident has been resolved. The build change that caused the Git Sync issue was rolled back, and Git Sync operations are now working normally. Affected spaces have been restored. If you still see missing or empty content in any space, please contact our support team at support@gitbook.com: mailto:support@gitbook.com and we will investigate promptly.

  • MonitoringUTC

    Cause identified as a build tooling change that affected Git Sync. The change has been rolled back, so new Git Sync operations are no longer affected. Recovery of affected spaces started at 15:00 GMT.

  • InvestigatingUTC

    We are investigating an issue where Git Sync operations can cause page content to become empty. Our team is working urgently to resolve this.

Oct 2026

API operations are slower than usual
ResolvedDegraded performance14 hours 32 minutes
  • ResolvedUTC

    The incident on Cloudflare is solved and our monitoring confirms that things are back to normal.

  • MonitoringUTC

    We have routed parts of our API connection to other regions to improve stability while this gets fixed by Cloudflare. We continue to monitor the situation as it progresses.

  • IdentifiedUTC

    Our API is responding slower than usual due to a known incident on Cloudflare. Any operations going through the affected region are slower or timing out. We are monitoring the incident closely.

    Cloudflare incident: https://www.cloudflarestatus.com/incidents/snth5ero95rz

OCT26
Upgrade The Things Stack Cloud to v3.37.0
CompletedMaintenance2 hours
  • CompletedOctober 26, 2026 at 11:00 AMUTC

    The scheduled maintenance has been completed.

  • UpdateOctober 26, 2026 at 10:19 AMUTC

    Verification is currently underway for the maintenance items.

  • In progressOctober 26, 2026 at 9:00 AMUTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

  • PlannedOctober 19, 2026 at 3:19 PMUTC

    During this maintenance window we will upgrade The Things Stack Cloud to v3.37.0 on all clusters (eu1, eu2, nam1, au1, as1).

    We expect brief service interruptions during this deployment.

    Some gateways may temporarily disconnect as services are restarted. Gateways are expected to automatically reconnect, but in some cases this may take up to one hour.

    Here is the changelog since the current version v3.36.2:

    Added

    • New gs_gateways_disconnected_total metric, counting gateway disconnections by protocol and disconnect reason. This makes disconnection reasons (such as gateways disappearing without a close handshake, or missing too many pongs) observable as a rate, instead of only through logs.
    • ttgc.managed-gateway-euis configuration option: Gateway EUI prefixes of managed gateways, defaulting to the EUI prefix of The Things Industries managed gateways. Gateways outside these prefixes are reported as not managed in the claiming info.
    • ttgc.lbscups.lns-port configuration option: the LoRa Basics Station LNS port of the Gateway Server, defaulting to 8887.
    • Downlink scheduling on all antennas of a gateway. Previously, only the first antenna could be used as a downlink path.
    • events.redis.store.expire-limiter-size configuration option to tune the memory used by the event stream expiration rate limiter, defaulting to 32 MiB.

    Changed

    • In the Semtech UDP Packet Forwarder protocol, PUSH_ACK and PULL_ACK acknowledgements are only sent after the gateway has connected to the Gateway Server and its data has been accepted.
    • Gateway disconnections are now logged once, as Disconnected, including the reason, instead of logging a Task failed warning for every task attached to the gateway connection. This removes several duplicate warnings per gateway disconnection, which were particularly noisy for gateways on unreliable backhaul.
    • Websocket close errors on the LoRa Basics Station frontend (such as a gateway disappearing without a close handshake) are now reported as a defined error with structured details. The gs.gateway.disconnect event for these disconnections now carries structured error details instead of a plain string; consumers that parse the event data should expect the ErrorDetails format.

    Fixed

    • Federated (OIDC/SSO) login no longer fails with unverified_email for identity providers such as Okta that omit the email_verified claim from the ID token and only provide it via the userinfo endpoint.
    • Parsing of the radio context (rctx) field of uplinks received via the LoRa Basics Station LNS protocol. The antenna index in the uplink metadata now reflects the radio context reported by the gateway and is echoed back in class A downlinks, instead of always being 0.
    • The antenna gain sent to LoRa Basics Station gateways in the router configuration. Each board now uses the gain of its own antenna instead of the first antenna's gain, and fractional gains are no longer truncated.
    • Memory usage of event-publishing components (most visibly the Application Server and Network Server) no longer grows with the number of entities.

Sep 2026

SEP7
The Things Stack Cloud Infrastructure Maintenance v3.36.2
CompletedMaintenance2 hours
  • CompletedSeptember 07, 2026 at 11:00 AMUTC

    The scheduled maintenance has been completed.

  • In progressSeptember 07, 2026 at 9:00 AMUTC

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

  • PlannedSeptember 01, 2026 at 6:25 AMUTC

    During this maintenance window we will make improvements servers that run The Things Stack Cloud.

    As some servers may have to restart, it is possible that there will be some service interruptions during the maintenance window.

    If you have questions, or if you experience problems after the maintenance has completed, please contact us at support@thethingsindustries.com.

Previous

Sep 2026 to Nov 2026

Next