Time capsule stopped working......!!!

The problem is not the hardware.. although apparently apple did change it over.

I am guessing your Macbook is on High Sierra.. or perhaps you even upgraded to Mojave??

Time Machine is very unreliable since Sierra. It was unreliable before that.. but with High Sierra it reached the pinnacle.. maybe Mojave will be even worse.. so testing long term is not in yet.

March to mid-June is really very good.. it can get down to a few weeks.. !!

Fixing the problem is difficult because it is built into the whole way Apple is attempting to prevent virus attacks.. and making it harder and harder to open network drives. And yet to make Time Machine reliable.

You must set IPv6 in the computer and on the TC to link-local only (auto does not cut it). That is assuming your not using a fully IPv6 network which is different configuration.

If the TC is using long names with spaces and illegal characters like apostrophe.. reset the TC to factory and reconfigure it.. all short names, no spaces and pure alphanumerics. Passwords same rules but can be longer.

If the TC is bridged.. that will definitely lead to trouble.. highly recommend using static IP at the very least. This is for when you use a modem router.

Do tell us the whole network setup.

What is the make and model of the modem? Is it also being used as a router?

How is the TC configured?

Screenshots help loads.

Even with all that the dreaded.. self corruption can be expected regularly.

The fix for this is to install Carbon Copy Cloner and use that backup software instead.

Far more reliable to network targets than Time Machine. We recommend TM now is only suitable to local USB drive plugged directly to your computer.

I find the temptation to return to windows quickly overwhelmed by the AV software and security software.. and adware software and every other protection you need to load into the system to have some hope of beating the hackers. Followed by loads of just hating it.. !!

However there is no reason to keep "UPGRADING" .. I keep a version or two behind.. wait for the next version to come out which generally means end of major support for previous version.. and the one before that should just about be ok.

I jumped ship at vista.. so must be pretty near when you jumped. Snow Leopard at that time was a great OS.

A lot of the network trouble comes from recent changes to mdns responder.

I found the recent changes have made it difficult to get network drives in particular to be reliable.

I am happy to work through the issues with you.

I recommend the following.

1. All names short, no spaces and pure alphanumeric.. passwords same but can be longer. Apple moved to SMB protocol at Yosemite or Mavericks.. but High Sierra AFP is seriously depreciated.. YET.. due to failure to upgrade the TC it is still required to do backups. SMB naming is a lot tighter than AFP and Apple RECOMMENDED names.. are just WRONG.

2. Use IPv6 set to link-local only (assuming your whole network is not running full IPv6.. most are not). Do this for both wireless and ethernet.. whichever you use.. AUTO does not cut it.

Set IPv6 to Link-local only on the TC as well.

3. The TC must have a static IP.. this is no issue when it is setup as main router.. but is a big issue in bridge.. You MUST set the TC to static IP so it does not keep changing. You can do this via dhcp reservation on the main router or on the Internet tab of the TC.. note that setting both is good thing.

I found if you are forced to use bridge on the TC it is good to use DHCP server as well.. this is tricky setup so ask for details.. with full details of your network. When you have lots of iOS as well as Mac for as long as the airport lasts you can use it as the main DHCP server without double NAT.. this worked particularly well in my experience. Apple includes a bonjour sleep proxy in the Airport router.. no other router will.

4. The next bits are esoteric perhaps..

Make sure DNS in computer includes the main router.. not just ISP dns.

Make sure the search domain is blank or local. Not the ISP domain.

Make the main router domain local if at all possible. The TC is locked to local.. apparently and that causes some of the issues.

Super Duper is fine.. Apple integrated Time Machine.. and it is great software.. until you start using it on network.. then everything tend to go to pieces.

You cannot use the backup in the same way but it is totally wrong to say you cannot recover from a CCC or SuperDuper backup.. Of course Apple will not support it.. the 3rd party will.

5. The Mac must not include AV or security software or accidentally I'm sure adware installed.

Other things are elusive at the moment.

If you need help post again but include screenshots as that gives me a lot more clues as to your setup.

Many thanks for sharing your recommendations on changing Time Capsule settings. My TC was backing up very slowly (1MB per hour ever after the disk was erased) until I changed the first 2 settings: shorten the name and using link-local only on IPv6. Now it is running at 30GB per hour. Hurray!!

Been struggling for months with a simpler version (Ethernet-connected Time Capsule NOT used as modem and/or USB drive) of this scenario. Just did a late-night 6 hour chat with Apple techs which seemed to work last night, but does not work today. Yesterday my iPad Pro would not connect at all, after “fixing” that Time Machine backups to the USB drive would hang.

I have to agree with your characterization of macOS from Sierra to the present, I recently “upgraded” to High Sierra knowing that my music software isn’t ready for Mojave. I do have Super Duper, but I have been told that Apple will not use anything but Time Machine backups for system restoring. I’ve been using Macs since 2002 after 20 years of Windows ****, which seems to have now consumed Apple. This may be a career-ending issue due to a heavy investment in Apple products for my studio.