Is the GA tracking configured to anonymize IP data?
If so, then IP filtering will not work as expected, as anonymizing IPs masks the last octet of the IP address.
In these instances you have a few options:
Adjust the filter match to that begin with and leave the last octet in the IP address blank. Keep in mind, this may have the unintended result of also filtering out other legit traffic, due to the IP range being caught by the filter being broader than intended.
Use an addon such as Ghostery to block GA tracking
Create a custom dimension with a User scope. On a private page on the site (non indexed and not linked to via other pages), add the tracking and configure it to send an event and the custom dimension named block with a value such as myvisits on page load.
Create a View level custom exclude filter, to exclude the custom dimension block with the value myvisits.
Bookmark the page and revisit it any time you clear your cookies/cache to reset the custom dimension for your visits.
When filtering custom dimensions the filter must be created within the View at the View level. It cannot be created at the Account level and then applied to a View.
You will need to do this for each View where you want to exclude your visits.
If the IP address is an IPv6 address (eg will look similar to 2620:0:10e2:2:c4bc:9fd2:974f:cf19). Then use match type that begin with and shorten from the end of the IP address if necessary.
To check if IP data is being anonymized, you can use GA Debugger with Chrome Dev Tools, and it will show you what parameters and values are being sent with each hit to GA. aip parameter value will be 1 if IP anonymization is set to true/turned on.