Kit systems
are operational.
Pulsetic can detect an outage before the provider officially reports it. 75 incidents on record since Aug 2018
Last updated: 13064 min ago · 0 user reports (24h)
Pulsetic can detect an outage before the provider officially reports it. 75 incidents on record since Aug 2018
Last updated: 13064 min ago · 0 user reports (24h)
Last incident resolved 5 months ago
Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.
Latest 50 reports from the last 48 hours
Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds on the Team plan, so the next answer arrives by email.
10 monitors free, checked every 5 minutes, with email alerts on failure and recovery. No credit card.
Click an issue to upvote it and help us better indicate the service status.
Have a different problem?
Distribution of reported issues over the last 24 hours.
Total Incidents
0
Jul 1 to Sep 29, 2026
Major / Critical
0
None recorded
Minor Incidents
0
None recorded
Median Resolution
—
Not enough data
Across all 4,379 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 2h 4m, and 35% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for Kit above.
Source: The State of Uptime 2026, figures as of .
From official status page
| 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
Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.
Based on our 90-day data, we've recorded 0 incidents, of which 0 were major or critical. The median resolution time is unknown.
Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.
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.
"Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, 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.
Add it as a dependency monitor. The Free plan includes one. See how it works
No credit card needed
Help us pinpoint the issue
Tell us what you're seeing, and we'll correlate your report with others from around the world.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.