Welcome to XboxIssues

Welcome. I decided to make this blog after being a Xbox Ambassador for a number of years.

If you don't know an Ambassador is a Volunteer that Microsoft uses to help ease the load on the actual hard working support people.

I noticed that alot of the questions I would get could easily be solved by using Microsofts Xbox.com site.

Since some of the help articles may be hard to find, understand or the issue may be called something different in the gaming community making it more difficult to solve, I've decided to make this blog to make it easier for fellow gamers to get xbox assistance, news and all things Xbox.

If you have any Xbox related question you can find the answer to feel free to contact me on YouTube, twitter or in the comments.

Thursday, May 2, 2019

NEWS: What is 768K Day, and Will It Cause Internet Outages?

An internet milestone known as "768k Day" is getting closer and some network administrators are shaking in their boots fearing downtime caused by outdated network equipment.

The fear is justified, and many companies have taken precautions to update old routers, but some cascading failures are still predicted.







WHAT IS 768K DAY?
The term 768k Day comes from the original mother of all internet outages known as 512k Day.

512k Day happened on August 12, 2014, when hundreds of ISPs from all over the world went down, causing billions of dollars in damages due to lost trade and fees, from a lack of internet connectivity or packet loss.

The original 512k Day took place because routers ran out of memory for storing the global BGP routing table, a file that holds the IPv4 addresses of all known internet-connected networks.

At the time, a large chunk of the internet was being routed through devices that were allocating TCAM (ternary content-addressable memory) large enough to store no more than 512,000 internet routes.

But when on August 12, 2014, Verizon added 15,000 new BGP routes, this caused the global BGP routing table to suddenly go over the 512,000 lines without warning. On older routers, this manifested by the global routing table file overflowing from its allocated memory, crashing the devices every time they attempted to read or work with the file. Companies like Microsoft, eBay, LastPass, BT, LiquidWeb, Comcast, AT&T, Sprint, and Verizon, were all impacted.

Many legacy routers received emergency firmware patches that allowed network admins to set a higher threshold for the size of the memory allocated to handle the global BGP routing table.

Most network administrators followed documentation provided at the time and set the new upper limit at 768,000 -- aka 768k.

Read the rest of the article at THE SOURCE


Please Don't Forget To Share:

No comments:

Post a Comment

In order to keep this page civil and clean all comments will need approval.