Uncover the true cost of unreliable connectivity

The True Cost of Unreliable Connectivity

Tired of dealing with connectivity headaches?
Wondering how downtime or poor connections are quietly draining your business?

We’ve got answers—and they’re ready when you are.

Watch our on-demand webinar to discover:

• The hidden costs of unreliable connectivity – and how it impacts your bottom line
• How to ensure seamless, reliable IoT performance across your operations
• Real-world strategies to scale IoT connectivity without the drama

No scheduling. No stress. Just insight when you need it.

Watch now, on your time.

Transcript

Hello, everyone, and welcome to Pelion's new webinar, The True Cost of unreliable Connectivity. 

We're very happy you could join us today, and we've got lots to talk about. 

My name is Judi Lembke, and today we're joined by two experts in the connectivity field, Alan Tate, CTO at Pelion, and Fredrik Stålbrand, principal analyst at Berg Insight. Welcome, gentlemen. 

Thank you. 

Before we get started, a little bit of housekeeping: We're eager to get your input, so please feel free to put any questions or comments in the chat, and we'll get back to you as soon as we can.  

So, without further ado, let's get started. Fredrik, you've been an analyst for a long time. Can you give us a brief overview of Berg Insight and your role there? 

Thanks, Judi, absolutely. So, I'm a principal analyst at Berg Insight covering the IoT connectivity markets, which I've been doing for close to a decade now.  Berg Insight is an analyst and consulting firm based in Sweden, and we specialize in IoT. 

So, we produce research covering various markets and technologies in the space. A couple of focus areas that we cover are vehicle telematics, smart utilities, industrial IoT, and connected healthcare. 

We are 12 analysts today and serve customers all over the world. 

Fantastic. Alan, tell us a little bit about Pelion and your role as CTO. 

Yeah, sure. Pelion’s been around for over 20 years actually, primarily focused on what was M2M and now in the IoT market. 

I've been part of this company's many forms since around about 2006 and have seen it from startup through the scale up through to spin out and then back out the other side. So today I look after the technology and delivery brief. 

We've got customers across a wide range of sectors that are classed as M2M: telehealth, telematics, and various other industries and areas that we're very strong in. So, if you have a smart meter in your home, chances are it’s running on our connectivity. 

We've got agreements with Hive, so we do EV charging, and we've got a large footprint of connected Wi Fi and transport Wi Fi. So, if you're on one of the trains or a few buses in the UK, there's a good chance you'll be running on our network. 

Fantastic. OK, so let's dive in. 

Today, we're talking about the true cost of unreliable connectivity. So, let's start with the big umbrella question. 

In a nutshell, Alan, what does reliable high-performance cellular IoT connectivity look like? 

At the end of the day, [it means] something that just works, something that you don't have to put a lot of effort into, something that you can rely on for your business. 

At the end of the day we all know what bad internet looks like – we know it's frustrating, it's incredibly annoying, it's sometimes worse than having no internet at all, so that expectation of connectivity is something which is really strong for people. 

We find that having downtime events, having connectivity issues where you end up not being able to rely on your connectivity is something which is really damaging to both brand recognition and essentially the health of your solution. 

All right, and Frederick, why is reliable connectivity the foundation of any successful IoT deployment? 

Yeah, just building on what Alan said, if we think about our personal lives, we're obviously very dependent on connectivity. 

And for enterprises, having bad connectivity – that means that the whole operational processes are disrupted, as many of their systems depend on continuous connectivity. 

So, the value derived from IoT is largely dependent on availability because you want to make sure that your processes in place work, that you can accept payments, that you have an accurate picture of your operations and assets when it matters. 

So, let's dive in a little bit more into availability, and this is for either of you. How does IoT connectivity, reliable or unreliable, impact the overall performance and efficiency of an organization? 

It's about what the organization's doing with the data. Fredrik mentioned there are payments, that if you're unable to take a payment over your connectivity method, then you're losing money. 

If you're relying on that data for security, if you're relying on that for a manufacturing process, if you're relying on that data in any way, interruption to that is an interruption to your service, interruption to your process. 

So that's where that criticality of data really comes in, how you're communicating backwards and forwards from your assets, and then where you put your risk tolerance for that not being available. 

I was going to say IoT connectivity is a type of infrastructure, right? So, it has this great impact on the overall performance, and it's infrastructure that enterprises consume as service. 

