Histórico de interrupções do Ngrok

1. 17 Gwengolo 2026 da 15:10 UTCinvestigating

   Usuários logando no dashboard.ngrok.com via SSO estão encontrando erros relacionados à validação de sessão.

2. 17 Gwengolo 2026 da 15:36 UTCmonitoring

   Identificámos um anfitrião individual que estava a experimentar problemas de rede e removemos da nossa infra-estrutura.

3. 17 Gwengolo 2026 da 20:37 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gwengolo 2026 da 20:05 UTCinvestigating

   Alguns usuários podem encontrar erros de login no dashboard.ngrok.com via SSO. Estamos a investigar.

2. 8 Gwengolo 2026 da 21:48 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 8 Gwengolo 2026 da 19:01 UTCinvestigating

   Atualmente estamos investigando um problema que impede alguns clientes de fazer login no dashboard.ngrok.com

2. 8 Gwengolo 2026 da 19:29 UTCinvestigating

   Endpoints do cliente usando a política de tráfego estão erroneamente sendo sinalizados como atingindo limites. A equipe de engenharia ngrok está atualmente trabalhando para resolver esta questão.

3. 8 Gwengolo 2026 da 19:30 UTCinvestigating

   Continuamos a investigar esta questão.

4. 8 Gwengolo 2026 da 19:37 UTCmonitoring

   Uma correção foi implantada em todas as regiões e os objetivos usando políticas de tráfego não estão mais sendo erroneamente limitados. Os clientes podem ainda ver avisos em seus painéis de aviso sobre os limites.

5. 8 Gwengolo 2026 da 20:26 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Gwengolo 2026 da 23:34 UTCinvestigating

   Novas contas ou authtokens recém-criados não são capazes de se conectar. Usuários obter Equipe está olhando para o problema.

2. 4 Gwengolo 2026 da 00:01 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 4 Gwengolo 2026 da 00:11 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gwengolo 2026 da 18:20 UTCresolved

   Entre 28 de agosto e 1o de setembro, as pessoas convidadas para uma conta ngrok não puderam aceitar o convite. O link do convite devolveu um erro em vez de assinar com o usuário. Uma mudança de autenticação enviada em 28 de agosto quebrou o URL que resgata um convite. Movemos a redenção para login.ngrok.com, e os convites funcionaram novamente a partir de 1 de setembro às 00:21 UTC. Os usuários encaminhados por Tóquio continuaram vendo o erro até as 14:15 UTC, quando limpamos uma configuração de roteamento na região. Se um convite ainda falhar, peça ao proprietário da conta para enviar um novo, ou suporte por [email protected].

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Mezheven 2026 da 20:16 UTCidentified

   Our certificate provider is experiencing an outage and you may experience a delay in seeing your certificate issued for domain in the system.

2. 19 Mezheven 2026 da 00:10 UTCmonitoring

   System is stable and generating certificates - monitoring for changes upstream.

3. 19 Mezheven 2026 da 05:04 UTCresolved

   This incident has been resolved.

1. 15 Mae 2026 da 00:49 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 15 Mae 2026 da 01:00 UTCmonitoring

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

3. 15 Mae 2026 da 01:13 UTCresolved

   This incident has been resolved.

1. 8 Mae 2026 da 20:12 UTCinvestigating

   Our certificate provider has run into an issue and is currently pausing generation and renewal of certificates.

2. 8 Mae 2026 da 21:28 UTCmonitoring

   Our provider has fixed their system.

3. 8 Mae 2026 da 22:21 UTCresolved

   This has been resolved

1. 28 Ebrel 2026 da 14:29 UTCinvestigating

   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.

2. 28 Ebrel 2026 da 14:30 UTCidentified

   The issue has been identified and the engineering team is working on the fix.

3. 28 Ebrel 2026 da 14:44 UTCidentified

   We expect a new version of the agent that resolves this issue to be available within the next hour.

4. 28 Ebrel 2026 da 15:24 UTCmonitoring

   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.

5. 28 Ebrel 2026 da 16:28 UTCresolved

   Agent version 3.39.1 is now available in the Microsoft Store.

1. 31 Meurzh 2026 da 03:12 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 1 Ebrel 2026 da 17:44 UTCresolved

   This incident has been resolved.

1. 6 Meurzh 2026 da 17:11 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 6 Meurzh 2026 da 17:25 UTCresolved

   This incident has been resolved.

1. 12 Genver 2026 da 17:01 UTCinvestigating

   We are currently investigating this issue.

2. 12 Genver 2026 da 17:27 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 12 Genver 2026 da 19:04 UTCresolved

   This incident has been resolved.

1. 26 Du 2025 da 18:28 UTCidentified

   We are seeing intermittent failures when attempting to download or upgrade the ngrok agent. We have identified the issue and working on a fix.

2. 26 Du 2025 da 20:44 UTCmonitoring

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

3. 26 Du 2025 da 20:44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 26 Du 2025 da 20:57 UTCresolved

   This incident has been resolved.

1. 4 Here 2025 da 00:35 UTCinvestigating

   We are currently investigating this issue.

2. 4 Here 2025 da 01:27 UTCmonitoring

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

3. 4 Here 2025 da 04:38 UTCresolved

   This incident has been resolved.

1. 27 Eost 2025 da 15:44 UTCidentified

   We have identified an issue with a third party vendor we use and are working on a fix.

2. 27 Eost 2025 da 16:15 UTCmonitoring

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

3. 27 Eost 2025 da 16:24 UTCresolved

   This incident has been resolved.

1. 13 Eost 2025 da 22:04 UTCinvestigating

   We are currently investigating this issue.

2. 13 Eost 2025 da 22:15 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 13 Eost 2025 da 22:34 UTCmonitoring

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

4. 14 Eost 2025 da 00:07 UTCmonitoring

   This incident has been resolved.

5. 14 Eost 2025 da 00:48 UTCresolved

   This incident has been resolved.

1. 11 Eost 2025 da 23:52 UTCinvestigating

   We are currently investigating this issue.

2. 12 Eost 2025 da 00:49 UTCmonitoring

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

3. 12 Eost 2025 da 15:20 UTCresolved

   This incident has been resolved.

1. 1 Eost 2025 da 19:08 UTCinvestigating

   We are currently investigating this issue.

2. 1 Eost 2025 da 21:15 UTCmonitoring

   Older apt releases have been restored and we are monitoring for any issues related to that.

3. 1 Eost 2025 da 22:41 UTCresolved

   This incident has been resolved.

1. 1 Eost 2025 da 18:25 UTCinvestigating

   We are currently investigating this issue.

2. 1 Eost 2025 da 18:39 UTCmonitoring

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

3. 1 Eost 2025 da 18:44 UTCresolved

   This incident has been resolved.

1. 22 Gouere 2025 da 17:03 UTCinvestigating

   We are currently investigating this issue.

2. 22 Gouere 2025 da 17:22 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 22 Gouere 2025 da 18:24 UTCmonitoring

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

4. 22 Gouere 2025 da 19:28 UTCresolved

   This incident has been resolved.