News / Voice
Wanadoo VoIP fault blocks incoming calls
On 2 February 2006, Wanadoo acknowledged a fault in its Wireless and Talk VoIP service. Calls originating on landlines or mobiles could not reach customers on the internet-telephony platform during the incident.
What failed
The company’s status notice, as described in the source, identified the problem at the connection between traditional telephone networks and the IP voice service. Wanadoo said the outage affected the service generally and that normal operation had returned by the previous afternoon.
A reminder about interconnection
VoIP can carry voice over data infrastructure, but users still depend on links with conventional telephone networks. A fault at that boundary can prevent calls even when the customer’s broadband connection is working. This report is an account of one 2006 outage, not a statement about present service reliability. The account does not identify the underlying technical cause, only the affected call path and restoration.
The failed route was into the service
Wanadoo described a fault affecting calls that began on conventional phones and were meant to reach Wireless and Talk users. That direction matters: an internet connection at the recipient’s premises could be healthy while the caller still could not reach the number. The incident therefore isolates an interconnection dependency rather than treating all voice availability as a property of the customer’s broadband line.
A call crosses more than one domain
For an incoming call to complete, the traditional telephone network and the IP voice service had to hand the call from one environment to the other. The status notice located the disruption at that boundary. This provides a concrete support scenario: a user may report that internet access works, yet family, customers or colleagues calling from mobiles and landlines cannot get through. Testing only the customer’s own connection would miss the affected path.
Restoration does not identify the cause
Wanadoo reported service restoration on the preceding day, but the account does not name the technical cause. That limit matters when interpreting the event. It supports a conclusion about the failed call direction and the importance of interconnection monitoring, not a claim about a particular component or a general quality judgement. For a voice provider, the trade-off is clear: a service can gain flexibility from IP delivery while still needing dependable interfaces to the older networks from which many calls originate. The stated restoration time confirms that the disruption ended; it does not turn a completed broadband session into evidence that the separate incoming voice route was healthy during the fault.