So, yeah, for the buyer, it's important to understand these different nuances. I think there's an interesting part of what you're describing. I think for too long people thought IoT connectivity isn't actually reliable. It's not an infrastructure service. 

And from our perspective at Pelion it is. There's nothing stopping us delivering this as a high availability, high reliability service because people understand how to deliver reliable connectivity in multiple other fields. 

We're adapting those technologies and capabilities to IoT where there are some different challenges, mostly number of devices, scale, and the fact that you're on a wireless network for 50% of your transit. But yeah, it's very much today becoming a critical infrastructure service and, and we back it as such. 

OK, so it is critical, and it has to be always on and always reliable, but outages are a fact of life in the IoT world – unfortunately, we know they happen. In fact, a recent report said 97% of companies deploying IoT suffer outages on a monthly basis. So, what is the state of connectivity uptime today? How do you see it, Alan? What's acceptable, what's not acceptable? 

I think these are large, complicated systems, so you will always see issues. But I think the challenge that we have is that there's an evolving set of best practices in IoT. 

So, from our perspective, we can have the most reliable network in the world, and it can be interconnected in many, many carriers. But if the device isn't set up to take advantage of that, or there are gaps in those processes, then customers are going to issues that that are reported. I mean, very rarely is it something that we would see solely being a connectivity issue, but you then have the core way things that end up getting attached. 

Your device can't get attached for a period of time, so it gets confused, and it shuts down or it gets disconnected from the network or the application servers are just not designed to handle the volume of connections that come from an IOT device. So, it's very difficult to get all these bits right. 

So, you see enterprise solutions or even SME-based solutions, which are being rolled out, and they're fine to a point, and then suddenly they get scale, they get volume, and then they begin to have a number of challenges. So, having very high availability, connectivity is one part of that. 

But overall, designing devices and designing applications in a way that are aware that they're in a potentially messy environment is something which is incredibly important for the overall solution health. 

Well, we'll get to hardware in a minute, but what about cost implications, Fredrik? If we look at this table, it's clear downtime has significant implications. So how does, unreliable connectivity lead to unexpected operational disruptions, financial losses? 

In many cases, downtime directly translates to lost revenue, but it could also translate into higher costs, because you need to change processes in various ways. I think the retail examples are good examples: if you cannot accept payments, you cannot charge the customer. 

There’s been many surveys on this. One has been conducted by Open Gear, which is an enterprise networking company where they've asked hundreds of CIOs about the cost of downtime. 

And it shows that the average cost of a single minute of downtime is 4000 dollars. This adds up, of course, if you accumulate this over the course of frequent outages, which are not uncommon either. 

So, that's monetary costs. What about reputational costs, reputational damage? 

Right, yeah, it definitely has an impact. I mean, downtime damages trust with customers and users of these systems. And operationally, disruptions manifest in various ways whether you're a public transport operator or a healthcare provider or retailer. 

What about the cost of fixing connectivity failures versus investing in a reliable connectivity upfront? Alan, what's your take on that? 

I mean, it's more expensive to retrofit. Essentially the challenges come down to if you're lucky enough to never have any issues to your cost of service. It is always going to be quite low, but you have to look at the total cost of ownership for your solution at all points. So, there's no guarantee that buying the best device and having the best application is the right answer, because if you don't have reliable connectivity in the middle, then that very smart device may as well be a rock. 

So, it all comes down to you have to look at your solution in its entirety: select good hardware, and make sure it has reliability, and it has connection management. You have to design your application to take in the fact that you're going over essentially a wireless carrier, which means you'll have packet wash, you'll have retransmissions, and you need a connectivity provider that understands what it means to run a high up time capability, because at the end of the day, your application can be perfect, your device can be perfect, but if you're continuously dropping packets through your provider or they're continuously offline, you're not getting the service that you need. 

So, IoT is one of those ones where it's a collection of parts that really outperform the whole, and you need to get to that point where the data is something which is most reliable out of it. That's how we work together for various different partners and work for our customers to help them understand what they need to put in place in order to be able to get a very high guaranteed level of service. 

And Fredrik, in your experience, do you think businesses underestimate the cost of downtime and do they really take that on board what it could cost them if they have an unreliable provider? 

Yeah, I think it's easy to focus on the immediate, easily quantifiable costs. You have the short-term revenue impacts or direct costs, but then you also have these more hidden costs that are not that easy to quantify, as we've talked about. 

