intelligence_src_1b0ea7addf33a18b0f
- Source-provided label
- Publisher RSS metadata
- Evidence class
- mentioned in report
- Confidence
- Not reported
- Observed
- Jan 31, 2013 00:00 UTC
- Retrieved
- Oct 13, 2026 19:07 UTC
Creating a low-latency calling network
RedPhone is our mobile app for end-to-end encrypted voice calls. When we talk about RedPhone, we tend to emphasize the cryptography, and how using it can help keep your communications safe. What we don’t talk about as much is the VoIP application underneath all of that, which it turns out was actually the hard part. When we were developing RedPhone, we discovered that the cryptographic aspects of it were relatively straightforward. What we didn’t anticipate was how difficult the mechanics of delivering high-quality, low-latency, and highly available voice communication would be. This describes the basic strategy we developed for the network side of low-latency and highly available calls. Read more...
Reference details
- Source category
- research-report
- First reported
- Jan 31, 2013 00:00 UTC
- Last reported
- Jan 31, 2013 00:00 UTC
- Catalog updated
- Oct 13, 2026 19:07 UTC
- Record ID
99c546e9f3a6f6d499fd129b2555a1eead511181713628654f0d977ad6b3176b
Published indicators
Network indicators are visibly defanged. This page does not make them clickable or send them to another service.
No validated file hashes or network indicators are stored for this record.
Source observations
This record contains metadata and attribution only. It does not host, download, unpack, render, or execute malware samples.
Feed collection status
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
1 sources: 0 stale, 0 needing attention, 0 paused, 0 unverified.
Review source update dates and status
- intelligence_src_1b0ea7addf33a18b0fRecent successful batchLast successful batch: Last attempt:
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.