While the downtime lately has been pretty rough, I have to imagine that it's either because of the new changes to YouTube or they are intentionally doing something to harm this app since 233k people are automatically skipping sponsors. This has to be doing things YouTube doesn't like, but they can eat shit. Ajay's extension has worked very well for most of the length of time that I've used it and I feel like he's trying to fix whatever the current issue is. It's saved me from watching hours of terrible normally unblockable advertisements and I'm grateful the work that's already gone into making that possible.

Working again now, was broken for a while.

Switched from Chrome to FF specifically for this, worked for 2 days, has not worked for multiple days. This is an all or nothing review, either it works or it doesn't. It doesn't.

Something we vitally need. Does the job perfectly.

works for almost all videos, even new ones with low views

Perfect, 10/10. Awesomeness. Just wish it worked on Rumble

good extension but it stopped working randomly

Edit: Issue fixed, great extension, changing review to 5 stars. Thanks for fixing it. :-)

Old review:
Great extension, but lately, in last lets say a week, it stopped working multiple times, I get error "A connection error has occurred. Error code: 522" and due to server dependency it basically stops functioning. Also same happens with homepage:
https://sponsor.ajay.app
Error "Connection timed out Error code 522", though that in between starts working again, before it drops, extension doesn't. Also I think before that I got too many connections as error for website, so it might be that "suffering from success" type of situation, though I obviously can't say that for sure. But it might be worth considering some kind of backup from where extension can pick list of segments and stuff.

Also might be worth integrating:
https://status.sponsor.ajay.app/
Into extension, it would be way of letting community know that you are already aware of the issue. Considering it is repeating issue.

Yesterday had an error code 503 , today 504 :(