Usually when online service is not working or when something goes wrong online it is DNS, well that is what most of the time is the case. And yes, DNS or Domain Name Server seems to be an issue with Facebook being completely down along with Instagram and wassap.
The true cause is that there is no working Border Gateway Protocol (BGP) routes into Facebook's sites. BGP is the standardized exterior gateway protocol used to exchange routing and reachability information between the internet top-level autonomous systems (AS). Most people, indeed most network administrators, never need to deal with BGP.
Cloudflare VP Dane Knecht was the first to report the underlying BGP problem. This meant, as Kevin Beaumont, former Microsoft's Head of Security Operations Centre, tweeted,
"By not having BGP announcements for your DNS name servers, DNS falls apart = nobody can find you on the internet. Same with WhatsApp btw. Facebook has basically de-platformed themselves from their own platform."
Many people are very annoyed by this and with the fact that they cannot use their social media platforms but it seems that Facebook employees are in even bigger annoyance as it was reported that Facebook employees can't enter their buildings because their "smart" badges and doors were also disabled by this network failure. If true, Facebook's people literally can't enter the building to fix things.
Reddit user u/ramenporn, who claimed to be a Facebook employee working on bringing the social network back from the dead, reported, before he deleted his account and his messages:
"DNS for FB services has been affected and this is likely a symptom of the actual issue, and that's that BGP peering with Facebook peering routers has gone down, very likely due to a configuration change that went into effect shortly before the outages happened (started roughly 1540 UTC). There are people now trying to gain access to the peering routers to implement fixes, but the people with physical access is separate from the people with knowledge of how to actually authenticate to the systems and people who know what to actually do, so there is now a logistical challenge with getting all that knowledge unified. Part of this is also due to lower staffing in data centers due to pandemic measures."
Ramenporn also stated that it wasn't an attack, but a mistaken configuration change made via a web interface.
Both BGP and DNS are down, the "connection to the outside world is down, remote access to those tools don't exist anymore, so the emergency procedure is to gain physical access to the peering routers and do all the configuration locally."
Technicians on site don't know how to do that and senior network administrators aren't on site.
It seems that it will all be down for a couple of more hours before the issue is resolved.
Users, when upgrading to Windows 10 from Windows 7 or Windows 8/8.1, or when upgrading to a new version, build, service pack, or major update of Windows 10, can encounter error code 0xC1900101, 0x30018. Windows 10 installation fails and stops or hangs. During the installation process, it will reach a certain maximum limit (normally at 6% or 32%) then reverts back to the previous version of the operating system and displays the following message:
We couldn’t install Windows 10. We’ve set your PC back to the way it was right before you started installing Windows 10.
0xC1900101 – 0x30018 The installation failed in the FIRST_BOOT phase with the error during the SYSPREP operation.
In attempting to fix Error Code 0xC1900101-0x30018, it is vital to know what causes this issue. The most probable causes of this error are:
NOTE: If this fails, if possible, you can try using the .ISO file in upgrading.
If you’re using Windows Update in installing Windows 10, you can implement the following:
NOTE: Don’t forget to hit Enter after every command.
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
NOTE: Don’t forget to hit Enter after every command.
ren
C:WindowsSoftwareDistribution SoftwareDistribution.old
ren
C:WindowsSystem32catroot2 Catroot2.old
NOTE: Don’t forget to hit Enter after every command.
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
“It looks like you don’t have permission to save changes to this file. Try saving a copy instead.”There are several options you can explore to resolve this error. You can try updating the Microsoft Photos app or verify the ownership of the destination folder. You can also re-register and reinstall the app. For more detailed instructions, make use of the options provided below.
Set-ExecutionPolicy Unrestricted
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"}Note: In the command given, do not forget to replace the “PackageFullName” with the actual package name for the Photos app. After executing the command, it will uninstall the Photos app from your computer so you need to install it again from the Windows Store by simply looking for it. Once you found it, just click on install to start the installation process.
Some Windows users have been experiencing errors in an attempt to upgrade to Windows 10 OS. This includes the “We Couldn’t Install Windows Technical Preview 0x80070070 – 0x20005” error code. If you’re one of the many users who’ve encountered this error, you might want to check the available space on your device. Error code 0x80070070 – 0x20005 occurs when you do not have the required space to be able to install the upgrade.
In order to upgrade to Windows 10, you need to have at least 40 to 50 GB of free space in your device. Thus, you need to free up some space in order to successfully upgrade your system to Windows 10. See below for the manual methods you can employ to solve your problem.
NOTE: It would be best to seek help from an experienced technician if you are not confident enough to perform the manual methods yourself or you can alternatively make use of an automated tool.
Sometimes, there are unused applications just lying around your device. This may take up your needed space from your device for a system upgrade. Uninstalling these applications can make space that will eventually elude error code 0x80070070 – 0x20005 along with its alternatives – code 0x80070070 – 0x50011, code 0x80070070 – 0x50012, and code 0x80070070 – 0x60000.
If there are tons of images, media, videos, or documents that you rarely use but will still be needing in the future, you can move these files to another drive where Windows 10 will not be installed on.
If there are no secondary drives in your device, consider using a USB Drive or external hard disk. Another option you can do is making use of cloud storage programs like One Drive or Google Drive. In this way, you’ll still have access to these files even if it’s not in a physical location while making larger space in your device.
Most Windows users download applications or software regularly. These applications or software might come from unsafe sites where you might have accidentally downloaded a virus or malware along with the legit application or software you intended to download.
With that said, it is highly recommended to download and install in your device a reliable and powerful antivirus. Using an antivirus, you can now perform an overall scan of your device’s system. Once you’re able to detect and remove any suspected virus or malware, you’ll now be able to get rid of the error code 0x80070070 – 0x20005. After solving the issue, you can now resume upgrading to Windows 10.
Can’t seem to put up with the long and technical manual repair process? You can still fix this error by downloading and installing a powerful automated tool that will surely get the job done in a jiffy!