Skip to content
PulseWatchOUTAGE.INTEL
Knock logo

Communication

Is Knock down right now?

NormalOfficial status last polled Oct 4, 2026 06:38 UTCknock.appOfficial status page

Are you on the Knock team and see something inaccurate? Report it to us. We respond within one business day.

Is Knock down right now?

No. Knock has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 4, 2026 07:35 UTC

Normal

Knock is operating normally

As of Oct 4, 2026 07:35 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Oct 2, 2026 21:30 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unavailable

Current measurements are not available for a health score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Knock.

3

Incident days

27

No recorded incident

32h 8m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Knock. Hover a day for detail.

Sep 5Sep 10Sep 15Sep 20Sep 25Sep 3001234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

3

Days with incidents

1 incident

Busiest day

32h 8m

Recorded duration

Report volume

0 reports in last 24H

07:30 AM11:00 AM02:30 PM06:00 PM09:30 PM01:00 AM04:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Knock: vendor-reported major incident on October 1 (tracked 1d 5h)

Oct 1, 03:34 PM → Oct 2, 09:30 PM · 1d 5h · high

Knock reported a major-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 1d 5h and closed tracking on 2026-10-02T21:30:09.971Z.

Duration
1d 5h
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, therefore it cannot describe what users experienced. The incident is known from Knock's own status page.

Incident timeline

  1. Oct 1, 03:34 PM

    The vendor reported a major-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 1, 03:34 PM

    Status updated: possible issue

  3. Oct 2, 09:30 PM

    PulseWatch closed the incident

Official updates

  1. Oct 1, 03:34 PM

    Knock reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

95.5%

90-day uptime

98.5%

Calculated from Knock's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other communication services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

Knock: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Knock or have an alert rule on it can be alerted, labelled vendor-reported.

10/1/2026, 3:34:52 PM · 1d 5h

03:34 PM09:30 PM
Detection10/1/2026, 3:34:52 PM · 2d ago

Detected — high severity

Knock: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Knock or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedHigh

Knock: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Knock or have an alert rule on it can be alerted, labelled vendor-reported.

9/21/2026, 6:35:13 PM · 2h 13m

06:35 PM08:48 PM
Detection9/21/2026, 6:35:13 PM · 12d ago

Detected — high severity

Knock: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Knock or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

Knock incident correlated across 1 signal group: official/vendor.

8/31/2026, 4:51:11 PM · 1h 15m

04:51 PM06:06 PM
Detection8/31/2026, 4:51:11 PM · 1mo ago

Detected — medium severity

Knock incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Knock enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

knock.app