knak. Status · History · Incident #64513

RESOLVED

Unable to Access Knak after logging in

Critical · Started Oct 20, 2025 · 10:22 AM

Duration

21h 9m
Severity

Critical
Detection lead

—
User reports

—

Summary

Unable to Access Knak after logging in

This incident has been resolved.

Started

Oct 20, 2025 · 10:22 AM
Resolved

Oct 21, 2025 · 7:31 AM
Duration

21h 9m
Severity

Critical

Event timeline

How this incident unfolded

◐

Investigating
Oct 20 · 10:22 AM knak.

We are currently investigating this issue.
◉

Monitoring
Oct 20 · 10:33 AM knak.

We have been experiencing a temporary outage due to the ongoing AWS outage https://health.aws.amazon.com/health/status. We are currently stable but are closely monitoring the situation.
✓

Resolved
Oct 21 · 7:31 AM knak.

This incident has been resolved.

Pattern

Other recent incidents

Browse full incident history →

Get alerted before the next knak. outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start Monitoring Free