<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>LocalXpose Status - Incident history</title>
    <link>https://localxpose.instatus.com</link>
    <description>LocalXpose</description>
    <pubDate>Thu, 16 Apr 2026 14:31:00 +0000</pubDate>
    
<item>
  <title>Many EU tunnels are unreachable</title>
  <description>
    Type: Incident
    Duration: 4 hours and 34 minutes

    Affected Components: eu.loclx.io
    Apr 16, 14:31:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 16, 15:27:24 GMT+0 - Identified - To resolve the capacity constraints in our EU region, we are provisioning additional resources. We will begin migrating affected tunnel connections as soon as the deployment is complete. Apr 16, 15:35:00 GMT+0 - Monitoring - Our services in the **EU region** are now back online. We have successfully deployed additional capacity and migrated all affected tunnels. We are currently **monitoring** the infrastructure to ensure continued stability.

Thank you for your patience while we resolved this. Apr 16, 15:59:18 GMT+0 - Resolved - This incident has been resolved. Apr 16, 18:43:43 GMT+0 - Identified - Following a brief period of recovery, we have identified further capacity constraints affecting our EU infrastructure. We are currently provisioning additional server resources to handle the load and will provide an update once the mitigation is complete. Apr 16, 18:57:09 GMT+0 - Monitoring - Additional capacity was taken online and tunnels are migrated to the new resources. Apr 16, 19:04:35 GMT+0 - Resolved - This incident has been resolved all EU tunnels are working as expected. Apr 23, 19:04:00 GMT+0 - Postmortem - A detailed postmortem of this outage can be found on our blog: &lt;https://localxpose.io/blog/incident-2026-04-16-eu-outage&gt; 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:31:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:27:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  To resolve the capacity constraints in our EU region, we are provisioning additional resources. We will begin migrating affected tunnel connections as soon as the deployment is complete..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Our services in the **EU region** are now back online. We have successfully deployed additional capacity and migrated all affected tunnels. We are currently **monitoring** the infrastructure to ensure continued stability.

Thank you for your patience while we resolved this..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:59:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:43:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Following a brief period of recovery, we have identified further capacity constraints affecting our EU infrastructure. We are currently provisioning additional server resources to handle the load and will provide an update once the mitigation is complete..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:57:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Additional capacity was taken online and tunnels are migrated to the new resources..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:04:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved all EU tunnels are working as expected..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:04:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  A detailed postmortem of this outage can be found on our blog: &lt;https://localxpose.io/blog/incident-2026-04-16-eu-outage&gt;.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 16 Apr 2026 14:31:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmo1lalno00a1xmfgnc1l8igp</link>
  <guid>https://localxpose.instatus.com/incident/cmo1lalno00a1xmfgnc1l8igp</guid>
</item>

<item>
  <title>Some customers unable to make API requests, existing tunnels remain active</title>
  <description>
    Type: Incident
    Duration: 15 minutes

    Affected Components: localxpose.io
    Feb 26, 01:28:00 GMT+0 - Investigating - A subset of API traffic has triggered network security countermeasures. We are actively investigating the impact. If you believe your account is affected, please contact LocalXpose Support at hello@localxpose.io. Feb 26, 01:33:00 GMT+0 - Monitoring - We determined the issue to be resolved at this time. If you believe your tunnels are affected, please contact LocalXpose Support at hello@localxpose.io. Feb 26, 01:43:00 GMT+0 - Resolved - This incident has been resolved. If you have any issues, please contact LocalXpose Support at hello@localxpose.io. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:28:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  A subset of API traffic has triggered network security countermeasures. We are actively investigating the impact. If you believe your account is affected, please contact LocalXpose Support at hello@localxpose.io..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:33:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We determined the issue to be resolved at this time. If you believe your tunnels are affected, please contact LocalXpose Support at hello@localxpose.io..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:43:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. If you have any issues, please contact LocalXpose Support at hello@localxpose.io..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 26 Feb 2026 01:28:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmm2szaud0iu9g3s9p40mxhpg</link>
  <guid>https://localxpose.instatus.com/incident/cmm2szaud0iu9g3s9p40mxhpg</guid>
</item>

<item>
  <title>Tunnels offline in US, Europe, and Asia-Pacific regions</title>
  <description>
    Type: Incident
    Duration: 12 minutes

    Affected Components: , us.loclx.io, eu.loclx.io, ap.loclx.io, 
