Kit logo
ALL SYSTEMS OPERATIONAL

Kit systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Aug 2018 · 75 incidents caught

Last checked: 3 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    Kit is up and running.

    Last incident resolved 4 months ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked Kit. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds, so the next answer arrives by email.

10 monitors free, email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

Last 90 days

90-Day Health Summary

  • Total Incidents

    0

    Since Aug 2018

  • Major / Critical

    0

    None recorded

  • Minor Incidents

    0

    None recorded

  • Median Resolution

    Not enough data

Kit Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
CPU Overload
May 20, 2026 · 8:26 AM 3794d 12h 26m
None
Resolved
Details →
Email sending time degraded
May 20, 2026 · 8:26 AM 3789d 12h 3m
None
Resolved
Details →
Infrastructure upgrade
May 20, 2026 · 8:26 AM 3785d 1h 33m
None
Resolved
Details →
SSL Certification Problems
May 20, 2026 · 8:26 AM 3779d 17h 17m
None
Resolved
Details →
Intermittent errors in API
May 20, 2026 · 8:26 AM 3771d 20h 54m
None
Resolved
Details →
Email Sending Experiencing Lag
May 20, 2026 · 8:26 AM 3751d 9h 8m
None
Resolved
Details →
Configuration error
May 20, 2026 · 8:26 AM 3749d 13h 13m
None
Resolved
Details →
Errors subscribing to certain objects via API
May 20, 2026 · 8:26 AM 3696d 14h 26m
None
Resolved
Details →
Email sending errors
May 20, 2026 · 8:26 AM 3652d 17h 10m
None
Resolved
Details →
Performance issues
May 20, 2026 · 8:26 AM 3619d 1h 36m
None
Resolved
Details →

Common questions

Frequently Asked Questions

  • Is Kit down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does Kit go down?

    Based on our 90-day data, we've detected 0 incidents, of which 0 were major or critical. The median resolution time is unknown.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.