So, it could be related to changing processes, changing two processes that are less efficient, or you need to bring in more staff and pay overtime costs and stuff like that. 

The promise of IoT disappears if it's not right. That's the challenge. And I think the thing about it is that getting it wrong is something which is really costly. So, if you deploy a solution in the field and you've then got to go to a truck to repair it and make some changes to it, or you lose access to that device over the network for any reason, then that's where you eliminate your savings for having an IoT product. 

I think there's a number of studies done that show what's best for people to adopt a wider use of IoT solutions, and it's return on investment. People cannot map the return on investment because of the risk of ‘if I deploy these devices and they're supposed to save me money by doing X, but whenever Y happens, then I've got to go and do something about it’. Building a model that shows what the return investment of that is, but also what the risk is, is very difficult for them – that justification for your CIOs and others to sign off on. 'I’ve already got a process that cost us X it's known. I could have this process that could save me why, but it could then cost me a huge amount else.’ 

That's the area where the adoption is slowed down because people don't have the trust that this is enterprise grade yet. You know, there isn't yet an IoT solution where someone walks out and one day I hope it's Pelion that says, you don't get fired for buying IBM. I want us to get to that point where you don't get fired for, you shouldn't get fired for choosing. 

But I mean, it's a case of I want us to be that byword for this is enterprise grade, this is enterprise security, this is enterprise availability as much as you would get from having two fixed lines attached to your device. 

And Fredrik, just briefly, I don't want to dive into this too much, but you mentioned staff. And when you're adopting IoT often it means you have to adjust your business model and you need different competencies within your staff, which is also something to think about to mitigate issues.  

So let's talk about mitigation. 

What are some potential mitigation strategies to avoid unplanned downtime. Alan, what are the key factors to consider when choosing an operator for reliable cellular connectivity? 

I mean, it's looking very much at what your use case is and how critical your data is. So, to give you an example, we have smart meters that wake up every single morning and they must be able to do one message. And that's it. So, the device is tuned for that, the time on the set for the battery requirements. They need a provider that they know. They do multi-network. They've got dedicated access into our systems, and they know that it must work for that once a day or once a week. So, they've designed their entire solution around being able to handle an incredibly high load for a very short period of time. 

You've then got other customers who are looking at, you know, how do I stream data all day, 24/7 and all of that, and they're then working with us to make sure that they're choosing someone who has opt out that they can show that has access to multiple networks as to where they need it, but then can offer them redundancy and peering into their control systems and visibility to understand what's going on. 

So, it really depends on the use case, it depends how you're deploying your application services. It depends how remote your asset is. So, someone who's doing a CCTV camera onsite is different from someone who has a smart meter and an industrial site, or someone doing CCTV and it's a pole somewhere and you have to go there. 

These are all decisions you have to make that come down to how well you're going to design your device to be able to handle not having to go and someone has to go through it all the time, all the way through to choosing a network provision which is redundant, reliable, and transparent enough that you understand what's actually happening and you're able to design your solution around that. 

So, Fredrik, how can a company assess the reliability of an operator's network before committing to a plan? And would it be different for someone new to IoT, to someone who has been in the IoT game for a while but wants to maybe find a new provider? What, should they be looking for? 

So, there are a couple of different things that one can look for. I mean, it's related to coverage, it's related to various mitigation strategies. It really depends on the business case. 

And for me, it's usually around transparency of service. So, we work with about 10+ mobile operators around the world and a huge number more for roaming, and the ones that we work best with are the ones that we can have detailed conversations with and an understanding of how they're set up. We can integrate with them at more than one point of presence, and they have redundancy and they have a similar service model and redundancy from what we do. 

They're quick to tell us as we are to our customers, if something's going wrong and being able to communicate that effectively. So for me, transparency and reliability are probably the two things I look for when I look for a mobile network in order to provide service to our customers, because if you can't get that from the carrier you're working with, you can't pass it on to your customers, and you can't stand behind that if you don't have the visibility of what's actually happening. 

What about the potential trade-offs between price and connectivity reliability when choosing an operator? 

 I think the question answers itself. If you're trading off reliability for price, then your data is obviously not critical and not valuable to your business. So, if you're trying to do something at the worst possible cost, then your entire solution is generally built around that concept. And if you get the data, great, if you don't, then there isn't the value there. 