loclx.io →
    Jan 23, 18:13:00 GMT+0 - Investigating - We are investigating an alert triggered by automated healthcheck failures in `ap`, `eu`, and `us` regions. Jan 23, 18:18:00 GMT+0 - Monitoring - We have identified the issue and are beginning to restore service. Existing tunnels are expected to begin reconnecting automatically now.

As always, if customers are experiencing additional issues our support team is standing by to help. Jan 23, 18:25:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:13:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are investigating an alert triggered by automated healthcheck failures in `ap`, `eu`, and `us` regions..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:18:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have identified the issue and are beginning to restore service. Existing tunnels are expected to begin reconnecting automatically now.

As always, if customers are experiencing additional issues our support team is standing by to help..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:25:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 23 Jan 2026 18:13:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmkr88wyc09ee9vy6k4onks7o</link>
  <guid>https://localxpose.instatus.com/incident/cmkr88wyc09ee9vy6k4onks7o</guid>
</item>

<item>
  <title>Issues establishing connections in EU region</title>
  <description>
    Type: Incident
    Duration: 1 hour and 29 minutes

    Affected Components: eu.loclx.io
    Dec 13, 13:31:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 13, 14:16:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Our immediate response was blocked by available capacity in the region. Our team is deploying an alternative configuration while working with our cloud provider to restore the affected component. We will provide another update soon. Dec 13, 14:30:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Dec 13, 15:00:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:31:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:16:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident. Our immediate response was blocked by available capacity in the region. Our team is deploying an alternative configuration while working with our cloud provider to restore the affected component. We will provide another update soon..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 13 Dec 2025 13:31:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmj4ch57d05hvn3e5rmtjdvio</link>
  <guid>https://localxpose.instatus.com/incident/cmj4ch57d05hvn3e5rmtjdvio</guid>
</item>

<item>
  <title>Cloudflare Gateway Errors on API Endpoints</title>
  <description>
    Type: Incident
    Duration: 1 hour and 30 minutes

    Affected Components: localxpose.io
    Nov 18, 11:30:00 GMT+0 - Investigating - At approximately 11:30 UTC on 18 Nov 2025 we began detecting automation failures due to API reachability and quickly moved to investigate Cloudflare as the source of the issue, but were unable to use Cloudflare&#039;s Dashboard or APIs due to what appears to be a global Cloudflare outage.

Our initial assumption based on our own monitoring is this issue only affects the subset of all users currently needing to interact with the API or Web UIs. We have not observed any tunnel connection failures at this time, and existing tunnels appear stable.

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._ Nov 18, 12:55:00 GMT+0 - Monitoring - Status page change was blocked by Cloudflare error. Internal logs for LocalXpose API show occasional disruption, but most users should not experience any issue, and are encouraged to retry any failed requests. We are currently monitoring the result of Cloudflare&#039;s incident.

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._ Nov 18, 12:05:00 GMT+0 - Identified - We are continuing to work on communication and resolution for this incident. API connectivity appears to be disrupted intermittently for different users, with some users reporting no issues. The issue appears global, not limited to a specific region. We have been unable to log into the Cloudflare Dashboard or update our own status page at this time.

We are currently not detecting any issues with customer tunnels, only the LocalXpose API and GUI.

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._ Nov 18, 13:00:00 GMT+0 - Resolved - Since 12:00 UTC we&#039;ve seen no requests failing. 

* our API logs: normal since 11:50 UTC
* our monitoring: healthy since 11:51 UTC
* Cloudflare logs: normal since 12:00 UTC 🤨

We consider 12:00 UTC the resolution time of this incident, in spite of the fact most of the internet still appears affected. If we detect additional failures we will publish an updated incident timeline accordingly.

**If you have any issues now or in the future please contact** [**hello@localxpose.io**](mailto:hello@localxpose.io)**. Our team is happy to help investigate.**

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._ 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  At approximately 11:30 UTC on 18 Nov 2025 we began detecting automation failures due to API reachability and quickly moved to investigate Cloudflare as the source of the issue, but were unable to use Cloudflare&#039;s Dashboard or APIs due to what appears to be a global Cloudflare outage.

Our initial assumption based on our own monitoring is this issue only affects the subset of all users currently needing to interact with the API or Web UIs. We have not observed any tunnel connection failures at this time, and existing tunnels appear stable.

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:55:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Status page change was blocked by Cloudflare error. Internal logs for LocalXpose API show occasional disruption, but most users should not experience any issue, and are encouraged to retry any failed requests. We are currently monitoring the result of Cloudflare&#039;s incident.

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on communication and resolution for this incident. API connectivity appears to be disrupted intermittently for different users, with some users reporting no issues. The issue appears global, not limited to a specific region. We have been unable to log into the Cloudflare Dashboard or update our own status page at this time.

