I believe the TWC tech is referring to prefix filter updates and not routing table updates. Some of TWC's peers most likely use IRR based filters on their BGP sessions. Most networks only check once a day for IRR changes and apply those changes to filters. It looks TWC put in proxy route objects today for your blocks so I am guessing someone at TWC forgot to make the updates in advance. Work around is for them to reach out to the peers with IRR based filters and request a manual update. Sounds like that is what they are doing.
route: 68.68.176.0/24
descr: RR-RC-Princetown Cable Company, Inc.-Albany
origin: AS11351
notify: ipaddreg@rr.com
mnt-by: MAINT-RR
changed: ipaddreg@rr.com 20111214
source: RADB
route: 68.68.177.0/24
descr: RR-RC-Princetown Cable Company, Inc.-Albany
origin: AS11351
notify: ipaddreg@rr.com
mnt-by: MAINT-RR
changed: ipaddreg@rr.com 20111214
source: RADB
Run the below on 12/15 and it should return your blocks.
$ whois -h filtergen.level3.net radb::as11351 | grep 68.6
$
Courtney Smith
courtneysmith@comcast.net
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments