Störungsverlauf von Ngrok

1. 8. September 2026 um 20:05 UTCinvestigating

   Einige Benutzer können Fehler beim Anmelden bei dashboard.ngrok.com über SSO feststellen. Wir untersuchen derzeit.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. September 2026 um 19:01 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das verhindert, dass sich einige Kunden bei dashboard.ngrok.com anmelden

2. 8. September 2026 um 19:29 UTCinvestigating

   Endpunkte von Kunden, die Verkehrsrichtlinien verwenden, werden fälschlicherweise als Grenzwerte markiert. Das ngrok engineering team arbeitet derzeit daran, dieses problem zu lösen.

3. 8. September 2026 um 19:30 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

4. 8. September 2026 um 19:37 UTCmonitoring

   Ein Fix wurde für alle Regionen bereitgestellt und Endpunkte, die Verkehrsrichtlinien verwenden, werden nicht mehr fälschlicherweise eingeschränkt. Kunden können immer noch Hinweise in ihren Dashboards sehen, die vor den Limits warnen.

5. 8. September 2026 um 20:26 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. September 2026 um 23:34 UTCinvestigating

   Neue Konten oder neu erstellte Authtoken können sich nicht verbinden. User get Team untersucht das Problem.

2. 4. September 2026 um 00:01 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 4. September 2026 um 00:11 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. September 2026 um 18:20 UTCresolved

   Zwischen dem 28. August und dem 1. September konnten Personen, die zu einem Ngrok-Konto eingeladen wurden, die Einladung nicht annehmen. Der Einladungslink hat einen Fehler zurückgegeben, anstatt den Benutzer anzumelden. Eine Authentifizierungsänderung, die am 28. August verschickt wurde, brach die URL, die eine Einladung einlöst. Wir haben die Einlösung auf login.ngrok.com verschoben, und die Einladungen haben ab dem 1. September um 00:21 UTC wieder funktioniert. Benutzer, die durch Tokio geroutet wurden, sahen den Fehler bis 14:15 Uhr UTC, als wir eine veraltete Routing-Konfiguration in dieser Region gelöscht haben. Wenn eine Einladung immer noch fehlschlägt, bitten Sie den Kontoinhaber, eine neue zu senden, oder senden Sie eine E-Mail an [email protected].

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. Juni 2026 um 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. Juni 2026 um 00:10 UTCmonitoring

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

3. 19. Juni 2026 um 05:04 UTCresolved

   This incident has been resolved.

1. 15. Mai 2026 um 00:49 UTCidentified

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

2. 15. Mai 2026 um 01:00 UTCmonitoring

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

3. 15. Mai 2026 um 01:13 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 20:12 UTCinvestigating

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

2. 8. Mai 2026 um 21:28 UTCmonitoring

   Our provider has fixed their system.

3. 8. Mai 2026 um 22:21 UTCresolved

   This has been resolved

1. 28. April 2026 um 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. April 2026 um 14:30 UTCidentified

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

3. 28. April 2026 um 14:44 UTCidentified

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

4. 28. April 2026 um 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. April 2026 um 16:28 UTCresolved

   Agent version 3.39.1 is now available in the Microsoft Store.

1. 31. März 2026 um 03:12 UTCidentified

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

2. 1. April 2026 um 17:44 UTCresolved

   This incident has been resolved.

1. 6. März 2026 um 17:11 UTCidentified

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

2. 6. März 2026 um 17:25 UTCresolved

   This incident has been resolved.

1. 12. Januar 2026 um 17:01 UTCinvestigating

   We are currently investigating this issue.

2. 12. Januar 2026 um 17:27 UTCidentified

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

3. 12. Januar 2026 um 19:04 UTCresolved

   This incident has been resolved.

1. 26. November 2025 um 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. November 2025 um 20:44 UTCmonitoring

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

3. 26. November 2025 um 20:44 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 26. November 2025 um 20:57 UTCresolved

   This incident has been resolved.

1. 4. Oktober 2025 um 00:35 UTCinvestigating

   We are currently investigating this issue.

2. 4. Oktober 2025 um 01:27 UTCmonitoring

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

3. 4. Oktober 2025 um 04:38 UTCresolved

   This incident has been resolved.

1. 27. August 2025 um 15:44 UTCidentified

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

2. 27. August 2025 um 16:15 UTCmonitoring

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

3. 27. August 2025 um 16:24 UTCresolved

   This incident has been resolved.

1. 13. August 2025 um 22:04 UTCinvestigating

   We are currently investigating this issue.

2. 13. August 2025 um 22:15 UTCidentified

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

3. 13. August 2025 um 22:34 UTCmonitoring

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

4. 14. August 2025 um 00:07 UTCmonitoring

   This incident has been resolved.

5. 14. August 2025 um 00:48 UTCresolved

   This incident has been resolved.

1. 11. August 2025 um 23:52 UTCinvestigating

   We are currently investigating this issue.

2. 12. August 2025 um 00:49 UTCmonitoring

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

3. 12. August 2025 um 15:20 UTCresolved

   This incident has been resolved.

1. 1. August 2025 um 19:08 UTCinvestigating

   We are currently investigating this issue.

2. 1. August 2025 um 21:15 UTCmonitoring

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

3. 1. August 2025 um 22:41 UTCresolved

   This incident has been resolved.

1. 1. August 2025 um 18:25 UTCinvestigating

   We are currently investigating this issue.

2. 1. August 2025 um 18:39 UTCmonitoring

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

3. 1. August 2025 um 18:44 UTCresolved

   This incident has been resolved.

1. 22. Juli 2025 um 17:03 UTCinvestigating

   We are currently investigating this issue.

2. 22. Juli 2025 um 17:22 UTCidentified

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

3. 22. Juli 2025 um 18:24 UTCmonitoring

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

4. 22. Juli 2025 um 19:28 UTCresolved

   This incident has been resolved.

1. 21. Juli 2025 um 20:19 UTCmonitoring

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

2. 22. Juli 2025 um 15:21 UTCresolved

   The upstream provider's issues are resolved