We are currently not detecting any issues with customer tunnels, only the LocalXpose API and GUI.

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Since 12:00 UTC we&#039;ve seen no requests failing. 

* our API logs: normal since 11:50 UTC
* our monitoring: healthy since 11:51 UTC
* Cloudflare logs: normal since 12:00 UTC 🤨

We consider 12:00 UTC the resolution time of this incident, in spite of the fact most of the internet still appears affected. If we detect additional failures we will publish an updated incident timeline accordingly.

**If you have any issues now or in the future please contact** [**hello@localxpose.io**](mailto:hello@localxpose.io)**. Our team is happy to help investigate.**

&gt; _This is a retroactive incident being published at 18:00 UTC on 18 Nov 2025\. The update messages were being written at the time of the update, but were unpublished due to the Cloudflare outage affecting the Instatus Dashboard UI._.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 11:30:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmi4vqbs700pihqzh0acft8qr</link>
  <guid>https://localxpose.instatus.com/incident/cmi4vqbs700pihqzh0acft8qr</guid>
</item>

<item>
  <title>Connection timeouts in Asia-Pacific tunnels</title>
  <description>
    Type: Incident
    Duration: 9 minutes

    Affected Components: ap.loclx.io
    Sep 27, 12:27:00 GMT+0 - Investigating - We are currently investigating automated healthcheck failures in the `ap` region(s). Sep 27, 12:36:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:27:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating automated healthcheck failures in the `ap` region(s)..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:36:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 27 Sep 2025 12:27:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmg2akcgo02guv8t1vii312j6</link>
  <guid>https://localxpose.instatus.com/incident/cmg2akcgo02guv8t1vii312j6</guid>
</item>

<item>
  <title>Underlying infrastructure malfunction affecting API services</title>
  <description>
    Type: Incident
    Duration: 34 minutes

    Affected Components: localxpose.io
    Sep 13, 10:07:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 13, 10:08:00 GMT+0 - Identified - We received a notification that one of our cloud providers is investigating an &quot;underlying infrastructure malfunction&quot;. Sep 13, 10:37:00 GMT+0 - Monitoring - We can confirm API requests are being handled successfully. We are continuing to actively monitor performance. Sep 13, 10:41:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 34 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:07:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:08:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We received a notification that one of our cloud providers is investigating an &quot;underlying infrastructure malfunction&quot;..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:37:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We can confirm API requests are being handled successfully. We are continuing to actively monitor performance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:41:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 13 Sep 2025 10:07:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmfi78e8p03pc11anjqux4g73</link>
  <guid>https://localxpose.instatus.com/incident/cmfi78e8p03pc11anjqux4g73</guid>
</item>

<item>
  <title>Many US-based tunnels disrupted by DDoS protection</title>
  <description>
    Type: Incident
    Duration: 27 days and 14 hours

    Affected Components: us.loclx.io
    May 7, 11:33:00 GMT+0 - Monitoring - We have implemented a fix and are currently monitoring the affected system. May 7, 16:00:00 GMT+0 - Resolved - This incident has been resolved. May 6, 16:34:00 GMT+0 - Investigating - We are currently investigating this incident. May 6, 16:39:00 GMT+0 - Identified - Our monitoring systems and operations engineers have identified the scope of impact and are working on a fix May 7, 08:34:00 GMT+0 - Investigating - We have been alerted by our own monitoring, and are requesting information from our hosting provider regarding the behavior of their automated DDoS protection. May 6, 17:34:00 GMT+0 - Monitoring - All gateway servers are healthy, and service has been restored for affected users. We are monitoring and will continue engaging with our cloud provider to identify root causes and next steps. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 27 days and 14 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:33:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have implemented a fix and are currently monitoring the affected system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:34:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:39:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our monitoring systems and operations engineers have identified the scope of impact and are working on a fix.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:34:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have been alerted by our own monitoring, and are requesting information from our hosting provider regarding the behavior of their automated DDoS protection..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:34:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  All gateway servers are healthy, and service has been restored for affected users. We are monitoring and will continue engaging with our cloud provider to identify root causes and next steps..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 6 May 2025 16:34:00 +0000</pubDate>
  <link>https://localxpose.instatus.com/incident/cmakns85i000gpw1k0vimg2id</link>
  <guid>https://localxpose.instatus.com/incident/cmakns85i000gpw1k0vimg2id</guid>
</item>

  </channel>
  </rss>