Kapable status
Everything is working
We check each Kapable and Signet service once a minute from a server in Helsinki, outside the platform it checks. A service counts as down after two failed checks in a row.
Kapable
Websitekapable.ai
Working
90 days ago30 days ago100.00% up100.00% upToday
Sign-inSigning in to your company's desktop
Working
90 days ago30 days ago100.00% up100.00% upToday
DesktopThe sign-in page of a company desktop
Working
90 days ago30 days ago100.00% up100.00% upToday
Data and storageTables, files and secrets for apps
Working
90 days ago30 days ago100.00% up100.00% upToday
Hosted appsApps at kapable.run addresses
Working
90 days ago30 days ago100.00% up100.00% upToday
Git and buildsgit.kapable.dev, where code lives and builds start
Working
90 days ago30 days ago100.00% up100.00% upToday
RunnersThe service your own build machines connect to
Working
90 days ago30 days ago100.00% up100.00% upToday
Docsdocs.kapable.ai
Working
90 days ago30 days ago100.00% up100.00% upToday
Signet
Websitesignetauth.com
Working
90 days ago30 days ago100.00% up100.00% upToday
Developer docssignetauth.dev, guides and API reference
Working
90 days ago30 days ago100.00% up100.00% upToday
Signet Cloudsignetauth.cloud
Working
90 days ago30 days ago100.00% up100.00% upToday
ConsoleWhere you manage hosted sign-in
Working
90 days ago30 days ago100.00% up100.00% upToday
Hosted sign-inA hosted Signet instance answering sign-in requests
Working
90 days ago30 days ago100.00% up100.00% upToday
Past incidents
Signet sign-in did not answer for about 10 minutes
ResolvedSignet's websites and hosted sign-in answered errors, then nothing, for about 10 minutes. A short load spike on the server that runs them caused it, and it recovered by itself.
Kapable was unreachable for about 25 minutes
ResolvedThe main Kapable server was overloaded for about 25 minutes and stopped answering web requests. It recovered by itself.