ngrok
Infrastructure. Source: ngrok status page.
- Incidents, last 90 days
- 5
- Median to mitigation
- 26m
- Median to resolution
- 1h 25m
- p95 to resolution
- 5h 27m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Login, tokens, certificates or credentials failed | 4 |
| A code release introduced the failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
All recorded incidents
SSO session validation errors on dashboard.ngrok.com
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: Login, tokens, certificates or credentials failed. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Users logging into dashboard.ngrok.com via SSO are encountering errors related to session validation.
-
monitoring
We've identified an individual host that was experiencing networking issues and removed it from our infrastructure.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Error when signing in via SSO
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Some users may encounter errors logging in to dashboard.ngrok.com via SSO. We are currently investigating.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Endpoints using traffic policies are erroneously hitting limits
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating an issue preventing some customers from logging in to dashboard.ngrok.com
-
investigating
Customer endpoints using traffic policy are erroneously being flagged as hitting limits. The ngrok engineering team is currently working to resolve this issue.
-
investigating
We are continuing to investigate this issue.
-
monitoring
A fix has been deployed to all regions and endpoints using traffic policies are no longer being erroneously limited. Customers may still see notices in their dashboards warning about the limits.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
New accounts or newly created authtokens are not able to connect
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
New accounts or newly created authtokens are not able to connect. Users get Team is looking into the issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
User invites disruption
Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
resolved
Between August 28 and September 1, people invited to an ngrok account couldn't accept the invitation. The invitation link returned an error instead of signing the user in. An authentication change shipped on August 28 broke the URL that redeems an invitation. We moved redemption...
Excerpts are shortened. Read the full incident on ngrok's status page.
Delays issuing certificates
Affected: Certificates
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
Our certificate provider is experiencing an outage and you may experience a delay in seeing your certificate issued for domain in the system.
-
monitoring
System is stable and generating certificates - monitoring for changes upstream.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
SSO Login to the ngrok Dashboard is currently redirecting back to the login page
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Delay in generating and renewing certificates for custom domains
Affected: Certificates
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Our certificate provider has run into an issue and is currently pausing generation and renewal of certificates.
-
monitoring
Our provider has fixed their system.
-
resolved
This has been resolved
Excerpts are shortened. Read the full incident on ngrok's status page.
Users who install ngrok via the Microsoft Store encounter a fatal panic immediately on starting an endpoint.
Affected: ngrok Agent and Libraries
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Users who have installed the ngrok agent via the Microsoft Store on Windows are seeing fatal panics on endpoint startup on the most recent agent version. Non Windows users and Windows users installing via other channels should not be impacted.
-
identified
The issue has been identified and the engineering team is working on the fix.
-
identified
We expect a new version of the agent that resolves this issue to be available within the next hour.
-
monitoring
Agent version 3.39.1 has been released to all channels. Once approved by Microsoft, the new build will be available via the Microsoft Store.
-
resolved
Agent version 3.39.1 is now available in the Microsoft Store.
Excerpts are shortened. Read the full incident on ngrok's status page.
Download of the ngrok binary are returning 500 errors
Affected: ngrok.com
Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Mac OS Agent Download is currently broken
Affected: ngrok.com
Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Slowness in Traffic Inspector Data Viewing
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Intermittent issue downloading the ngrok agent
Affected: ngrok Agent and Libraries
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are seeing intermittent failures when attempting to download or upgrade the ngrok agent. We have identified the issue and working on a fix.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Connection issues with endpoints
Affected: Region - EU, Region - US
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Errors on our billing and usage pages
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
We have identified an issue with a third party vendor we use and are working on a fix.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Some customers are running into degraded tunnel starts in all regions
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
This incident has been resolved.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Agent connections in the SA region are receiving errors when starting
Affected: Region - SA
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Older ngrok apt packages missing
Affected: ngrok Agent and Libraries
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
Older apt releases have been restored and we are monitoring for any issues related to that.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Traffic Inspector - New events are delayed
Affected: Events
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Error with certificates in ngrok
Affected: Dashboard (https://dashboard.ngrok.com), API (https://api.ngrok.com)
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Delays issuing certificates
Affected: Certificates
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
monitoring
Our certificate provider is experiencing an outage and you may experience a delay in seeing your certificate issued.
-
resolved
The upstream provider's issues are resolved
Excerpts are shortened. Read the full incident on ngrok's status page.
ngrok web assets are down
Affected: Dashboard (https://dashboard.ngrok.com), API (https://api.ngrok.com), ngrok.com
Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Agents are failing to start with an error message about dev domain
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been indentified and only affects a very small number of accounts. A fix is being work on.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
New events not showing in traffic inspector for some accounts
Affected: Events
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Traffic Inspector events in EU region not populating for some customers
Affected: Events
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This issue has been resolved
Excerpts are shortened. Read the full incident on ngrok's status page.
Rate limit action causing connection issues
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1, ngrok.com
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
Endpoints using the rate limit action are having connection issues due to a recent release. We are working on getting a fix out.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Traffic Inspector and Events are delayed
Affected: Events
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We have identified the issues and are working on a fix
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Sites unavailable
Affected: Dashboard (https://dashboard.ngrok.com), Region - AP, API (https://api.ngrok.com), Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1, ngrok.com
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
We are recovering and monitoring performance
-
identified
The issue has been identified and will be working to restore service.
-
monitoring
We have mostly recovered and are monitoring
-
identified
The issue has been identified and will be working to restore service
-
monitoring
We have stabilized and are monitoring status
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Customers receiving 3200 errors and inaccessible endpoints
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Intermittent connectivity issues
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
identified
We are continuing to work on a fix for this issue.
-
identified
We are continuing to work on a fix for this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Dashboard SSO logins are failing
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Unable to upgrade to pro or enterprise plans
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Getting a high rate of ERR_NGROK_503 in the EU region - No available reserved addresses
Affected: Region - EU
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
We have identified the issue and are deploying a fix.
-
monitoring
We have deployed the fix and are monitoring
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Dashboard failures: Billing Page and Account Creation down
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: The text does not say enough to tell. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
We are tracking an issue that prevents new accounts from being created, existing accounts from being deleted and also results in failures to access the billing subscription page to view or manage an account's subscription. We are preparing a fix for deployment. No other services...
-
monitoring
A fix has been deployed which resolves the issue and restores all dashboard functionality. We are monitoring to ensure that the fix is correct.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Intermittent service outages in the past 12 hours
Affected: Region - AP, Region - AP, Region - AU, Region - AU, Region - EU, Region - EU, Region - IN, Region - IN, Region - JP, Region - JP, Region - SA, Region - SA, Region - US, Region - US, Region - us-cal-1, Region - us-cal-1
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
The fix has been confirmed and the issue is now resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
New endpoints failing to start in all regions
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Partial outage in EU for endpoint connections
Affected: Region - EU
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We have a failure in our EU region that will impact a limited number of connections to that region.
-
identified
We believe we have identified the underlying issue and are working on a fix
-
monitoring
We have deployed a fix and are monitoring our systems
-
resolved
This incident has been resolved
Excerpts are shortened. Read the full incident on ngrok's status page.
Delayed certificate provisioning for wildcard domains created in the last two days
Affected: Certificates
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
IPv6 Network Connection Issues
Affected: Region - AP, Region - AP, Region - AU, Region - AU, Region - EU, Region - EU, Region - IN, Region - IN, Region - JP, Region - JP, Region - SA, Region - SA, Region - US, Region - US, Region - us-cal-1, Region - us-cal-1
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating intermittent issues with agents and endpoints connecting to some of our IPv6 addresses.
-
identified
The underlying issue has been identified, and we are working on fix.
-
monitoring
We have pushed out a fix and are monitoring
-
resolved
The incident has been resolved and connections are working as expected.
Excerpts are shortened. Read the full incident on ngrok's status page.
Agents experiencing tunnel connection errors
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Agents are experiencing tunnel connection errors (3200) for a subset of users. We are investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Some accounts getting suspended without warning
Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
We have identified impacted accounts that were improperly suspended by our billing system not recognizing invoices as paid. We have worked to ensure that accounts are no longer suspended, and are working to reinstate their paid subscriptions, where applicable. If your paid...
-
monitoring
We have identified and remediated the core issue impacting our billing system. All accounts impacted have the correct subscription plan enabled on their account, and will receive an email today. Thank you for your patience.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Degraded service in the EU region
Affected: Region - EU, Region - EU
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Investigating networking disruption to our documentation and front page
Affected: Dashboard (https://dashboard.ngrok.com)
Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
Intermittent request failures in eu and us regions
Affected: Region - EU, Region - EU, Region - US, Region - US
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
JP region degraded state
Affected: Region - JP, Region - JP
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We have a identified an issue with the jp region and are working to resolve the issue.
-
monitoring
We have fixed the issues with JP region and are monitoring.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
`jp` region is down for new tunnel starts and endpoint configuration changes
Affected: Region - JP
Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
The `jp` region is unable to update state, as such new tunnel starts will fail and changes to configuration for endpoints and Edges will fail. Existing tunnels are still working. The team has identified the issue and is working on mitigation.
-
identified
We are continuing to work on a fix for this issue.
-
monitoring
We are seeing `jp` recover and are continuing to monitor.
-
resolved
We are fully recovered in `jp`.
Excerpts are shortened. Read the full incident on ngrok's status page.
`jp` region experiencing degraded tunnel start errors
Affected: Region - JP
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are seeing tunnel start issues in `jp` and investigating.
-
resolved
An issue with pod resources and deploys caused intermittent failures for some new tunnels. This issue is now resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.
`ap` region degraded
Affected: Region - AP
Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We have identified an issue with a service rollout in the `ap` region and are resolving this issue. Customers may see a percentage of requests fail at ngrok's edge. We are resolving the issue and monitoring for recovery.
-
monitoring
We are seeing a partial recovery and continuing to monitor.
-
resolved
After monitoring, we believe this issue to be resolved. Please reach out to our support team if you continue to see issues.
Excerpts are shortened. Read the full incident on ngrok's status page.
OAuth, OIDC, and SAML modules for Edges degraded
Affected: Region - AP, Region - AU, Region - EU, Region - IN, Region - JP, Region - SA, Region - US, Region - us-cal-1
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
We have identified an issue with the following Edge modules that may be impacting customers' ability to access content served by the Edge: OAuth, OIDC, and SAML. We are rolling out a fix and monitoring. This issue started approximately ten minutes ago.
-
monitoring
Fixes are rolled out. The team will continue monitoring to confirm a full recovery.
-
monitoring
Customers using SAML modules may in rare cases need to clear cookies if you are seeing `BAD REQUEST` errors on login.
-
resolved
The system should be recovered for all users.
Excerpts are shortened. Read the full incident on ngrok's status page.
Intermittent errors affecting ngrok services in US
Affected: Dashboard (https://dashboard.ngrok.com), API (https://api.ngrok.com), Region - US, Region - US
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on ngrok's status page.