If the data in your IoT solution is valuable enough, people will invest in order to make sure it gets there. And that's the difference in a low-cost provider that turns around and says, you know, oh, you know, charge me once and this will work forever, versus someone that says, we'll actually stand behind you for service level. 

All right, and how do solutions like multi-network SIMs Fredrik help address the challenges of IoT connectivity, especially and particularly in remote or rural areas? 

Right. So, yeah, multi-network SIMs, uh, it essentially means that you have access to multiple different networks. In remote areas you have often inconsistent coverage because, you know, mobile operators, they don't prioritize these areas as much as they do like cities. So, if you have multiple options, these solutions expand the effective coverage area. It's like a Venn diagram, almost. So, you ensure that the device connects to the strongest available network at any given moment.  

You get a large number of mobile operators that cover 99% of the whatever country they're in. Unfortunately, if there's more than one, it's not the same 99%. That's the same – you get this overlap area where one works and one doesn't. And I mean, yeah, there's the benefit. There's lots of industries where that's really important, things like energy and renewables, where they're typically further away from people. 

You see that in some metering opportunities, you see that some last mile opportunities, aqua farming and others, it becomes critically important that you cover as much ground as possible in order for them to have the best solution. 

And what about low signal or high latency environments, Alan. What role do connectivity solutions like Pelion’s play in keeping devices connected in these environments? 

I think the thing is we do our best to not introduce any additional wait and see or additional challenges in our network for them. 

From our perspective, if you can gain the touch on the cellular network and we can open an IP connection to you, then you should be able to get the same level of service as you would across any other communication method. 

And what about eSIMs, Frederick? We're hearing a lot about them and there's a lot of people using them. What do they bring in terms of reliable connectivity? 

It's a good question. ESIMs in themselves may not be better or worse. It really depends on how you implement it, which is a very consultancy type answer. But as a starting point they're physically more reliable because it's a chip soldered onto the PCB of the device. 

Another point is that they're remotely programmable, so you can upload different operators. 

I think one of the more interesting points related to reliability is a couple of features that will be implemented in the new uh specification, SGP 32, and those are related to fallback and different types of fallback scenarios, so if the primary profile fails, it will fall back to a secondary profile or the bootstrap profile. There are a couple of things happening there, which are interesting and will start to become implemented in the coming years. 

Alan, what's your take on eSIMs and reliability? 

We've already seen the benefits of them. Since about 2018, we've been putting out all our settings of the YCC enabled OSE, um, so that's SGP.32 today, so in terms of specification, we're trialing and moving towards SGP 32. Presently, for us, it's mostly about assurance and assurance models, talking to our customers. 

So, if you go into a relatively contentious roaming environment, let's say like the US and some of the providers going in there, you can't guarantee for potentially the lifetime of an asset that the same agreements are going to be in place. 

Even the same providers are going to necessarily be in place, and they want some sort of assurance that if my radio environment changes or my commercial model changes, I want to be able to, to swap that subscription to something local or a different provider that has that capability. 

On our website we referenced our blog post, where we did 25,000 of these for one of our customers in the US doing door entry systems. They were not happy with the reliability of one of the providers and also the cost points being introduced on them. They said, hey, we want to go to a local solution here and we want you to help enable it. So, we did a swap from a European-based operator to a North American-based operator with pretty much zero device loss. And, you know, that really points to the promise of the technology.  

Because we're managing all those connections, and consistency of service across both, we can manage it very closely to give that very high level of uptime. But I think the downside of eUICC and as it is today is it's incredibly fragmented. 

SGP 32: one of the promises of it is to kind of try and change that so that there is Less ‘small garden’ effect, because today we can only really work with eSIMs we provided and we've delivered and for any of our customers, you know, they had that capability back then. But as I said, we made that decision to make sure that our customers were insured against future network changes. And if the device can support it, we can generally do a profile spot for them. But in the future, it will allow you to essentially personalize to Pelion at that point, and then we can take over that capability and we can drive from there. 

And you mentioned devices, so hardware considerations like modules or antennas, Fredrik, what should businesses prioritize to ensure reliable connectivity? 

So, the choice of the module is largely driven by the network that you would like the device to connect to. So, you need to think about do you require 5G speeds or do you more prioritize battery life and what requirements do you have on that size and costs etc. So, it's really a balance there of sort of matching the module to your application. 

And antennas – it's an interesting hardware category. It often doesn't get a lot of attention, but it's really one of the biggest determinants of connectivity performance. So, if you have a poorly designed antenna or poorly placed antenna, it can lead to weak signal strength or total connectivity failure even if the module and network are functioning perfectly. 

