Is Knak down?

Last checked 2m ago
Current status
Knak is up

No active incidents. All 4 components operational.

  • Official status page: status.knak.io
  • Checked every 5 minutes
  • 4 components tracked

Knak is operational right now. Last checked 2m ago; the most recent incident resolved 14d ago.

Real-time Knak status, recent outages, and incident history: pulled directly from Knak's official status page at status.knak.io every 5 minutes. Pingoru tracks 4 Knak services and has captured 1 incident in the last 90 days (99.87% uptime). Get email, Slack, Discord, or webhook alerts the moment Knak reports a new incident, free for 3 monitors, no credit card.

Users who monitor Knak also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 8,000+ providers
Knak uptime 99.87% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 5h 36m
    Started Oct 21, 2026, 01:28 PM UTC · Resolved Oct 21, 2026, 07:05 PM UTC
    Knak AppKnak Send
    Timeline · 10 updates
    • investigating · Oct 21, 2026, 01:28 PM UTC

      Our Engineering and Security teams are responding to PHP2SHELL, a recently disclosed vulnerability in widely used web software, including components Knak relies on. We are actively monitoring our systems and applying protective measures. Protecting your data comes first. If we see a threat that needs further action, we may take Knak offline temporarily, possibly with little advance notice. We know any disruption affects your team’s ability to build and launch campaigns. We apologize for the inconvenience and will post updates on our status page as they become available.

    • investigating · Oct 21, 2026, 02:27 PM UTC

      We're actioning a patch

    • investigating · Oct 21, 2026, 02:28 PM UTC

      We're actioning a patch.

    • investigating · Oct 21, 2026, 03:12 PM UTC

      We’ve applied the patch and are currently testing it before bringing Knak back online. Our preliminary investigation has shown no indication that Knak has been compromised. We’ll let you know as soon as Knak is back up.

    • identified · Oct 21, 2026, 03:32 PM UTC

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

    • monitoring · Oct 21, 2026, 03:45 PM UTC

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

    • monitoring · Oct 21, 2026, 03:59 PM UTC

      We are continuing to monitor for any further issues.

    • monitoring · Oct 21, 2026, 04:03 PM UTC

      We are continuing to monitor for any further issues.

    • resolved · Oct 21, 2026, 07:05 PM UTC

      This incident has been resolved.

    • postmortem · Oct 29, 2026, 03:22 PM UTC

      ## Summary On October 21, 2026, we took the Knak platform, including Knak Send, offline for about two hours as a precaution. Two critical vulnerabilities had been announced in PHP, the programming language that runs much of the web, including parts of Knak. The issue was in PHP itself, not in Knak's code. We applied the fix the same morning, then reviewed our systems for any sign the vulnerabilities had been used against us. We found no evidence that these vulnerabilities were exploited against Knak, and no evidence of unauthorized access to customer data. No action is required on your part. ## Timeline \(Eastern Time\) * **October 20:** The PHP security team announced two critical vulnerabilities \(CVE-2026-109618 and CVE-2026-109619\), known as "PHP2Shell", with a fix to follow. * **October 21, about 9:30 a.m.:** We took the Knak platform and Knak Send offline as a precaution while we applied the fix. * **About 11:45 a.m.:** Service restored, running the patched version of PHP. ## What we reviewed Our DevOps and security teams reviewed activity from October 19, the day before the vulnerabilities became public, through the time the patch was applied and compared it against normal activity from the preceding weeks. The review covered: * Firewall, load balancer and web server logs. * Application logs, errors and performance monitoring. * Application security detections. * Outbound network traffic. * Cloud account activity and credential use, reviewed from early October through October 22. ## What we found * No requests matching the PHP2Shell attack pattern against production. * No server crashes, unusual memory use or unexpected outbound traffic. * No unusual activity on Knak's cloud hosting or identity provider accounts. ## Additional steps we took * Rotated production cloud access keys as a precaution. * Applied additional hardening recommended by the PHP project. ## What you need to do No action is required. We apologize for the disruption to your service. Given the severity of these vulnerabilities, we chose to take the platform offline until the fix was in place, rather than risk exposing your data. If you have any questions, please reach out to your Customer Success Manager or [[email protected]](mailto:[email protected]).

    Latest: ## Summary On October 21, 2026, we took the Knak platform, including Knak Send, offline for about two hours as a precaution. Two critical vulnerabilities had been announced in PHP,…

Incident record

Since April 2026 · Statuspage by Atlassian · 4 components checked every 5 minutes
51incidents recorded
10last 12 months
1last 90 days
5 hourstypical duration, 12 months

The longest incident in the last year, Knak Tracking Pixel Degraded Performance on January 19, 2026, ran for 25 hours.

Most affected components, last 12 months

  • Knak App9
  • Knak Send3

Latest incidents

  • Knak PHP security patch October 21, 2026 · 6 hours · degraded service

    Our Engineering and Security teams are responding to PHP2SHELL, a recently disclosed vulnerability in widely used web software, including components Knak…

  • Knak AI Degraded Performance July 16, 2026 · 8 hours · degraded service

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

  • Claude outage affecting Knak AI June 23, 2026 · 96 minutes · major outage

    A Claude outage is degrading Knak AI's performance. We are monitoring the provider's status updates.

Outage history

Past 90 days · 1 incident View full outage history →
  • Started Oct 21, 2026, 01:28 PM UTC · Resolved Oct 21, 2026, 07:05 PM UTC · 5h 36m