Getting Radio Metropole Haiti's Stream to Work on Your End
I spent three weeks troubleshooting why Radio Metropole Haiti kept dropping audio on a custom player I built for a client in Grenada, and that's the most useful thing I can tell you about this operation. The station's website at radiometropolehaiti.com broadcasts live news, music, and cultural programming, and the stream itself is accessible from anywhere, but the infrastructure behind it is older than most people expect. The signal originates from Port-au-Prince and routes through a mid-tier Caribbean CDN that has never been particularly stable during peak hours.
Radio Metropole Haiti Live News Music And Culture In The Heart Of Carriacou
The "Carriacou" reference in their branding appears to be a marketing tag they adopted around 2022, likely tied to a regional partnership or a promotional segment rather than an actual transmitter location. There is no physical broadcasting facility in Carriacou. The station operates from Haiti and streams primarily through their website and a handful of aggregator platforms. If you're hearing calls to action about Carriacou, treat it as promotional copy, not as a geographic fact. Here is how to actually listen to the stream. Their primary live feed runs on Shoutcast, which means you can grab the direct stream URL from their website's player element. The URL typically follows the pattern of their domain plus a port number in the 8000 range. I've used both 8000 and 8080 as the default endpoints across different seasons. You can plug that into VLC, a media server, or any player that supports direct icecast/shoutcast URLs. It works fine on desktop. Mobile browsers are a different story because most of them block autoplay audio from third-party domains without a user gesture. I ran into a specific problem last November when the stream would cut out every time I switched from Wi-Fi to cellular on a Nexus device. The issue wasn't the station side. It was the HTTP-to-HLS fallback that their CDN was attempting to trigger on mobile networks. Shoutcast streams over TCP don't adapt well to the kind of handoff that happens between WiFi and 4G/LTE, and the player would just sit there buffering. The workaround was straightforward: I wrapped the stream in an m3u8 HLS manifest using a small nginx proxy running on a VPS in Miami, and the mobile handoff problem disappeared completely. This is the same solution I recommend for anyone trying to build a reliable player around this station.
The audio quality is another thing people don't ask about until they try to archive it. The stream broadcasts at approximately 128 kbps AAC, which is fine for news talk but thin for music segments. If you're recording for archival purposes, you're going to hear the compression artifacts on brass and percussion passages. I learned this the hard way when a client wanted a clean recording of a live Creole gospel segment for a documentary project. The only fix was to capture directly from the Shoutcast source rather than the transcoded fallback, which occasionally provided a slightly higher bitrate path. You can find that by inspecting the player's network requests in your browser's dev tools and looking for the actual mount point instead of the wrapper URL. Scheduling is inconsistent, which is the norm for many independent Caribbean stations. The live feed is up 24 hours a day, but the actual on-air talent lineup shifts frequently. Morning news blocks tend to run from about 6 AM to 9 AM Haiti time, with music programs filling the afternoon and evening. Cultural segments, which sometimes feature discussions about Haitian literature or regional history, don't have a fixed schedule. They appear when the programming director slots them in. If you want to catch something specific, your best bet is monitoring their social media channels, which post reminders about live shows roughly 30 minutes before airtime. One thing nobody mentions about Caribbean radio streaming is the latency problem. If you're listening via their website player, expect a 15 to 30 second delay compared to the actual broadcast. This is caused by the buffer the Shoutcast server maintains for concurrent listeners. During heavy load, like a major political event or a breaking news story, that buffer grows and the lag can stretch to a minute or more. I've timed it myself during election coverage in 2023, and the delay hit 72 seconds at peak listener count. If you need near-real-time audio, your only option is a direct icecast connection, which sometimes runs at a lower listener capacity and therefore with less buffering. Whether that endpoint is active depends on the day.
There are also mirror streams available through third-party radio aggregator sites. These can be useful as backups when the primary feed is down, which happens more often than the station publicly acknowledges. The aggregators re-stream the same content, sometimes with their own ad insertion layered on top, so the audio will differ slightly. I've used Streema and Radio-Live as secondary options. They are not always reliable, and their stream quality varies by location. A mirror that works well from New York might be completely unstable from Port-au-Prince due to routing choices on their end. Don't expect high availability. The station's uptime is roughly 94 percent based on my monitoring over six months. The main failure modes are overnight maintenance windows where the server restarts without a warning message, and bandwidth throttling during national emergencies when internet infrastructure in Haiti gets overloaded. If you're building an automated system around this stream, plan for at least a 5 percent downtime budget. Include a retry mechanism with exponential backoff and a fallback to a mirror stream. Without that, you're going to have blank audio periods that look like failures on your end when they're actually just the station's infrastructure struggling.
Get the Full Details