You can see this on top of these electrical cabinets sometimes. They're these really old antennas, they are just like banged off almost because of different conditions in the city and they might not be functioning. So, when it comes to these components, it's important to engage early in the design process to avoid expensive redesigns and issues post-deployments. So do the work pre-deployment. And many of the vendors also offer reference design and integration guides and support services to ensure optimal implementation. 

We know that IoT is growing and it's an ever-growing market. Customers, businesses – they have a choice of an MNO or an MVNO like Pelon. MNO owns the networks. Pelion takes levereges those networks. Alan, how do you see the balance shifting between MNOs and MVNOs in terms of market share, growth, which model is best suited for scaling IoT deployments? What's your take on all that? 

Again, this is one of the nuances. It really comes down to where you're deploying your solutions. So, if you've got something which is a single country, high-capacity data network access, and you really don't need more than one provider, chances are your local MNO will probably be able to offer you something which is compelling. 

The moment MVNOs begin to get interesting is when you have to do something slightly more complex that isn't off the shelf of the operator. That's something that you're looking to do either on more total cost of ownership, you're looking to do across multi-region, you need access to more than one carrier for coverage or regional reasons, and you potentially need a deeper integration than what the original MNO will offer you at a reasonable price point. So, if you were to go and replicate the operator it's going to take a large amount of time. We're already there, we can give you segmented access, it'll just work. 

I think that's what it really comes down to. It comes down to your aspirations and where you're looking to grow. If you're only ever going to be doing a small deployment in one country, then probably a local MNO will do you fine. 

The moment you need to go beyond that, you need to go to more than one carrier to global or regional, then that's when you look for MVNOs that can offer that a differentiated level of service. So, businesses really need to think not just about today but also about tomorrow and where they're headed. 

You know, we've done a lot of migrations from operators directly into our service primarily for that reason. The MNO, their biggest strength is they can offer their network at whichever price point and capability they choose. The biggest downside is they can only offer their network. 

So, we see them at a point where they have customers they don't necessarily want to lose. They still want to see the revenue in their network, but they're aware that customers are outgrowing them, and then they'll potentially work with us at that point to migrate the customer or innovate them or do some sort of sell off arrangement which allows them to keep the revenue, but also that customer to expand in regions that they're no longer able to support. 

What about new technologies? 5G – I mean, I guess it's not that new anymore – but it's still fairly new, and then there's other technologies coming. What role, Fredrick, do they play in ensuring reliable connectivity? 

There are a couple of trends that we see related to reliability. For example, enterprises that need really ultra reliable connectivity, they build their own private 5G networks at their facilities. It's quite rare, but some do it. 

Then there is the trend of integrating cellular connectivity with the cellular connectivity solutions, and satellite connectivity is now a part of the 3DPP standard. So, if the device is out of cellular coverage, it will connect to a satellite network. So that's sort of an additional redundancy mechanism that is put in place through the satellite networks, which is quite interesting. It's not commercially available yet but it's starting to get implemented. 

What’s your take, Alan? 5G satellite, all of that. How do you see it? 

I think that it just depends on the use case and the requirements of the device. 5G is a wonderful technology, but it grows a massive gambit across, as I said, ultra reliable latency-based applications also into redcap, which is the kind of next generation ATC style applications. 

Satellite is an interesting use case, you know, there will always be areas that cellular cannot service, so having something where you're able to offload on to cellular or the applications where we can see whether they're doing things like MBRT from space and other elements like that is an interesting use case for the raw data requirements which are there. 

Again, a lot of these things are about selecting the thing, the technology which is best for your use case. And I would argue that there are some things about, a lot of IoT is about looking at how you future-proof. 

It's looking about how you make decisions, not just for today, but for the lifetime of your asset. 

And that can vary wildly from various different implementations, you know, we've got Smart meters or industrial use cases which are expected to be out 15+ years, and then you've got ones which are more closely aligned to consumer replacement cycles where they'll be, you know, junk for we waste in 24 months and the newest technology we put in and everywhere in between. 

So, I think the requirements really come down to what you're using it for, how valuable is your data, and what reliability constraints do you have. 

And you mentioned futureproof, Alan. So, Fredrik, what factors should businesses consider when scaling IoT deployments, especially internationally? 

