Forum Discussion
Web Speech API not working in Edge v. 147
Hello,
The JavaScript Web Speech API is not working with speech recognition in Edge v. 147 for multiple users in Spain, Italy and Turkey. This has been a problem since at least April 22, 2026. Can you fix it please?
12 Replies
I wonder what are they doing there and they can not fix a problem that affects thousands of users wordwide. Web speech recognition doesn't work. It returns network error. So simple.
Also in Austria it is not working.
Also in Greece it is not working.
the following script works perfect on Chrome but returns network error on Edge
<!DOCTYPE html>
<html lang="el">
<head>
<meta charset="UTF-8">
<title>Edge Speech Test</title>
</head>
<body>
<h2>Speech Recognition Test</h2>
<button id="start">Start</button>
<button id="startTwice">Start Twice (test error)</button>
<pre id="log"></pre>
<script>
const SR = window.SpeechRecognition || window.webkitSpeechRecognition;
let recognition = null;
function log(msg) {
document.getElementById("log").textContent += msg + "\n";
console.log(msg);
}
function createRecognition() {
const r = new SR();
r.lang = "el-GR";
r.continuous = false;
r.interimResults = false;
r.onstart = () => log("✅ STARTED");
r.onresult = (e) => {
const t = e.results[0][0].transcript;
log("✅ RESULT: " + t);
r.stop();
};
r.onerror = (e) => log("❌ ERROR: " + e.error);
r.onend = () => log("🔚 ENDED");
return r;
}
// ✅ Normal start (like working case)
document.getElementById("start").onclick = () => {
log("---- NORMAL START ----");
recognition = createRecognition();
recognition.start();
};
// 🚨 Double start test (simulate your app)
document.getElementById("startTwice").onclick = () => {
log("---- DOUBLE START ----");
recognition = createRecognition();
recognition.start();
// Δεύτερο start σχεδόν αμέσως
setTimeout(() => {
try {
recognition.start();
log("⚠ δεύτερο start()");
} catch(e) {
log("caught error: " + e.message);
}
}, 50);
};
</script>
</body>
</html>
- Kelly_Y
Microsoft
Hi Everyone! Our developers are investigating and need some additional information. If you are able, can you provide the following?
1. Navigate to edge://metrics-internals/#variations and provide the values for SpeechNetworkStack and CFRSpeechServiceProtectECS experiments. It is possible you will not have these but if you do, it will look something like this:
"SpeechNetworkStack": { "enableFeatures": [ "msSpeechRecognitionChromiumNetworkStack" ] }, "CFRSpeechServiceProtectECS": { "enableFeatures": [ "msSpeechSynthesisServiceUseCetoService", "msSpeechRecognitionServiceUseCetoService" ] },2. After you see the failure, navigate to edge://histograms and provide the information under the following sections (they will all be right next to each other)
"Microsoft.SpeechRecognition.CancellationReason"
"Microsoft.SpeechRecognition.Error"
"Microsoft.SpeechRecognition.ErrorRate"
"Microsoft.SpeechRecognition.Event"
"Microsoft.SpeechRecognition.Method2"
"Microsoft.SpeechRecognition.SdkInstall"
"Microsoft.SpeechRecognition.WasRateLimited"If you prefer, please feel free to send me a message with this information. Thanks!
-Kelly
Hello Kelly,
It has been working poorly for over a month now. Some days it worked for a few hours. But most days the speech recognition API gives a "network" error over and over again. Below is the information you requested:
edge://metrics-internals/#variations
There is not "SpeechNetworkStack" entry.
"CFRSpeechServiceProtectECS": {
"enableFeatures": [
"msSpeechSynthesisServiceUseCetoService",
"msSpeechRecognitionServiceUseCetoService"
]
},
edge://histograms/
- Histogram: Microsoft.SpeechRecognition.CancellationReason recorded 29 samples, mean = 0.8 (flags = 0x41) [#]
0 ------O (6 = 20.7%)
1 -----------------------O (23 = 79.3%) {20.7%}
2 ...
- Histogram: Microsoft.SpeechRecognition.Error recorded 35 samples, mean = 26.3 (flags = 0x41) [#]
0 ...
25 ------------O (12 = 34.3%) {0.0%}
26 O (0 = 0.0%) {34.3%}
27 -----------------------O (23 = 65.7%) {34.3%}
28 ...
- Histogram: Microsoft.SpeechRecognition.ErrorRate recorded 149 samples, mean = 2.6 (flags = 0x41) [#]
0 ------------------------------O (30 = 20.1%)
1 ------------------------------O (30 = 20.1%) {20.1%}
2 ------------------------------O (30 = 20.1%) {40.3%}
3 ------------------------------O (30 = 20.1%) {60.4%}
4 ...
7 -----------------------------O (29 = 19.5%) {80.5%}
8 ...
- Histogram: Microsoft.SpeechRecognition.Event recorded 75 samples, mean = 1.5 (flags = 0x41) [#]
0 ------------------------------O (30 = 40.0%)
1 ------------------------------O (30 = 40.0%) {40.0%}
2 --O (2 = 2.7%) {80.0%}
3 -O (1 = 1.3%) {82.7%}
4 ------O (6 = 8.0%) {84.0%}
5 ...
8 ------O (6 = 8.0%) {92.0%}
9 O (0 = 0.0%) {100.0%}
- Histogram: Microsoft.SpeechRecognition.Method2 recorded 66 samples, mean = 1.5 (flags = 0x41) [#]
0 ------------------------------O (30 = 45.5%)
1 ------O (6 = 9.1%) {45.5%}
2 O (0 = 0.0%) {54.5%}
3 ------------------------------O (30 = 45.5%) {54.5%}
4 O
- Histogram: Microsoft.SpeechRecognition.SdkInstall recorded 30 samples, mean = 1.0 (flags = 0x41) [#]
0 O (0 = 0.0%)
1 ------------------------------O (30 = 100.0%) {0.0%}
2 ...
- Histogram: Microsoft.SpeechRecognition.WasRateLimited recorded 30 samples, mean = 0.0 (flags = 0x41) [#]
0 ------------------------------O (30 = 100.0%)
1 ...
I did some additional tests and got some observations.
I used Speech Translator extension for the tests, basically it restarts the speech recognition onend() or onerror() events.
On the first start it returned me "No speech" error this time (so it means it started normally and there was just no sound), but on the restart I kept getting "Network error" over and over again.
Then I tried again (complete new initialization of SpeechRecognition) and I got "Network error" right away and kept getting "Network error" over and over again.
I tried a bit later and got "No speech" 2 times and then "Network Error" again.
I did some tests with different VPNs and without any - in my case it didnt affect the behavior.
And I dont have any "Microsoft.SpeechRecognition" records here:
edge://metrics-internals/#variations
The only related to SpeechRecognitions lines there are:
"CFRSpeechServiceProtectECS": { "enableFeatures": [ "msSpeechSynthesisServiceUseCetoService", "msSpeechRecognitionServiceUseCetoService" ] },I recoded histogram for the attempt where I got 2 "No Speech" and then many "Network Error" (full report sent in dm):
Histograms The page will show the difference in histogram data since you switched to Monitoring mode. The page will automatically refresh every 1 second unless you click stop. Include histograms from subprocesses - Histogram: Microsoft.SpeechRecognition.CancellationReason recorded 2 samples, mean = 1.0 (flags = 0x41) [#] 0 O (0 = 0.0%) 1 --O (2 = 100.0%) {0.0%} 2 ... - Histogram: Microsoft.SpeechRecognition.Error recorded 4 samples, mean = 26.0 (flags = 0x41) [#] 0 ... 25 --O (2 = 50.0%) {0.0%} 26 O (0 = 0.0%) {50.0%} 27 --O (2 = 50.0%) {50.0%} 28 ... - Histogram: Microsoft.SpeechRecognition.ErrorRate recorded 20 samples, mean = 2.6 (flags = 0x41) [#] 0 ----O (4 = 20.0%) 1 ----O (4 = 20.0%) {20.0%} 2 ----O (4 = 20.0%) {40.0%} 3 ----O (4 = 20.0%) {60.0%} 4 ... 7 ----O (4 = 20.0%) {80.0%} 8 ... - Histogram: Microsoft.SpeechRecognition.Event recorded 8 samples, mean = 0.5 (flags = 0x41) [#] 0 ----O (4 = 50.0%) 1 ----O (4 = 50.0%) {50.0%} 2 ... - Histogram: Microsoft.SpeechRecognition.Method2 recorded 8 samples, mean = 1.5 (flags = 0x41) [#] 0 ----O (4 = 50.0%) 1 ... 3 ----O (4 = 50.0%) {50.0%} 4 O (0 = 0.0%) {100.0%} - Histogram: Microsoft.SpeechRecognition.SavedAudioLength recorded 4 samples, mean = 2.0 (flags = 0x41) [#] 0 ... 2 ----O (4 = 100.0%) {0.0%} 3 ... - Histogram: Microsoft.SpeechRecognition.SdkInstall recorded 4 samples, mean = 1.0 (flags = 0x41) [#] 0 O (0 = 0.0%) 1 ----O (4 = 100.0%) {0.0%} 2 ... - Histogram: Microsoft.SpeechRecognition.WasRateLimited recorded 4 samples, mean = 0.0 (flags = 0x41) [#] 0 ----O (4 = 100.0%) 1 ...So overall it looks like some issue related to rate limiting...
Can confirm the problem. A year ago I've created a ticket related to same/similar bug here and it was fixed, but now we got it again:
Web Speech API stopped working on Edge starting with v.134 | Microsoft Community Hub
Experince the issue with constant "Network error" on Windows 10 with Edge Version 148.0.3967.70 (Official build) (64-bit).
It affects millions of users. Please consider to prioritize the fix.
The same problem is occurring in Japan. It doesn't work with Chrome, but I discovered it on my work PC and then checked my home PC and the same issue is occurring there as well.
It is getting worse. Today it is not working in the United States.
I also have this issue. Good to know I am not the only one.
Now the speech recognition part of the Web Speech API in Edge is not working for users in Mexico either. It is showing a network error. Is anyone at Microsoft working on this?
Thank you.
Poland has the same issue.
