You may have read it on social networks: you buy a connected V-16 beacon, you go years without using it and, before you know it, the company that sold it to you has gone bankrupt, has stopped paying for its servers and now you have a nice paperweight because, without connectivity with DGT 3.0, that beacon has become illegal. It’s true? No. Plain and simple. When we buy a connected V-16 beacon, the manufacturer assures us that the connectivity is guaranteed for at least 12 years. The manufacturer may offer more connectivity time, as an incentive to purchase, but it cannot offer less. This, like the luminosity of the beacon or the 30 minutes that it must be in operation for at least, is one of the demands that Traffic has set to manufacturers so they can sell their beacons and we let’s buy them with enough peace of mind to be following the rules. Sure, but… what if the company goes bankrupt? It is one of the questions that some users have asked and that has been answered by accounts on social networks like Twitter. It is stated that when a connected V-16 beacon is activated and the required 100 seconds pass, the following process is launched: Protocol A: the beacon sends the data exclusively to the manufacturer’s servers Protocol B: Data leaves the manufacturer’s servers and is forwarded to the National Access Point for Traffic and Mobility Information which is where all activations and any other type of emergency are reflected. The response points out that, in the event that the manufacturer stops selling the connected V-16 beacon, the connection would be broken and therefore we would be left with a luminous paperweight because without connectivity that light is not legal. Insured. To confirm these details, we have contacted some of the companies that manufacture or sell these types of beacons. César Basterrechea explains to us from Atressa Automotivewho have their own beacons, that the information is not true and clarifies what would happen if their company went bankrupt and stopped paying for the beacons. First, he points out, the manufacturer has to register in DGT 3.0 and request a connectivity license. When this requirement is met, the following happens: “My operator sends me the data generated by one of my beacons through an APN and which is protected within a private VPN, the information reaching my Cloud once received, we send it through a VPN with a digital certificate to the DGT 3.0. If my company closed tomorrow, my operator would redirect the data emitted from my beacons to another APN of its own and through its own VPN it would send the data to the DGT cloud” With these words he explains, therefore, that it is the operator that offers its support if the company stops paying for the servers and, therefore, cannot offer the service. They confirm it to us. Asked to the other party, the answer is the same. In Xataka We have contacted Orange, an operator that offers connectivity in different connected V-16 beacons on the market. The company confirms the above, although it points out that, exactly, it is not that the operator keeps the servers of the bankrupt company, it only guarantees that the signal reaches DGT 3.0. “The communication architecture has been defined so that there are two ways to send the data to DGT 3.0: through the manufacturer’s cloud services (which must always be used if there are no incidents) or directly from the operator if the manufacturer’s cloud service is not operational (manufacturer bankruptcy or massive drop in its cloud service)” It’s not easy. The truth is that although we have confirmation from this beacon manufacturer And getting there is not easy. In the Resolution of November 30, 2021 which details the requirements that a V-16 beacon must have connected to be valid, it specifies that the manufacturer must have support to offer the service if it cannot be performed, but nowhere does it specify whether this company should be the operator, as Atressa Automotive tells us. This text explains the above-mentioned details of protocols A and B. Subsequently, the following is stated: The implementation of a device with these characteristics requires having a standard channel and a common language. Additionally, defining this standard also makes it easier for a third party to perform these functions if necessary due to the existence of a problem in the information systems of a manufacturer. The data model that the messages that V-16 devices send to their manufacturers’ information services must comply with is defined below. a hoax. Although with the connected V-16 beacons we have had a lot of controversy and we know that there are even those who has demonstrated cybersecurity risksThe truth is that this time we are facing a hoax. The DGT has actively repeated that when we buy a connected V-16 beacon we are guaranteed access to DGT 3.0 for 12 years. And although the protocol does not clearly detail whether a specific company must take charge (operators, other manufacturers…), it does specify that it must guarantee backup to keep the service active. Photo | DGT In Xataka | V16 beacon without eSIM or connectivity: what the DGT says about them from 2026