I think it can be a little bit difficult to see how the needs of the business will evolve, but, it's also about being clear about what networks can be accessed, how are they accessed, and what will happen if my device crosses into another country, for example, and also the management aspect. Can you manage that at scale and what type of controls do you have? 

And Alan: connectivity management Fredrik mentioned. We have the Pelion portal. Can you tell us what role does it plays? 

I think what I was going to say on Fredrik’s point was essentially it comes down to consistency. So you want to deploy a solution worldwide that's not fragmented, you want to be able to understand what networks they can connect to, and you want to be able to manage it as much as possible, essentially, and be on a technology stack that will maintain and evolve for the lifetime of, of your capabilities. 

So, the last thing you want to do is to have 15 different relationships covering 20 different countries. It's a mess to manage and that's what we do as business, and it is challenging. So, you don't want to go out as an individual provider providing your service and have to deal with the fragmentation that inherently comes from buying global solutions. You want something that just works, you want something that's effortless from that perspective. 

So, Fredrik, we spoke earlier, and you had some of the top mistakes businesses make when setting up IoT and connectivity and how they can avoid them. Can you walk us through this a little bit? 

Yeah, the price aspect we talked a little bit about, it's easy to focus on price, of course, but cheap connectivity, it may become expensive if it breaks, and if you have downtime costs it will be more than what you've saved on cheap connectivity. 

And planning for scale we just talked about going into more countries, more regions, and you know how you will manage that is a key part as well of that. It's important to plan for, and then the coverage aspect is connected to that, of course. What are the networks, how are they accessed? What happens if the networks go down or if your device crosses into another country, what happens? So just be clear about how that works. 

And Alan, we also spoke earlier, and you gave me your top three pieces of key advice to businesses looking to scale while maintaining reliable connectivity. Can you tell us about these? 

We didn't compare notes, but I think they're probably around the same concepts. Essentially beware of people who are telling you, we can do this for nothing, this will work in a certain way, it will always work 100% of the time, you have this, you have that. 

IoT is hard. There's no silver bullet. You have to make sure you've built everything together. 

I'd say you need to partner with providers who deliver service backed by their experience and capability, and they're willing to stand behind it. You need to be able to understand how they're delivering that service, who their operability relationships are with, and generally, someone that should be above board and who understands what you’re connecting to and what level of service you should be able to expect and what cost that's going to be. 

And if someone can't stand behind that and say the service is doing this and it's doing that, then to me, it's not a real vision, it's someone who's selling paperwork. 

You just mentioned service – we're just about out of time, but I actually just wanted to ask you, when you're choosing a provider and either of you or both of you can answer this, how important is service in the long term, short term, you know, in terms of futureproofing, what do you need from your provider besides the connectivity? 

Well, I think it comes down to choosing the right people to work with on the support side, but also in terms of advisory, having a partner that can give you good advice on what is happening in the marketplace when it comes to new technologies and so forth. Not every new technology may add value for your specific use case, and having a partner that can assess that is very important, you know, on top of the operational services and so forth. 

A friend for me is a partner who's invested in making sure your solution works. That's when I work with people, that's what I want to see when we work downstream, that's what we try and engage in. We want to make sure that if you're on board with us, then it becomes a scalable solution that we can help support for you into the future. 

You know, from my perspective and many years of various different forms of service management, there is no benefit in bringing something on that you can't support longer term. It just becomes high cost, and you upset the customer. It's not something that you're going to be able to deliver against. And that comes back to the total cost of ownership and price conversations because if you're not being upfront, you're not being honest with the customer about the way the solution will interact with what they're trying to do, then you're both setting yourselves up for a high cost builder. 

That is all the time we have for today. I want to thank both you, Alan Tait, CTO at Pelion and Fredrik Stålbrand, principal analyst at Brig Insight. Thank you for joining us today and also thank you to all of you who joined us to hear these remarkable insights. 

This expertise has been really good and I've actually learned something today. For those of you who are watching, make sure you check your mailbox for the report Berg insight has done with Pelion around unreliable connectivity. You'll find a deeper dive into this topic. 

And if you want to listen to this webinar again or share it with a colleague or a friend, you can watch it on demand at Pelon.com. 

If you're looking to explore how to safeguard your IoT deployments and ensure effortless reliable connectivity, don't hesitate to reach out to the Pelion team. 

And that's it for us today. Thanks again, everyone, and we'll see you in our next session.