Hi Venkatachalapathy,
Our multi-cdn architecture should take care of this for you. It's been designed so that there is no single point of failure, and there should never be a case where the utag.js is not served, and hence no need to publish to any additional locations. The service monitors from multiple locations around the world and will always serve from the quickest (available) CDN in the visitor's region.
If you really wanted to build in extra redundancy (which in my personal opinion is unnecessary), you could host the utag.js file yourself, but you would have to write some custom javascript code on your website to fall back on the self-hosted js file.
Hope this helps, but please let me know if anything is unclear.
Craig.
Check out our new Swift integration library for iOS, macOS, tvOS and watchOS: https://github.com/Tealium/tealium-swift with updated
documentation https://community.tealiumiq.com/t5/Swift/tkb-p/swift.