Operations | Monitoring | ITSM | DevOps | Cloud

It took about twenty-three years, a couple of IPv6 days, the exhaustion of most of the IPv4 address pools available at Regional Internet Registries (RIRs), and the increase of prices in IPv4 address market, but finally, it looks like IPv6 made it and met one important threshold in November 2020 – 100k IPv6 prefixes are now currently announced on the Internet!

Inspecting complicated network issues shouldn’t require you to switch between multiple tabs and network records. Solving these issues often boils down to finding the IP addresses of a network entity. Be it a desktop, server, port, or some other entity, its IP address gives you much-needed insight into details like its asset tag, interface specifics, user, and device type. This information helps you get to the bottom of network issues, aiding in effective troubleshooting.

Securing access to business resources has always been of high priority for admins and IT teams. In the wake of the pandemic, workforces are more distributed than ever before, and 76 percent of global office workers state that they would like to work from home even when the pandemic is over.

With the advanced containerization that has become the norm in the modern cloud, your infrastructure is likely more distributed, and thus more exposed to networking issues, than ever before. When troubleshooting application performance issues, this can make it difficult to link the symptoms you observe through monitoring the “golden signals” (requests, latency, and errors) on individual endpoints in your application to their underlying root causes.

On October 1, 2020, the FCC invited comments from the telecommunications industry to ascertain progress on implementing Caller ID Authentication. Verizon’s reply underscored the extensive amount of time and effort its team(s) have put in, yielding substantial progress.