- Home
- System Status
Service health
System Status
Current state of the CodigoMorse.io translator, decoder, audio engine, API and website. The tools run in your browser, so the most common reason for a problem is on your device; the checklist further down solves nearly all of them.
Morse Code Translator
Text to Morse and Morse to text, letter breakdown, copy.
Uptime figures are indicative 90-day values compiled from our monitoring and updated manually when this page is reviewed; they are not a live feed. Because the translator, decoder and audio tools execute entirely in your browser, they keep working even during brief hosting interruptions once a page has loaded.
At a glance
Key figures
Representative values from recent monitoring. The website is served through Cloudflare and a LiteSpeed cache, which is why pages load in well under a second from most regions.
Last 90 days
Incident history
Every event that affected a component, with its duration. All listed incidents are resolved. The browser-based tools were not affected by any of them.
| Status | Time | Component | Details | Duration |
|---|---|---|---|---|
| Resolved | 2026-03-28 14:02 UTC | Ingestion pipeline | Packet-loss threshold exceeded in the AP-NORTHEAST cluster. Automatic failover started; no user-visible impact on the website. | 14 s |
| Resolved | 2026-03-27 09:44 UTC | API layer | Elevated latency during scheduled maintenance of the primary database node. API responses slowed; the browser tools were unaffected. | 2 min 12 s |
| Resolved | 2026-03-26 23:12 UTC | Core encryption | Entropy pool exhaustion in the cryptographic module. Re-seeded from the hardware random source. | 1 s |
No open incidents. If you are seeing a problem that is not listed here, it is probably local to your browser or network; try the steps below and then tell us.
What to do if a tool fails
Because the tools are JavaScript running on your device, almost every failure report we receive has a local cause. Work through this list in order; each step takes a few seconds.
- Reload the page once.
A partially loaded script is the most common cause of a translator that "does nothing". Use a normal reload; on a stubborn page, a hard reload (Ctrl+Shift+R or Cmd+Shift+R) fetches fresh files past any cache.
- No sound? Interact first, then check the volume.
Browsers refuse to start audio until you tap or click the page. iPhones also silence web audio when the ring/silent switch is on silent. Tap the page, raise the media volume, then press Listen again.
- Seeing a "?" in decoded text?
That is not an outage: it marks a group of dots and dashes that is not a valid character. Check the spacing (one space between letters, a slash between words) and that you have not pasted typographic dots or dashes. The reading guide explains the rules.
- Disable content blockers for the page.
Some aggressive blockers strip the script files that power the tools. Allow codigomorse.io, or try a private window, and reload.
- Try another browser or device.
The tools support every current browser (Chrome, Firefox, Safari, Edge) on desktop and mobile. Very old browsers without Web Audio support can translate text but not play it.
- Still stuck? Send us the details.
Email [email protected] with the page URL, what you typed, what happened, and your browser and device. We answer within two business days and we fix confirmed bugs quickly.
Checking the API
Developers can probe the API directly: a GET /status call with a valid key returns 200 OK when the service and the key are both healthy. The API documentation lists the error codes to expect otherwise. A 429 means you hit the rate limit, not that the API is down.
How we monitor
External checks request the home page, the decoder and the API health endpoint every few minutes from three regions and alert us on failure. Server-side, we watch error rates and response times from the web server and the cache layer. This page is reviewed and updated by hand after any event; it is not generated automatically, which is why the figures above are labelled as indicative.
FAQ
Frequently asked questions
Is the Morse code translator down right now?
All components are operational as of the last review date shown at the top of this page. If the translator is not responding for you, reload the page and run through the checklist above; a local script or cache problem is far more likely than an outage.
Why does the audio not play?
Browsers block sound until you interact with the page, and phones in silent mode mute web audio. Tap the page, check the volume and the silent switch, then press Listen again.
Do the tools work offline?
Once a page has loaded, the translator, decoder and audio player keep working without a connection, because all processing happens in your browser. Navigating to another page needs a connection again.
How often is this page updated?
After any incident and on a regular review schedule. The figures are compiled from our monitoring and entered manually; they are indicative, not a live dashboard.
Where do I report a problem?
Email [email protected] or use the contact page. Include the page URL, your browser and what you expected to happen.
Everything is running
Head back to the tools, or read the API docs if you are integrating.