←View full Krisp status
Krisp: Transcription Failed / Audio Not Recognized
Current Status: Major Outage
Last checked: 1m ago
What We're Seeing Right Now
No recent issues reported. If you're experiencing problems with Krisp, report below to help the community.
What is this error?
When Krisp fails to transcribe audio, the speech-to-text engine could not process your file. This can be due to audio quality, unsupported languages, format issues, or service problems.
Error Signatures
Transcription failedCould not recognize speechNo speech detectedAudio format not supportedTranscription errorUnable to process audioLanguage not supportedCommon Causes
- Audio quality too low (background noise, distortion)
- Unsupported audio format or codec
- Language not supported or auto-detection failed
- Audio file too long or too large
- Krisp transcription service is down
✓ How to Fix It
- Ensure audio is clear with minimal background noise
- Convert to WAV or MP3 format
- Specify the language explicitly if possible
- Try a shorter audio segment first
- Check file size against Krisp's limits
- Check this page for service-wide issues
Live Signals
Service Components
Krisp App
OperationalRecent Incidents
No incidents in the past 30 days
Frequently Asked Questions
Why did Krisp fail to transcribe my audio?
Most failures are due to audio quality, format, or file size. Try clear audio in WAV/MP3 format. If the issue is widespread, check the status above.
What audio formats does Krisp support?
WAV, MP3, and M4A are widely supported. Check Krisp's documentation for exact format requirements.
Is Krisp transcription down?
Check community reports below for real-time feedback.