WEBVTT

00:00:00.080 --> 00:00:07.200
oh look at that another major online outage that means you can't book travel

00:00:05.040 --> 00:00:11.519
find a date or order that refill of toilet paper you so desperately need

00:00:09.519 --> 00:00:15.440
seriously send help if it seems to you like many of the sites you depend on are

00:00:13.679 --> 00:00:18.480
going down more frequently you're definitely not alone but it's not like

00:00:16.880 --> 00:00:23.840
facebook and amazon are running on Windows vista so why the heck do these

00:00:21.080 --> 00:00:26.640
multi-billion dollar services seem so unreliable

00:00:24.960 --> 00:00:31.199
it might be easy to blame some of the high profile outages we've seen over the

00:00:28.480 --> 00:00:34.640
past few years on the coven pandemic due to the huge amount of load placed on

00:00:32.800 --> 00:00:39.520
cloud servers from folks working from home or otherwise staying in i mean

00:00:37.440 --> 00:00:43.520
it's a lot of zoom calls but while stay-at-home orders and remote work did

00:00:41.680 --> 00:00:47.760
play a part critical services experiencing downtime was already

00:00:45.440 --> 00:00:51.520
becoming an all too frequent problem before the pandemic

00:00:49.600 --> 00:00:55.440
and it's still a big concern even now that much of the world is trying to get

00:00:52.879 --> 00:00:58.239
back to normal but like most wide scale problems

00:00:56.480 --> 00:01:03.039
there are many things at play for starters round the clock internet usage

00:01:00.480 --> 00:01:08.000
became very common very quickly think about the explosion in always connected

00:01:05.439 --> 00:01:12.240
iot devices people leaving high def videos playing all night so they can

00:01:10.080 --> 00:01:16.159
fall asleep to them and massive game and software downloads that often take place

00:01:14.400 --> 00:01:19.920
while users are in bed these things just weren't that common

00:01:18.000 --> 00:01:24.080
only 10 years ago but the explosion and net traffic since then has overloaded

00:01:22.159 --> 00:01:28.560
infrastructure that was only designed to handle peak traffic during certain hours

00:01:26.479 --> 00:01:32.720
of the day but with all the resources that big tech has why does this problem

00:01:31.040 --> 00:01:36.240
seem to be getting worse instead of getting better we'll tell you right

00:01:34.479 --> 00:01:40.159
after we thank freshbooks the invoicing and accounting solution that's built for

00:01:37.920 --> 00:01:43.759
owners and their clients freshbooks users save a ton of time and money we're

00:01:42.000 --> 00:01:48.399
talking 11 hours a week that they used to spend sorting through invoices and

00:01:45.600 --> 00:01:51.920
keeping track of financials plus 94 of freshbooks users say it's super easy to

00:01:50.560 --> 00:01:55.680
get up and running and with award winning support you're never alone

00:01:53.920 --> 00:02:01.040
switch to freshbooks today and join over 24 million people who have used it and

00:01:58.399 --> 00:02:05.200
loved it try freshbooks free for 30 days no credit card required by going to

00:02:02.640 --> 00:02:08.720
freshbooks.com techquickie and get started today so the fact that big tech

00:02:07.520 --> 00:02:12.959
is so well big is actually part of the issue

00:02:11.120 --> 00:02:16.640
here even though the internet is a pretty big place there are actually a

00:02:14.720 --> 00:02:22.080
fairly small number of services that help run a huge number of sites for

00:02:19.840 --> 00:02:26.239
example amazon web services provides back-end cloud computing for everything

00:02:24.560 --> 00:02:31.200
from your netflix recommendations to your roomba vacuum to your venmo account

00:02:28.879 --> 00:02:35.599
to even your airline reservations and of course aws has had numerous outages that

00:02:33.760 --> 00:02:41.440
have made headlines with causes as diverse as server cooling failures nasty

00:02:38.879 --> 00:02:46.160
weather overloaded systems and ddos attacks amazon does have redundancies

00:02:43.840 --> 00:02:50.560
built in but even so the fact that one company helps support so much net

00:02:48.400 --> 00:02:54.800
traffic leaves one very obvious point of failure for lots of services that you

00:02:52.720 --> 00:02:59.519
didn't even know were reliant on amazon or one of its few large-scale

00:02:56.959 --> 00:03:03.040
competitors like microsoft azure or google cloud

00:03:00.879 --> 00:03:06.879
and to top it all off your isp is routing much of this traffic over cable

00:03:04.959 --> 00:03:12.319
lines that haven't received upgrades to improve capacity in a very long time

00:03:10.000 --> 00:03:17.040
which can lead to congestion in the last mile of wiring that goes to your house

00:03:15.120 --> 00:03:21.599
and there isn't even enough fiber on the back end right now to keep up with

00:03:19.280 --> 00:03:26.879
projected increases in data usage especially as mobile carriers continue

00:03:23.680 --> 00:03:29.200
to roll out 5g so until cloud systems

00:03:26.879 --> 00:03:34.080
become more secure and more redundant and telecom providers build out better

00:03:31.120 --> 00:03:38.000
infrastructure i would not count on 100 uptime but the good news is that these

00:03:35.760 --> 00:03:42.239
outages give you an excuse to stop mindlessly scrolling through your phone

00:03:40.319 --> 00:03:45.599
and go touch some grass thanks for watching guys if you like this video hit

00:03:43.760 --> 00:03:48.959
like hit subscribe and hit us up in the comments section with your ideas of

00:03:47.519 --> 00:03:51.599
topics that we should cover in the future